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 · Zoth Protocol
- Sequence
- #5
- Score
- 18 → 8 (-10)
- Cluster
- mainnet-beta
- Slot
- 423876168
- Off-chain at
- 2026-06-02T19:49:55.129Z
- Anchored at
- —
- Block time
- —
Independent verification
- 1. Database (off-chain)
- 6ewS2ozXtsjcMxMrRsCqgDeEjJRTYecWuduEN7Bg2Bxw
- 2. Recomputed (your browser)
- computing…
- 3. On-chain (Solana memo)
- fetching…
Canonical bytes hashed (1434 chars)
{"actor":"judge","decided_at":"2026-06-02T19:49:54.885Z","decision":"review_revise","investigation_id":"4a736de8-81d9-4b63-944d-32ddd8b0ff17","new_score":8,"page_slug":"zoth-protocol","prev_score":18,"reason":"The core facts of both March 2025 exploits — loss amounts, on-chain addresses, attack mechanics, and fund flows — are well-confirmed by multiple independent Tier 2 security research sources, and zero claims are actively contradicted by a more credible source. However, the reviewer identified several issues requiring correction: claim_findings[25] (timeline entry 11) places the 'Next Chapter' press release on April 1, 2025, but the PR Newswire release is dated May 9, 2025, making this a material date error in the timeline; claim_findings[16] (Bolts Capital $15M) is partially supported but its April 1 timeline placement is similarly unsupported — the formal announcement did not occur until August 2025. Additionally, claim_findings[11] (LTV vulnerability flagged in a prior audit) is unverifiable from any consulted source, including the primary cited Verichains article. Two high-priority coverage gaps — the page is effectively 14 months stale with no events past April 2025, and the pre-incident audit history is absent — further support a revision rather than approval.","score_delta":-10,"sequence_num":5,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}