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 · Radiant V2
- Sequence
- #3
- Score
- 54 → 54 (0)
- Cluster
- mainnet-beta
- Slot
- 464298852
- Off-chain at
- 2026-11-02T00:46:35.593Z
- Anchored at
- 2026-11-02T00:46:54.000Z
- Block time
- 2026-11-02T00:46:54.000Z
Independent verification
- 1. Database (off-chain)
- AadxYrJSKb8JMVveP3cq6oVx2mGPKuQc4vXvszqYqu64
- 2. Recomputed (your browser)
- computing…
- 3. On-chain (Solana memo)
- fetching…
Canonical bytes hashed (1343 chars)
{"actor":"reviewer","artifact_identity":"30b72a3838576f6d81773288fb7e1de5","blocked_count":1,"decided_at":"2026-11-02T00:46:35.526Z","decision":"review","disputed_pct":0.1429,"findings_hash":"ECuh1AKsfN6dBMabfghCXTfmg3TK1beVft9CectVswNx","investigation_id":"7d00d907-ddca-4513-9bdc-f3e52a5766e5","judge_def_hash":"8800307026131ea9d5da939d32b9a1f1884b2b84a5de33c8e87931d36f38d0f8","new_score":54,"omissions":{"material":1,"total":1},"page_content_hash":"751e445d8dbcd32e997f3ccf6c705f9121313d1f3cf735897dc5c79382851201","page_slug":"radiant-v2","prev_score":54,"reason":"The core incident facts hold: the Jan 2024 exploit, the Oct 16, 2024 multisig compromise on BSC and Arbitrum, the 3-of-11 threshold, and the Dec 2024 UNC4736 attribution. The page omits the June 2026 wind-down announcement, which is critical and makes some wording stale. Some granular technical details could not be checked because Radiant's primary posts were blocked, and 'sanctioned' for Tornado Cash may be outdated. Only a sample of claims was checked.","reviewer_def_hash":"bc11388ce4bc4deea1b064fea362663ae06e3f4f687f99604769044d6ffba770","score_delta":0,"scored_claims":7,"sequence_num":3,"subject_status":"shut_down","subject_status_contradicts_page":true,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}