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
- 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. - 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.
- 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.
Decision
review · Wormhole
- Sequence
- #7
- Score
- 62 → 62 (0)
- Cluster
- mainnet-beta
- Slot
- 462173064
- Off-chain at
- 2026-10-27T18:31:51.904Z
- Anchored at
- 2026-10-27T18:31:57.000Z
- Block time
- 2026-10-27T18:31:57.000Z
Independent verification
- 1. Database (off-chain)
- 8KvxGLfxRBjw9VEawe4JCobQz7mkQEJPRrMgJ3jxfXVd
- 2. Recomputed (your browser)
- computing…
- 3. On-chain (Solana memo)
- fetching…
Canonical bytes hashed (1484 chars)
{"actor":"reviewer","artifact_identity":"7ff957ed80d6228e00417a6c690368e6","decided_at":"2026-10-27T18:31:51.765Z","decision":"review","disputed_pct":0.1333,"findings_hash":"9qD5VXbxSAG3GkTGvg6p1T2UWem4j4bhrDPChM5z6ae8","investigation_id":"57924d6e-a4c7-4662-8069-3e5dd2071dba","judge_def_hash":"8800307026131ea9d5da939d32b9a1f1884b2b84a5de33c8e87931d36f38d0f8","new_score":62,"omissions":{"material":1,"total":1},"page_content_hash":"53376dbb008e49df7bc5fd740e56c9bcf050d277ae94794a713596fa573f2576","page_slug":"wormhole","prev_score":62,"reason":"The core narrative holds: the Feb 2022 exploit, Jump's replenishment, the Oasis counter-exploit, the independence from Jump, the $225M raise, the W token, the Aptos bug and the Jump SEC settlement all check out. Problems are a stale recovery picture (the summary says funds are largely unrecovered, while a reported July 2024 recovery of more than $400M by Tai Mo Shan Limited is omitted), an unsupported hacker counter-claim, a misattributed March 2024 NY judgment, an unverified August 2023 departure date, and internal drafting artifacts that refer to 'pages' instead of sources. The project is operating with no 2026 incident found.","reviewer_def_hash":"bc11388ce4bc4deea1b064fea362663ae06e3f4f687f99604769044d6ffba770","score_delta":0,"sequence_num":7,"subject_status":"operating","subject_status_contradicts_page":false,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}