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
- #2
- Score
- 15 → 15 (0)
- Cluster
- mainnet-beta
- Slot
- 418855591
- Off-chain at
- 2026-05-10T15:44:07.804Z
- Anchored at
- —
- Block time
- —
Independent verification
- 1. Database (off-chain)
- 47S8WJ127FyuBdXLvyHsjmNSZrUmFXVxrgtpS1QgmiQz
- 2. Recomputed (your browser)
- computing…
- 3. On-chain (Solana memo)
- fetching…
Canonical bytes hashed (1835 chars)
{"actor":"judge","decided_at":"2026-05-10T15:44:07.573Z","decision":"review_approve","investigation_id":"3d2cc7b8-95f7-498d-b8b1-64ac61450e87","new_score":15,"page_slug":"drift","prev_score":15,"reason":"The reviewer evaluated 32 claims and found zero disputed by more credible sources, yielding a disputed_pct of 3.1%, well within the 0-10% approval band. All core allegations — the $285-286M exploit amount, April 1 date, DPRK attribution indicators, durable nonce attack mechanics, the Circle class-action filing, and the Tether recovery structure — are confirmed by Tier 1 sources including Chainalysis, Elliptic, BlockSec, Bloomberg, DL News, and official Drift Protocol communications. The four partially_supported findings (claim_findings[1], [6], [12], [24]) are marginal: the 'second-largest Solana hack' framing is confirmed by Elliptic; the lawsuit citation relies on a weak NatLawReview source but is independently corroborated; the CVT March 11 date in the section text is an internal inconsistency with the page's own timeline (which correctly states March 12 per Chainalysis); and the token ATL figure conflates a 24-hour low with a true all-time low. The one unverifiable claim (claim_findings[23], 70% token loss) is potentially overstated — available data supports approximately 54% — and the cited source index for it does not resolve to any source in the page's sources_used list, indicating a citation gap. One link rot instance exists (founding team domain 301 redirect) on a non-critical source. Two high-priority coverage gaps are noted (on-chain fund tracing, regulatory/law enforcement response) but these suggest expansion rather than inaccuracy in existing content.","score_delta":0,"sequence_num":2,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}