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_revise · Zcash
- Sequence
- #3
- Score
- 62 → 50 (-12)
- Cluster
- mainnet-beta
- Slot
- 425191268
- Off-chain at
- 2026-06-08T21:22:33.110Z
- Anchored at
- —
- Block time
- —
Independent verification
- 1. Database (off-chain)
- EC9D5ncNoiux9APLiqoU7jctfr2x6iTKTDZQy8WQAtaw
- 2. Recomputed (your browser)
- computing…
- 3. On-chain (Solana memo)
- fetching…
Canonical bytes hashed (1369 chars)
{"actor":"judge","decided_at":"2026-06-08T21:22:32.971Z","decision":"review_revise","investigation_id":"c74f94ee-608e-40f1-ba08-8dde9224dc41","new_score":50,"page_slug":"zcash","prev_score":62,"reason":"The review confirmed 26 of 35 claims outright, with the remaining 6 rated partially supported rather than disputed — none were directly contradicted. However, claim_findings[22] (the assertion that the 2022 Halo 2/Orchard upgrade eliminated the counterfeiting-vulnerability class going forward) is materially overstated: a distinct Orchard circuit soundness flaw discovered on May 29, 2026 required an emergency NU6.2 hard fork on June 3, 2026, disproving the 'eliminated this class' language on a section the page itself marks severity: critical. The high-priority coverage gap for this NU6.2 event — entirely absent from the page despite a 30%+ price impact — directly undermines a security claim and warrants revision before the page is treated as current. Additionally, the May 2026 market figures in claim_findings[1] have become materially stale (price down roughly 30% to ~$438 by review date). All other partial-support findings are minor wording or precision issues that do not affect the page's overall accuracy.","score_delta":-12,"sequence_num":3,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}