Skip to main content
AVOID.NET
← avoid.net

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

  1. 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.
  2. 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.
  3. 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
#3
Score
0 → 0 (-10)
Cluster
mainnet-beta
Slot
443517569
Off-chain at
2026-08-25T22:21:45.232Z
Anchored at
—
Block time
—

Independent verification

1. Database (off-chain)
HUSHzecqwhVLwF9wSwyxjvwTGrdkB1rA4UyEYCszdbr3
2. Recomputed (your browser)
computing…
3. On-chain (Solana memo)
fetching…
Canonical bytes hashed (2457 chars)
{"actor":"judge","decided_at":"2026-08-25T22:21:45.040Z","decision":"review_revise","investigation_id":"0180d047-73a2-45da-9503-dfef6cc4ea9d","new_score":0,"page_slug":"q2-2026-defi-record-hack-wave","prev_score":0,"reason":"Of 38 fact-checked claims, 30 were confirmed against primary sources, 4 were disputed, and 4 were partially supported. Disputed claims come to 4/38 = 10.5%, which sits just above the 10% approval threshold, so this page is judged on the revise band rather than approved outright. None of the disputes touch the core allegations — the KelpDAO, Drift, Humanity Protocol, and THORChain hack narratives and their North Korea attributions all check out against primary sources (claim_findings[6]-[9], [11]-[15], [16]-[20], [21]-[22]). The disputed items are: a quoted phrase attributed to two named outlets that appears in neither (claim_findings[24]); a governance-migration date on the Drift page that is conflated with the later attack date (claim_findings[13]); a $14 billion DeFi-withdrawal figure correctly reported but wrongly attributed to CoinTribune instead of its actual source, which is already cited elsewhere on the page (claim_findings[30]); and a $1.3 million 'second Aztec Connect hack' figure that appears to be a duplicated Raydium figure, with the real second Aztec incident closer to $2.1-2.2 million (claim_findings[32]). Separately, the page's headline number — 83 incidents and $755 million in Q2 2026 losses — is the majority figure across outlets but is presented as settled when at least three credible sources, including one already in the page's own source list, report different totals (70-85 incidents, $746M-$775M) (claim_findings[0], [3]). A related TVL claim overstates how quickly Aave's TVL fell (claim_findings[29]), and a market-cap figure is not actually contained in its cited source (claim_findings[31]). None of the four coverage gaps are marked high priority, and the reviewer flagged a sibling AVOID.NET page covering the same quarter with unreconciled figures as a medium-priority, not urgent, issue. Taken together this supports revision rather than denial or clean approval: the page's core factual scaffolding holds, but its headline figure needs a caveat, several attributions need correcting, and it should be reconciled with the sibling page.","score_delta":-10,"sequence_num":3,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}