Skip to main content
Sign in
← avoid.net

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

  1. 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.
  2. 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.
  3. 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 · SushiSwap
View on Solana ↗
Sequence
#5
Score
3252 (+20)
Cluster
mainnet-beta
Slot
426514494
Off-chain at
2026-06-14T23:15:59.609Z
Anchored at
Block time

Independent verification

1. Database (off-chain)
Ho5f8ZfwnKVLWVdWziWnogE7y21fToW3g8V3Cy3MD2FR
2. Recomputed (your browser)
computing…
3. On-chain (Solana memo)
fetching…
Canonical bytes hashed (1557 chars)
{"actor":"judge","decided_at":"2026-06-14T23:15:59.498Z","decision":"review_approve","investigation_id":"df79decd-dab0-46e7-a234-b7db05d89ce2","new_score":52,"page_slug":"sushiswap","prev_score":32,"reason":"The blue-chip calibration review found zero disputed facts across all six claim findings — all are marked supported. The current score of 32 (CRITICAL band) is demonstrably too harsh for a legitimately operating protocol. Three incidents that drove the low score are materially misrepresented in severity: claim_findings[0] shows Chef Nomi returned all ~$14M in full, producing $0 net user loss; claim_findings[1] confirms the SEC subpoena has resulted in no charges and remains a non-public fact-finding inquiry; claim_findings[2] shows the $3.3M RouterProcessor2 exploit was partially recovered with a reimbursement plan executed. claim_findings[5] identifies a guilt-by-association inference linking SBF's 2020 multisig stewardship to his 2023 FTX fraud — an inference unsupported by the cited timeline. Real material caveats remain (claim_findings[3]: December 2025 single-wallet governance concentration; unresolved SEC inquiry; ~98.7% TVL decline; unverified North Korean IT worker allegations) and are sufficient to hold the page at CAUTIONARY rather than VERIFIED. A +20 delta moving the score from 32 to 52 is proportionate to the miscalibration and consistent with the reviewer's 0.82 confidence.","score_delta":20,"sequence_num":5,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}