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
- #4
- Score
- 22 → 22 (0)
- Cluster
- mainnet-beta
- Slot
- 457771959
- Off-chain at
- 2026-10-16T20:33:25.706Z
- Anchored at
- 2026-10-16T20:33:30.056Z
- Block time
- —
Independent verification
- 1. Database (off-chain)
- JUUvBiWgtxkvp4CjRAVstJMviijSyJ5Z8kBk69qkiYn
- 2. Recomputed (your browser)
- computing…
- 3. On-chain (Solana memo)
- fetching…
Canonical bytes hashed (2121 chars)
{"actor":"reviewer","artifact_identity":"f91943ab0435cff26a83ef1aecd26bed","decided_at":"2026-10-16T20:33:25.248Z","decision":"review","disputed_pct":0.36,"findings_hash":"3q4wmVas6B3rJdKsN5ahPdNjoKA8L8Cm94GKBUDVn8om","investigation_id":"931907a8-d223-4aca-a200-3a427b25acf4","mode":"findings_only","new_score":22,"page_content_hash":"febd5cfd56162d286b9c48f35102b5c6493147ccd2520e7b38ada3e24aa8fce5","page_slug":"ctrl-wallet-security-exploit-and-forced-shutdown","prev_score":22,"reason":"The page's core narrative -- the June 21-23, 2026 SecondFi/Cardano signing-flaw exploit, the ~16.1M ADA / 374-address official loss figure, the two-attacker Groom Lake forensic breakdown with hedged Lazarus Group attribution, SlowMist's $20M exposure estimate, and the subsequent Ctrl Wallet and SecondFi/Yoroi shutdowns -- is well supported by official and independent reporting that was directly checked against the page's citations. However, the review found a factual date error (the shutdown was announced July 7, 2026, not July 9, repeated in both prose and the timeline), a mischaracterized quote attributed to Charles Hoskinson (his actual public comments distanced IOG from the incident rather than calling the loss 'modest'), a wrong month for the zero-knowledge recovery portal's launch (early September per two independent sources, not 'late August'), an internal inconsistency in the summary about permanent loss of access versus the page's own correct statement that recovery-phrase export remained available past the deadline, an unverifiable direct quote attributed to EMURGO's CEO, an unverifiable claim about a GitHub code leak that appears in two sections but could not be found in any credible source, and a mismatched Wayback Machine archive link. The most significant omission is that a credible independent on-chain reconstruction found a scope roughly 8-9x larger than the official figures the page presents as complete, which is not mentioned anywhere on the page.","score_delta":0,"sequence_num":4,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}