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_revise · Wormhole
- Sequence
- #2
- Score
- 42 → 34 (-8)
- Cluster
- mainnet-beta
- Slot
- 419336318
- Off-chain at
- 2026-05-12T21:35:22.800Z
- Anchored at
- —
- Block time
- —
Independent verification
- 1. Database (off-chain)
- 8SovTqKaMbdGfaSAk5PYzLRtRX1vAT4ruFw7Hsf6Fm5K
- 2. Recomputed (your browser)
- computing…
- 3. On-chain (Solana memo)
- fetching…
Canonical bytes hashed (1674 chars)
{"actor":"judge","decided_at":"2026-05-12T21:35:22.651Z","decision":"review_revise","investigation_id":"57924d6e-a4c7-4662-8069-3e5dd2071dba","new_score":34,"page_slug":"wormhole","prev_score":42,"reason":"The core factual record of the February 2022 exploit — the mechanism, on-chain addresses, dollar figures, bailout, fundraise, and governance token launch — is well-confirmed across credible sources. However, three claims were disputed and one high-priority coverage gap requires correction before the page can be approved. The security section names the post-exploit replacement function as 'current_instruction_at' when independent security firms (Kudelski, Halborn) consistently identify it as 'load_instruction_at_checked' (claim_findings[27] disputed by Tier 2 sources). The bug bounty maximum is stated as $5 million but the live Immunefi program shows $1 million (claim_findings[28] disputed by Tier 1 source). Most significantly, the summary's statement that stolen funds 'remain substantially unrecovered despite a partial $140 million counter-exploit' materially understates the recovery outcome: law firm Kobre & Kim's public announcement states over $400 million was recovered by July 2024 via English court enforcement of a New York judgment (claim_findings[7] partially_supported; coverage_gaps[0] priority high). Additionally, the timeline entry for the Tai Mo Shan SEC charges is dated December 1, 2024, but the SEC's own press release is dated December 20, 2024 (claim_findings[36] disputed by Tier 1 source).","score_delta":-8,"sequence_num":2,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}