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 · Drift Protocol
- Sequence
- #6
- Score
- 22 → 52 (+30)
- Cluster
- mainnet-beta
- Slot
- 426514247
- Off-chain at
- 2026-06-14T23:15:46.566Z
- Anchored at
- —
- Block time
- —
Independent verification
- 1. Database (off-chain)
- B7Lrr5v8AHCfEXZYBjVHcoJtaDseF7CA1z6AmK1FmeVQ
- 2. Recomputed (your browser)
- computing…
- 3. On-chain (Solana memo)
- fetching…
Canonical bytes hashed (1466 chars)
{"actor":"judge","decided_at":"2026-06-14T23:15:46.443Z","decision":"review_approve","investigation_id":"3d2cc7b8-95f7-498d-b8b1-64ac61450e87","new_score":52,"page_slug":"drift","prev_score":22,"reason":"This is a severity-calibration adjudication. The page content is accurate — all six claim findings are supported (claim_findings[0] through claim_findings[5]) — and 0% of claims are disputed. The current score of 22/WARNING misclassifies Drift Protocol alongside scam and exit-fraud entities, directly contradicting the page's own 'VERIFIED (via DefiLlama)' status (claim_findings[0]). The $285M April 2026 loss was a DPRK/UNC4736 state-sponsored social engineering attack independently confirmed by Chainalysis, TRM Labs, Elliptic, Bloomberg, and CoinDesk; Drift was the victim, not the perpetrator (claim_findings[1]). A partial-negligence deduction is warranted for the zero-timelock Security Council migration five days before the exploit (claim_findings[3]), and the unresolved eight-year user recovery timeline is a material ongoing caveat (claim_findings[4]). These factors together support CAUTIONARY (52) rather than VERIFIED, but emphatically not WARNING (22). The reviewer's recommended score of 52 and +30 delta are well-grounded; reviewer confidence is 0.88. The page stays published with no status change.","score_delta":30,"sequence_num":6,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}