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_revise · SecondFi (Cardano Wallet)
- Sequence
- #3
- Score
- 28 → 13 (-15)
- Cluster
- mainnet-beta
- Slot
- 443506788
- Off-chain at
- 2026-08-10T18:52:41.756Z
- Anchored at
- —
- Block time
- —
Independent verification
- 1. Database (off-chain)
- J9XAj7PsCvbqWzYsy4QkKzjbAC6XJKFyJwdU9CdsSkJe
- 2. Recomputed (your browser)
- computing…
- 3. On-chain (Solana memo)
- fetching…
Canonical bytes hashed (1737 chars)
{"actor":"judge","decided_at":"2026-08-10T18:52:41.480Z","decision":"review_revise","investigation_id":"fdd3c427-bdd2-4ada-af57-b950be89225b","new_score":13,"page_slug":"secondfi-cardano-wallet","prev_score":28,"reason":"The page's central narrative -- a June 21-23, 2026 nonce-derivation exploit that drained about 16 million ADA (~$2.4 million) from 374 SecondFi/Yoroi wallets, with SlowMist flagging up to $20 million in broader exposure -- holds up against Tier 1 and Tier 2 reporting (claim_findings[0], [1], [2], [6]). However, the review found the page's on-chain forensic breakdown is internally inconsistent: the attacker-wave wallet counts don't add up against the source's own attacker-level totals (claim_findings[8]), and the page understates the combined ADA moved across both waves by roughly 9% by presenting a wave-2-only subtotal as the grand total (claim_findings[9]). More significantly, the page's 'unresolved questions' framing is stale relative to its own cited source archive dates: it omits EMURGO's July 22, 2026 announcement that SecondFi will not reopen and is shifting to a recovery-only operation, along with a published (if since-extended) recovery timeline (claim_findings[3], [13], [18]). This is flagged as a high-priority coverage gap. A quoted line attributed to Bitquery is also a paraphrase presented in quotation marks rather than the source's verbatim wording (claim_findings[7]). None of these issues undermine the core factual claims, but together they represent more than trivial inaccuracy and warrant revision before the page is treated as current.","score_delta":-15,"sequence_num":3,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}