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 · Drift Trade
- Sequence
- #2
- Score
- 10 → 0 (-12)
- Cluster
- mainnet-beta
- Slot
- 418756683
- Off-chain at
- 2026-05-10T04:40:46.316Z
- Anchored at
- —
- Block time
- —
Independent verification
- 1. Database (off-chain)
- EYo3gMhW8TCgYn9n3YFZjDsvCc9jAQFyn1DdzJXcgMPv
- 2. Recomputed (your browser)
- computing…
- 3. On-chain (Solana memo)
- fetching…
Canonical bytes hashed (1388 chars)
{"actor":"judge","decided_at":"2026-05-10T04:40:46.125Z","decision":"review_revise","investigation_id":"6c0e3163-225d-4120-a3c9-f112d15456a4","new_score":0,"page_slug":"drift-trade","prev_score":10,"reason":"The core factual record — two incidents on Solana, $14.5M in May 2022 and approximately $285M on April 1, 2026 — is substantiated by multiple Tier 1 sources including Chainalysis, TRM Labs, and Elliptic, so the page is not denied. However, three structural issues require revision before the page is in good standing. First, the entity name 'Drift Trade' used throughout the page (including the slug and all headings) is a DeFiLlama sub-brand label, not the canonical name — every authoritative source including the protocol's own incident reports uses 'Drift Protocol' (claim_findings[0], claim_findings[4]). Second, the sole cited source URL returns HTTP 403 across all sections, the timeline, and sources_used, meaning no live citation is currently resolvable on the page (claim_findings[6]). Third, the DPRK/Lazarus Group (UNC4736) attribution for the 2026 incident — confirmed by three Tier 1 blockchain analytics firms — is entirely absent, a high-priority omission that materially understates the risk profile (coverage_gaps[1]).","score_delta":-12,"sequence_num":2,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}