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
- Sequence
- #2
- Score
- 8 → 8 (0)
- Cluster
- mainnet-beta
- Slot
- 443511803
- Off-chain at
- 2026-08-25T04:06:11.249Z
- Anchored at
- —
- Block time
- —
Independent verification
- 1. Database (off-chain)
- 7djkE2nz9bE6t9iP82r2yVYsLNWfGTh9YqMcur2E37Sd
- 2. Recomputed (your browser)
- computing…
- 3. On-chain (Solana memo)
- fetching…
Canonical bytes hashed (1363 chars)
{"actor":"reviewer","decided_at":"2026-08-25T04:06:11.043Z","decision":"review","investigation_id":"19358cad-4557-4394-a860-f6a360b42cc6","new_score":8,"page_slug":"drift-protocol-dprk-exploit-april-2026","prev_score":8,"reason":"Of 44 atomic claims checked, 29 were confirmed against cited or independently located sources, 6 were partially supported (source exists but the page omits material context, e.g. the multisig threshold's origin and the ambiguity in the 'largest DeFi hack of 2026' ranking), 2 was disputed (the ~130,259 ETH holding is mis-valued by roughly 10x -- the page's own cited source states ~$293 million, not the ~$31 million given -- and a timeline date field internally contradicts its own event description), 1 is stale (the Q2 2026 relaunch target has since moved to Q3 2026 with a rebrand to 'Velocity', not reflected in the page), and 6 could not be independently confirmed or refuted in the time available. The core narrative -- exploit mechanics, dollar losses, medium-high-confidence DPRK/UNC4736 attribution, and recovery-plan terms -- is well supported by multiple independent outlets and the page is careful to characterize the DPRK attribution as an assessed, not confirmed, conclusion.","score_delta":0,"sequence_num":2,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}