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_approve · The DAO Hack 2016
- Sequence
- #3
- Score
- 2 → 0 (-3)
- Cluster
- mainnet-beta
- Slot
- 424139622
- Off-chain at
- 2026-06-04T00:57:56.367Z
- Anchored at
- —
- Block time
- —
Independent verification
- 1. Database (off-chain)
- BmApD86aDzvVVtWAmYWvB6XvDcDBmthG3d8ZQZugz2PV
- 2. Recomputed (your browser)
- computing…
- 3. On-chain (Solana memo)
- fetching…
Canonical bytes hashed (1295 chars)
{"actor":"judge","decided_at":"2026-06-04T00:57:56.140Z","decision":"review_approve","investigation_id":"cf4fc863-726e-492a-a76a-c6e4b303cdcd","new_score":0,"page_slug":"the-dao-hack-2016","prev_score":2,"reason":"The page holds up well across 28 verified claims: 22 confirmed, 3 partially supported, 1 unverifiable, and 1 disputed — yielding a disputed_pct of 7.1%, within the approve threshold. The single disputed item (claim_findings[25]) is a timeline date error: the page lists the Sirer moratorium paper as June 9, 2016, but the document was published May 27, 2016 per the primary source at hackingdistributed.com, approximately 21 days before the hack rather than the few days implied in both the timeline and section body text. This is a verifiable factual error but does not touch any core allegation about the attack, the hard fork, or the SEC findings. All hard fork mechanics, miner adoption figures, and SEC regulatory claims are confirmed by Tier 1 sources including the Ethereum Foundation blog and Harvard Law School. A minor score adjustment is applied to reflect the confirmed timeline error; no banner or status change is warranted.","score_delta":-3,"sequence_num":3,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}