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
- Sequence
- #5
- Score
- 40 → 40 (0)
- Cluster
- mainnet-beta
- Slot
- 462172130
- Off-chain at
- 2026-10-27T18:28:04.057Z
- Anchored at
- 2026-10-27T18:28:36.000Z
- Block time
- 2026-10-27T18:28:36.000Z
Independent verification
- 1. Database (off-chain)
- 9aMNzmSWvVcptAkJpMGGHEAb2ef1DMRr6j8GqHrmZEie
- 2. Recomputed (your browser)
- computing…
- 3. On-chain (Solana memo)
- fetching…
Canonical bytes hashed (1415 chars)
{"actor":"reviewer","artifact_identity":"9bfb4c495e71b1ac8256b1ac252dcf12","decided_at":"2026-10-27T18:28:03.888Z","decision":"review","disputed_pct":0.2,"findings_hash":"5p4EK84REdjdH2EfoniQLyrPTFaSYb6oHqNkzs87vBkq","investigation_id":"1d7658b7-0313-4731-ba92-f248c161629d","judge_def_hash":"8800307026131ea9d5da939d32b9a1f1884b2b84a5de33c8e87931d36f38d0f8","new_score":40,"omissions":{"material":0,"total":1},"page_content_hash":"22114cab52fce6621b73fde7eb025faaf9432d8a51c3d15673c86182f680ba94","page_slug":"zcash-orchard-pool-counterfeiting-bug","prev_score":40,"reason":"The core factual narrative is well supported: May 29 discovery by Hornby with Opus 4.8, June 1-2 emergency fixes with accurate block heights and Zebra versions, price figures, and the July 28 Ironwood activation. The page candidly flags source discrepancies. Weak points are the exact public disclosure date (June 3 vs June 4 per differing sources), an unsupported Foundation turnstile-accounting attribution, and a muddled 'Sapling-successor' phrase. Not all cited sources (AMBCrypto, Defiant, Unchained, SEC-related, ForkLog) were fetched.","reviewer_def_hash":"bc11388ce4bc4deea1b064fea362663ae06e3f4f687f99604769044d6ffba770","score_delta":0,"sequence_num":5,"subject_status":"operating","subject_status_contradicts_page":false,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}