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 Capital
- Sequence
- #4
- Score
- 18 → 18 (0)
- Cluster
- mainnet-beta
- Slot
- 462042367
- Off-chain at
- 2026-10-27T10:48:16.553Z
- Anchored at
- 2026-10-27T10:48:35.000Z
- Block time
- 2026-10-27T10:48:35.000Z
Independent verification
- 1. Database (off-chain)
- 5oDCMDDHyxawKDcrX2svvTzTnfv7L6a4HP77HB1vdFW2
- 2. Recomputed (your browser)
- computing…
- 3. On-chain (Solana memo)
- fetching…
Canonical bytes hashed (1222 chars)
{"actor":"reviewer","artifact_identity":"402ce9f4411dc175c87ac4ed14aa32b4","decided_at":"2026-10-27T10:48:16.349Z","decision":"review","disputed_pct":0.3,"findings_hash":"33tbohpDSCeAFgaqSbta4f2AoLiCh7hcwtGSHyEhJpvk","investigation_id":"2cf92517-f3d5-4d4e-ad0a-dcf16473b155","judge_def_hash":"8800307026131ea9d5da939d32b9a1f1884b2b84a5de33c8e87931d36f38d0f8","new_score":18,"omissions":{"material":1,"total":1},"page_content_hash":"4bd16b353b7ced44f05468c4ce8f5e7b69531d60403a002118a4e86f2eab0f06","page_slug":"radiant-capital","prev_score":18,"reason":"Core incident facts (Jan 2024 exploit, Oct 2024 multisig compromise, UNC4736 attribution, 3-of-11 multisig, Tornado Cash laundering) are supported. Some specifics (Sept 11 date, 4-of-7 change, six seconds) could not be verified, and the Mandiant attribution date is off. The page omits the June 2026 wind-down, which makes its current-status section stale and misleading.","reviewer_def_hash":"bc11388ce4bc4deea1b064fea362663ae06e3f4f687f99604769044d6ffba770","score_delta":0,"sequence_num":4,"subject_status":"shut_down","subject_status_contradicts_page":true,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}