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_approve · Zabu Finance
- Sequence
- #3
- Score
- 18 → 52 (+34)
- Cluster
- mainnet-beta
- Slot
- 426700984
- Off-chain at
- 2026-06-15T19:50:05.174Z
- Anchored at
- —
- Block time
- —
Independent verification
- 1. Database (off-chain)
- BJhzW1or5ePLnJPX26MfHjDs12XqREgqkSqsUY5wpL3U
- 2. Recomputed (your browser)
- computing…
- 3. On-chain (Solana memo)
- fetching…
Canonical bytes hashed (1534 chars)
{"actor":"judge","decided_at":"2026-06-15T19:50:04.967Z","decision":"review_approve","investigation_id":"165277a4-bd68-46b8-92c0-11ffcadf8ec3","new_score":52,"page_slug":"zabu-finance","prev_score":18,"reason":"Zero of 19 claims were disputed by a more credible source. The two unverifiable claims (specific SSL expiry date in claim_findings[8] and claim_findings[15]) relate to a minor operational detail that does not affect the core incident record. Three partially-supported claims involve a digit transposition in a token burn figure (claim_findings[14]) and a timeline date offset of 27 days for the PolyYeld precedent event (claim_findings[9]) — neither materially misrepresents the incident. The page's core factual record — the $3.2M flash loan exploit, its mechanism, date, DEXes involved, and the 'first Avalanche DeFi hack' characterization — is confirmed by Tier 1 and Tier 2 sources including CoinDesk, Halborn, and SlowMist. High-priority coverage gaps (empty section content fields, misplaced ZachXBT citation) indicate structural authoring issues that warrant future revision but do not undermine the accuracy of the published claims. The current trust score of 18 (CRITICAL) is a miscalibration: all incidents are classified as suffered (type b), which caps at CAUTIONARY under the scoring rubric, and the reviewer's recommended score of 52 is consistent with the evidence.","score_delta":34,"sequence_num":3,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}