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 · DODO AMM
- Sequence
- #6
- Score
- 62 → 51 (-11)
- Cluster
- mainnet-beta
- Slot
- 462049100
- Off-chain at
- 2026-10-27T11:12:00.038Z
- Anchored at
- 2026-10-27T11:12:25.000Z
- Block time
- 2026-10-27T11:12:25.000Z
Independent verification
- 1. Database (off-chain)
- DoaPejwdqFP4nrUsZiqwPpvymmWAsiv6o68KbBcHaTYc
- 2. Recomputed (your browser)
- computing…
- 3. On-chain (Solana memo)
- fetching…
Canonical bytes hashed (1592 chars)
{"actor":"judge","artifact_identity":"e76be5b8a0bde263008fb56f37ffd33b","band_override":null,"blocked_count":2,"decided_at":"2026-10-27T11:11:59.561Z","decision":"review_revise","delist_requested":false,"disputed_pct":0.5,"investigation_id":"3ff37634-d276-4760-a4b9-2c4b57a50a6d","judge_def_hash":"8800307026131ea9d5da939d32b9a1f1884b2b84a5de33c8e87931d36f38d0f8","new_score":51,"page_slug":"dodo-amm","prev_score":62,"reason":"Of six claims checked, two were blocked by the source and are left out of the count. Of the remaining four, one citation was disputed (claim_findings[4]: the November 2022 Alameda/FTX collapse is sourced to a 2021 article about the DODO hack) and one was unverifiable (claim_findings[5]: the 'no regulatory action' claim rests on a generic compliance blog). That gives a 50% disputed share, in the significant-issues band. The core exploit facts were confirmed by CoinDesk (claim_findings[0]), and the $3.1M recovery figure conflicts with CoinDesk's day-one figure but is unsettled (claim_findings[1]). The review found no omissions and no contradicting subject status. Because the reviewer's confidence is low (0.35) and the count rests on only four claims, the penalty is set at the mild end of the band.","reviewer_def_hash":"bc11388ce4bc4deea1b064fea362663ae06e3f4f687f99604769044d6ffba770","score_delta":-11,"score_limit":{"applied":-11,"limited":true,"proposed":-15,"rule":"limited_no_second_opinion","second":null},"scored_claims":4,"sequence_num":6,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}