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 · Unleash Protocol
- Sequence
- #4
- Score
- 55 → 55 (0)
- Cluster
- mainnet-beta
- Slot
- 464447076
- Off-chain at
- 2026-11-02T09:35:46.390Z
- Anchored at
- 2026-11-02T09:36:01.000Z
- Block time
- 2026-11-02T09:36:01.000Z
Independent verification
- 1. Database (off-chain)
- 24brMV5G4ZCgaghLrR2RwUmnuYNVSF66v9YWYmvUuQQB
- 2. Recomputed (your browser)
- computing…
- 3. On-chain (Solana memo)
- fetching…
Canonical bytes hashed (1585 chars)
{"actor":"judge","artifact_identity":"3adb14428f4c50941090a50551fc5724","band_override":null,"blocked_count":1,"decided_at":"2026-11-02T09:35:46.113Z","decision":"review_revise","delist_requested":false,"disputed_pct":0.3333,"investigation_id":"52ea6c6f-9de0-4ac0-809e-729d8224fa64","judge_def_hash":"8800307026131ea9d5da939d32b9a1f1884b2b84a5de33c8e87931d36f38d0f8","new_score":55,"page_slug":"unleash-protocol","prev_score":55,"reason":"The core incident (about $3.9M lost through a multisig takeover and unauthorized upgrade, 1,337 ETH sent to Tornado Cash, operations paused, no recovery plan) is confirmed by independent outlets (claim_findings[0], [2], [3]). Two of six scored claims could not be verified: the 34-transaction, 11-12 hour Tornado Cash detail was not found in the sources read (claim_findings[1]), and the early-2024 launch and team description rests on an official docs page that now returns 404 (claim_findings[4], [5]). That puts the unverifiable share at about 33%, in the significant-issues band. Because the unverified items are peripheral, the penalty sits at the mild end of the band. One TVL claim was not scored because the source blocked the reviewer, which limits coverage but is not a defect of the page. The reviewer's confidence was moderate (0.55) and no omissions or status contradictions were found.","reviewer_def_hash":"bc11388ce4bc4deea1b064fea362663ae06e3f4f687f99604769044d6ffba770","score_delta":0,"scored_claims":6,"sequence_num":4,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}