Skip to main content
AVOID.NET
← avoid.net

Verify a decision

Every moderation decision on AVOID.NET is anchored to the Solana blockchain. You don't have to trust us — you can verify cryptographically that we committed to a verdict at a specific moment and have not rewritten it.

How verification works

  1. We commit. When a moderator accepts/rejects a submission, we serialize the decision into deterministic UTF-8 bytes (payload_canonical_string), hash it with SHA-256, encode the digest as base58, and write it to Solana inside an SPL Memo v2 transaction.
  2. We store the bytes. The exact bytes we hashed are stored alongside the decision in our database. Anyone can read them and recompute the hash in any language.
  3. You compare three values. Database hash, your independently-recomputed hash, and the hash inside the on-chain memo. If all three match, the decision is authentic and timestamped.
The on-chain memo format is AVOID.NET|v1|h:<b58-sha256>|d:<id>|t:<iso>

Find a signature on any investigation page's decision log, or run python -m src.verify_decision --signature <sig> for a CLI check.

Sequence
#2
Score
33 → 33 (0)
Cluster
mainnet-beta
Slot
462279335
Off-chain at
2026-10-28T00:48:41.559Z
Anchored at
2026-10-28T00:49:18.000Z
Block time
2026-10-28T00:49:18.000Z

Independent verification

1. Database (off-chain)
6uCwJAhyxi1SzkJ8xGasKaDHznj1TDo53T4avWWvZCDd
2. Recomputed (your browser)
computing…
3. On-chain (Solana memo)
fetching…
Canonical bytes hashed (1482 chars)
{"actor":"reviewer","artifact_identity":"f545133a7acafb07b7ecce39ae7efb9a","blocked_count":1,"decided_at":"2026-10-28T00:48:41.499Z","decision":"review","disputed_pct":0.1111,"findings_hash":"B6EM8g6qCJmAhbvs7LJ8jVELssYuG9r65rjTP8hJJiCa","investigation_id":"4926d111-a9da-4f2e-b0c7-00525f264ae3","judge_def_hash":"8800307026131ea9d5da939d32b9a1f1884b2b84a5de33c8e87931d36f38d0f8","new_score":33,"omissions":{"material":0,"total":1},"page_content_hash":"ac6c2d76db9c039edae1d4f39bc9d30a9406c44a247aa4c978a819acee6cc1d7","page_slug":"mantra-chain-upstream-exploit-august-2026","prev_score":33,"reason":"The core incident timeline (first attack, halt block and time, disclosure chronology, price move, six-chain total) matches the Cosmos Labs post-mortem and CoinDesk. One discrepancy: the page uses about 05:30 UTC for the August 22 restart (press reports) while the primary post-mortem records 03:38 UTC, implying about 28 rather than 30 hours of downtime. The page handles conflicting vulnerability identifications and loss figures transparently. Only a sample of claims was checked; the 15:20 UTC window-close time and the crypto.news loss figure were not verified.","reviewer_def_hash":"bc11388ce4bc4deea1b064fea362663ae06e3f4f687f99604769044d6ffba770","score_delta":0,"scored_claims":9,"sequence_num":2,"subject_status":"operating","subject_status_contradicts_page":false,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}