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 · Edward Zimbardi
- Sequence
- #2
- Score
- 2 → 0 (-8)
- Cluster
- mainnet-beta
- Slot
- 462048509
- Off-chain at
- 2026-10-27T11:09:58.470Z
- Anchored at
- 2026-10-27T11:10:19.000Z
- Block time
- 2026-10-27T11:10:19.000Z
Independent verification
- 1. Database (off-chain)
- FUhEd1DAiaZcegQ8Rn93rSkcdtcoGsaa19DDUBP5Hbec
- 2. Recomputed (your browser)
- computing…
- 3. On-chain (Solana memo)
- fetching…
Canonical bytes hashed (1667 chars)
{"actor":"judge","artifact_identity":"a4112d641302c22d8309642f2c718a7f","band_override":null,"blocked_count":3,"decided_at":"2026-10-27T11:09:58.060Z","decision":"review_revise","delist_requested":false,"disputed_pct":0.1429,"investigation_id":"ba1fca3e-6263-4595-942f-90c03d13319e","judge_def_hash":"8800307026131ea9d5da939d32b9a1f1884b2b84a5de33c8e87931d36f38d0f8","new_score":0,"page_slug":"edward-zimbardi","prev_score":2,"reason":"No claim was contradicted. Of the 7 claims the reviewer could check, 1 could not be corroborated (claim_findings[9], the 1997 theft conviction, which the page already labels low-confidence), about 14%. Three further claims (claim_findings[2], [5], [6]) could not be checked because the sources blocked the reviewer, so they are left out of the calculation and count as a coverage limit, not a defect. The page omits a reported March 2024 Dutch arrest (omission_findings[0]) and does not state that the charges are allegations only (omission_findings[1]), so the page needs revision. Reviewer confidence is moderate (0.6), which keeps the penalty at the low end of the band.","reviewer_def_hash":"bc11388ce4bc4deea1b064fea362663ae06e3f4f687f99604769044d6ffba770","score_delta":-8,"scored_claims":7,"sequence_num":2,"severity_override":{"applied":true,"band":"minor","from_band":"minor","reason":"omission_findings[0] (reported March 2024 Dutch arrest) is rated material and is not on the page. It rests only on search snippets of a source the reviewer could not open, so it moves the verdict to the minor band, not higher."},"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}