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.
- Sequence
- #2
- Score
- 0 → 0 (0)
- Cluster
- mainnet-beta
- Slot
- 443519333
- Off-chain at
- 2026-08-26T05:08:26.645Z
- Anchored at
- —
- Block time
- —
Independent verification
- 1. Database (off-chain)
- 8Hiz26ceykPNw4Ag2pwCjfNknoZUhenBB46u2xe54MvA
- 2. Recomputed (your browser)
- computing…
- 3. On-chain (Solana memo)
- fetching…
Canonical bytes hashed (1382 chars)
{"actor":"reviewer","decided_at":"2026-08-26T05:08:26.428Z","decision":"review","investigation_id":"684bbcae-ea55-4172-b244-30907016bf98","new_score":0,"page_slug":"h1-2026-crypto-hack-landscape-ai-agent-attack-vector-emerges","prev_score":0,"reason":"The large majority of quantitative claims on this page -- incident counts, dollar totals, and firm-specific breakdowns from Blockaid, TRM Labs, and CertiK -- were independently confirmed against primary reports and multiple secondary outlets, and the page is generally careful to attribute figures to the specific firm that produced them. Issues found include: two disputed claims (a timeline entry conflating the April 14, 2026 CoW Swap DNS hijacking with an unrelated March 12, 2026 MEV/execution-failure event that was not a security breach, and an arithmetic error stating Europe accounted for 79.6% of wrench-attack incidents when the cited 39-of-52 figure equals 75.0%); an unsourced 'first documented production EIP-7702 drain' superlative not present in any cited source; an EIP-7702 malicious-delegation statistic drawn from mid-2025 Wintermute/GoPlus research presented without noting its earlier origin; and an omission of KelpDAO's public dispute of LayerZero's blame framing.","score_delta":0,"sequence_num":2,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}