Skip to main content
AVOID.NET
← 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_revise · Tornado Cash
View on Solana ↗
Sequence
#5
Score
28 → 26 (-2)
Cluster
mainnet-beta
Slot
462046045
Off-chain at
2026-10-27T11:01:34.565Z
Anchored at
2026-10-27T11:01:38.000Z
Block time
2026-10-27T11:01:38.000Z

Independent verification

1. Database (off-chain)
CT1nag6Ug48ns6LycvC5cvowwynt9YdFaZE59ofiH6JX
2. Recomputed (your browser)
computing…
3. On-chain (Solana memo)
fetching…
Canonical bytes hashed (1555 chars)
{"actor":"judge","artifact_identity":"20684d9391db3b4cf042483ad7a694bc","band_override":null,"decided_at":"2026-10-27T11:01:34.019Z","decision":"review_revise","delist_requested":false,"disputed_pct":0.4,"investigation_id":"4b6ee26d-dd35-4c7d-b41a-ccf5a997640a","judge_def_hash":"8800307026131ea9d5da939d32b9a1f1884b2b84a5de33c8e87931d36f38d0f8","new_score":26,"page_slug":"tornado-cash","prev_score":28,"reason":"Two of five checked claims (40%) could not be verified: claim_findings[0] and claim_findings[1] both describe an April 2026 detention order for Alexey Pertsev, and the cited sources date from 2024 and 2025 and do not support it. The other checked claims, including the 2025 Storm conviction, the March 2025 OFAC delisting and the April 2027 retrial date, are consistent with sources, although claim_findings[2] notes the retrial delay was also tied to a defense request. The unverified claims are one defect repeated in the page text and timeline, the reviewer's confidence is moderate, and the page's subject is not shut down or re-sanctioned, so the penalty sits at the low end of the significant band. The high-priority gap on Pertsev's 2026 appeal status also supports revision rather than approval.","reviewer_def_hash":"bc11388ce4bc4deea1b064fea362663ae06e3f4f687f99604769044d6ffba770","score_delta":-2,"score_limit":{"applied":-2,"limited":true,"proposed":-15,"rule":"limited_no_second_opinion","second":null},"sequence_num":5,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}