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 · Dark2Web
- Sequence
- #3
- Score
- 0 → 0 (-15)
- Cluster
- mainnet-beta
- Slot
- 464281892
- Off-chain at
- 2026-11-01T23:46:09.037Z
- Anchored at
- 2026-11-01T23:46:24.000Z
- Block time
- 2026-11-01T23:46:24.000Z
Independent verification
- 1. Database (off-chain)
- 8mFxRK75w4gyLqdtfhfdYMvC4BFUEeoM7GUPaMLnrebf
- 2. Recomputed (your browser)
- computing…
- 3. On-chain (Solana memo)
- fetching…
Canonical bytes hashed (1439 chars)
{"actor":"judge","artifact_identity":"874ca6a98ef74236995e95a2bf0fbb07","band_override":null,"blocked_count":2,"decided_at":"2026-11-01T23:46:08.773Z","decision":"review_revise","delist_requested":false,"disputed_pct":0.2857,"investigation_id":"70c2d847-3411-4499-91bb-79006efba6ca","judge_def_hash":"8800307026131ea9d5da939d32b9a1f1884b2b84a5de33c8e87931d36f38d0f8","new_score":0,"page_slug":"dark2web","prev_score":0,"reason":"Of 15 claims reviewed, 2 could not be checked because the source (the DOJ page) blocked the reviewer and were left out of the count. Of the remaining 13, none were contradicted, but 4 could not be matched to their cited sources (claim_findings[5], [11], [12], [14]), which puts the unverified share at about 31%, just inside the 30-60% band. The penalty is set at the mild end of that band because nothing was disputed, the core facts on defendants, charges, arrest date and seizure were confirmed by the Secret Service release and HelpNet Security, and the reviewer's confidence was moderate. Two further claims were only partly supported: the 'primary venue' wording for ransomware affiliates (claim_findings[8]) and the 2022-2025 period (claim_findings[7]).","reviewer_def_hash":"bc11388ce4bc4deea1b064fea362663ae06e3f4f687f99604769044d6ffba770","score_delta":-15,"scored_claims":14,"sequence_num":3,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}