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
- 0 → 0 (0)
- Cluster
- mainnet-beta
- Slot
- 464787584
- Off-chain at
- 2026-11-03T05:51:23.760Z
- Anchored at
- 2026-11-03T05:51:42.000Z
- Block time
- 2026-11-03T05:51:42.000Z
Independent verification
- 1. Database (off-chain)
- CrDJZRJyVpCf8LV3wm1oPbt52dHqMqPLFxNYajbXnQen
- 2. Recomputed (your browser)
- computing…
- 3. On-chain (Solana memo)
- fetching…
Canonical bytes hashed (1334 chars)
{"actor":"reviewer","artifact_identity":"f3f17597f3a2e4d2ac910cd62d42d132","blocked_count":1,"decided_at":"2026-11-03T05:51:23.664Z","decision":"review","disputed_pct":0.1,"findings_hash":"BNHPZ3ojWQA8MM9f8wPoAzSDEDoG3R7tzxPPMsLfMgD6","investigation_id":"0026323b-3794-4aa0-8930-94def1a21240","judge_def_hash":"8800307026131ea9d5da939d32b9a1f1884b2b84a5de33c8e87931d36f38d0f8","new_score":0,"omissions":{"material":0,"total":1},"page_content_hash":"9b93e4014d344b774d68da3bf73a4237e6ceb452c5eb6ccf81e5a8b79e8c66a3","page_slug":"dprk-it-worker-network-ofac-march-2026-designations","prev_score":0,"reason":"The page is largely accurate against the Treasury release and TRM. It hedges unverified figures openly. The main defect is that the Oct 2026 Obertas claim, in the prose and the timeline, cites a TRM post about an Aug 2025 action. The event itself is real. Some nationality tags (Vietnam) are not in the release text I read. I did not check the Scorechain, NK News, The Block, The Record or GlobalSecurity pages.","reviewer_def_hash":"bc11388ce4bc4deea1b064fea362663ae06e3f4f687f99604769044d6ffba770","score_delta":0,"scored_claims":10,"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}