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 · Fusion by IPOR
- Sequence
- #3
- Score
- 52 → 42 (-10)
- Cluster
- mainnet-beta
- Slot
- 425437319
- Off-chain at
- 2026-06-10T00:33:11.680Z
- Anchored at
- —
- Block time
- —
Independent verification
- 1. Database (off-chain)
- DMpqzWrDsohvL74YgnRXxSvkeA6T7T7bSZu7RYtBGtHk
- 2. Recomputed (your browser)
- computing…
- 3. On-chain (Solana memo)
- fetching…
Canonical bytes hashed (1286 chars)
{"actor":"judge","decided_at":"2026-06-10T00:33:10.788Z","decision":"review_revise","investigation_id":"610e5c95-082e-484a-843b-84925eef4194","new_score":42,"page_slug":"fusion-by-ipor","prev_score":52,"reason":"The page's core claims about the January 6, 2026 exploit — amount, technical mechanism, Tornado Cash routing, SEAL engagement, and DAO compensation commitment — are all confirmed by multiple independent sources. However, two issues require correction before the page can be approved. First, claim_findings[7] (the vault deployment date of 2024-01-01) is disputed as internally inconsistent: the page's own '490 days prior' language points to approximately August 2024, not January 2024, and no source confirms a January 2024 date. Second, claim_findings[4] (ZachXBT attribution in the public summary) is unverifiable — all consulted sources credit Hexagate and Blockaid as the alerters, not ZachXBT — and should be removed or sourced. Three high-priority coverage gaps also require attention: missing on-chain transaction links, dead docs.ipor.io citation URLs, and the unresolved ZachXBT attribution, all flagged by the reviewer.","score_delta":-10,"sequence_num":3,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}