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 · Famous Fox Federation
- Sequence
- #5
- Score
- 62 → 57 (-5)
- Cluster
- mainnet-beta
- Slot
- 425175895
- Off-chain at
- 2026-06-08T19:40:23.906Z
- Anchored at
- —
- Block time
- —
Independent verification
- 1. Database (off-chain)
- CNB22YMS5qdz8T6wemdMAs6HdWcNAR2tfQMiqgLkFdTH
- 2. Recomputed (your browser)
- computing…
- 3. On-chain (Solana memo)
- fetching…
Canonical bytes hashed (1224 chars)
{"actor":"judge","decided_at":"2026-06-08T19:40:22.488Z","decision":"review_approve","investigation_id":"287d27cb-c065-40d5-9fc6-d2793cbd0d6b","new_score":57,"page_slug":"famous-fox-federation","prev_score":62,"reason":"Zero claims were directly disputed across 27 findings, placing this page firmly in the approve band. The reviewer identified five partially-supported findings and four unverifiable claims, none of which concern core allegations of fraud, misconduct, or regulatory action. The most significant issues are two correctable timeline errors: claim_findings[25] dates the Jito Foundation Q&A to April 2024 when the article was published May 2023, and claim_findings[27] incorrectly states that Roadmap 2.0 outlined Citrus, which does not appear in the source document. Charity donation figures in claim_findings[23] are also slightly understated and two named charities are not confirmed by the cited source. These are editing-grade corrections, not grounds for revise or deny. A -5 score modifier is applied to flag the factual timeline inaccuracies for remediation.","score_delta":-5,"sequence_num":5,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}