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 · Q2 2026 Record Crypto Hack Wave
- Sequence
- #2
- Score
- 0 → 0 (0)
- Cluster
- mainnet-beta
- Slot
- 443517416
- Off-chain at
- 2026-08-25T22:19:41.028Z
- Anchored at
- —
- Block time
- —
Independent verification
- 1. Database (off-chain)
- 74UPCx78EjAW9NbDvusABtgMLTfXxCM33RFfMkaJju2n
- 2. Recomputed (your browser)
- computing…
- 3. On-chain (Solana memo)
- fetching…
Canonical bytes hashed (1299 chars)
{"actor":"reviewer","decided_at":"2026-08-25T22:19:40.888Z","decision":"review","investigation_id":"f7b62b47-2118-46e9-8025-4f381f47211f","new_score":0,"page_slug":"q2-2026-record-crypto-hack-wave","prev_score":0,"reason":"The large majority of quantitative claims in this page -- the 83-incident/$755.3M headline, the KelpDAO and Drift Protocol loss figures and mechanics, the THORChain and Humanity Protocol incidents, the bridge-loss aggregates, and the year-by-year DPRK hack-share percentages -- were independently corroborated against primary or high-credibility secondary sources. The most significant defect found is that the page's own cited source (TRM Labs) explicitly attributes the Drift Protocol and KelpDAO exploits to two different North Korean subgroups, while the page's summary and 'North Korean State Attribution' section incorrectly merge both into a single 'TraderTraitor subunit (UNC4736)' attribution. A separate sourcing error was found in the OFAC citation, which points to an unrelated 2019 Treasury press release rather than the March 2026 action it is meant to support, though the underlying factual claim is independently true.","score_delta":0,"sequence_num":2,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}