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
- #4
- Score
- 22 → 22 (0)
- Cluster
- mainnet-beta
- Slot
- 418776279
- Off-chain at
- 2026-05-10T06:52:12.303Z
- Anchored at
- —
- Block time
- —
Independent verification
- 1. Database (off-chain)
- 2zi9XzZGf7JL84j16gbio2n9sAKrz69mGvbsUBQXw8Xv
- 2. Recomputed (your browser)
- computing…
- 3. On-chain (Solana memo)
- fetching…
Canonical bytes hashed (1430 chars)
{"actor":"judge","decided_at":"2026-05-10T06:52:12.119Z","decision":"review_approve","investigation_id":"50227794-5b4a-4d07-97d3-2fae3507b3e0","new_score":22,"page_slug":"drift-protocol","prev_score":22,"reason":"The reviewer evaluated 31 claims and found zero disputed findings, 24 confirmed, 5 partially supported, and 1 unverifiable, yielding a disputed_pct of 3.2% — well within the 0-10% approval threshold. All core allegations about the April 2026 exploit amount, UNC4736/DPRK attribution at medium-high confidence, CCTP laundering path, Tether rescue package, and class action filing are confirmed by Tier 1 sources including Chainalysis, Elliptic, TRM Labs, Bloomberg, and CoinDesk. The most significant editorial issue is an internal inconsistency in claim_findings[10]: the page combines '12 minutes' (describing the 31 withdrawal transactions per TRM Labs) with the stated drain window of 16:05-18:31 UTC (approximately 2.5 hours), which refer to different attack phases and should be disambiguated. The NYDFS video verification claim (claim_findings[30]) remains unverifiable against a primary regulatory document and should either be directly sourced or qualified as a secondary characterization. No link rot, stale citations, or high-priority coverage gaps were identified.","score_delta":0,"sequence_num":4,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}