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
- 2 → 2 (0)
- Cluster
- mainnet-beta
- Slot
- 443519510
- Off-chain at
- 2026-08-26T06:07:02.217Z
- Anchored at
- —
- Block time
- —
Independent verification
- 1. Database (off-chain)
- EFH88opDVQvwJzoGRr94sYv7zfDFdsJe82NFfZiRY8FQ
- 2. Recomputed (your browser)
- computing…
- 3. On-chain (Solana memo)
- fetching…
Canonical bytes hashed (1073 chars)
{"actor":"reviewer","decided_at":"2026-08-26T06:07:02.017Z","decision":"review","investigation_id":"30fb1b89-f9c9-4690-8e88-091075aef49e","new_score":2,"page_slug":"kelpdao-layerzero-bridge-exploit-april-2026-dprk-lazarus","prev_score":2,"reason":"The large majority of claims on this page are corroborated by the cited or independently located sources, and the page notably handles the LayerZero/KelpDAO blame dispute and the DPRK subgroup attribution with appropriate hedging and balance rather than presenting either as settled fact. Three claims are disputed: an overstated Aave borrow amount ($236M vs. ~$190M reported elsewhere), an internally inconsistent Arbitrum freeze figure ($75M vs. the correct $71M stated two sentences earlier in the same paragraph), and a THORChain laundering statistic ($1.2B/85%) that appears to be misattributed from the 2025 Bybit hack rather than the 2026 KelpDAO/Drift total it is applied to.","score_delta":0,"sequence_num":2,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}