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.
- Sequence
- #3
- Score
- 71 → 71 (0)
- Cluster
- mainnet-beta
- Slot
- 462184714
- Off-chain at
- 2026-10-27T19:12:40.815Z
- Anchored at
- 2026-10-27T19:13:07.000Z
- Block time
- 2026-10-27T19:13:07.000Z
Independent verification
- 1. Database (off-chain)
- dAEAfoBbyoSPYMSPc71LnvvngQRrj8RxtP7FQCNkkhS
- 2. Recomputed (your browser)
- computing…
- 3. On-chain (Solana memo)
- fetching…
Canonical bytes hashed (1430 chars)
{"actor":"reviewer","artifact_identity":"bfd14ffa31d968b46fdebd6c53fe36bd","blocked_count":3,"decided_at":"2026-10-27T19:12:40.690Z","decision":"review","disputed_pct":0,"findings_hash":"ErqumMUJK57tboiNSq9Dcwubmybv2saoAZCNyjW54mSd","investigation_id":"27995d3d-bbc0-4136-a46a-dc9c09762ae7","judge_def_hash":"8800307026131ea9d5da939d32b9a1f1884b2b84a5de33c8e87931d36f38d0f8","new_score":71,"omissions":{"material":0,"total":2},"page_content_hash":"129f7c2dd4d3c4d3c70527f5c96cf840d18aca296d5369fa309d3b809f991d91","page_slug":"zcash-ironwood-shielded-pool-dprk-laundering-vector","prev_score":71,"reason":"The Bitget loss figure, the attack chain, the NEAR SHIELD amounts, the 2,746 ZEC deposit and the Chainalysis statistics are supported by sources I could read. The page hedges attribution appropriately. Several specifics could not be checked because the primary CryptoTimes source was blocked: the 08:15-08:46 UTC window, the t-address, the alias handles and the Ironwood block height. Two sources_used archive URLs point to unrelated articles. The page stops at Oct 1 and does not reflect later developments.","reviewer_def_hash":"bc11388ce4bc4deea1b064fea362663ae06e3f4f687f99604769044d6ffba770","score_delta":0,"scored_claims":7,"sequence_num":3,"subject_status":"operating","subject_status_contradicts_page":false,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}