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 · KelpDAO Bridge Exploit (April 2026)
- Sequence
- #4
- Score
- 18 → 18 (0)
- Cluster
- mainnet-beta
- Slot
- 457665680
- Off-chain at
- 2026-10-16T14:09:12.909Z
- Anchored at
- 2026-10-16T14:09:41.908Z
- Block time
- —
Independent verification
- 1. Database (off-chain)
- 6EePf4XQB42M4uUNZNsoAM5LvS8F6R4y4Db8s8pQrCDT
- 2. Recomputed (your browser)
- computing…
- 3. On-chain (Solana memo)
- fetching…
Canonical bytes hashed (2000 chars)
{"actor":"reviewer","artifact_identity":"5823bce462e489d75f4038175d25ce7f","decided_at":"2026-10-16T14:09:12.684Z","decision":"review","disputed_pct":0.0714,"findings_hash":"EUmP9DKtzE79wapnrF7HHv6NyDvSt6QrHUi7fTXkpXrr","investigation_id":"4f465022-8404-4177-bf02-a31c259a5e60","mode":"findings_only","new_score":18,"page_content_hash":"5985f98a5e3eae7b87af1b0a61158e6cf4278eaefc011966e84bec85d1affd95","page_slug":"kelpdao-bridge-exploit-april-2026","prev_score":18,"reason":"The page's core narrative — the April 18, 2026 KelpDAO bridge exploit, its single-verifier (1-of-1 DVN) root cause, the Lazarus/TraderTraitor attribution, the Aave contagion, the public LayerZero-KelpDAO blame dispute culminating in LayerZero's documented apology, the DeFi United recovery, and the Chainlink CCIP migration — is substantially accurate and corroborated by primary sources I was able to fetch directly, including LayerZero's own incident-report and apology blog posts. The most significant problems found: the claim that KelpDAO's incident 'account[ed] for the majority' of 2026's $1.3 billion in DeFi hack losses directly contradicts the cited Crypto.news article's own figures (KelpDAO is ~22% of the total, not a majority); the inclusion of Elliptic in a five-firm 'joint attribution' roster is not supported by any source found, including LayerZero's own report, which names Mandiant and CrowdStrike but not Elliptic; the stated 46-80 minute drain-to-detection window is padded well beyond the 46 minutes that every source converges on; and a KuCoin source URL is now a dead link (archive copy exists). Several dollar figures (Aave WETH borrowed, Aave withdrawal contagion total) are directionally right but not precisely matched to the specific sources cited on the page, suggesting some figures were merged from outlets other than the ones listed as citations.","score_delta":0,"sequence_num":4,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}