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 · Ledger
- Sequence
- #3
- Score
- 58 → 53 (-5)
- Cluster
- mainnet-beta
- Slot
- 425235599
- Off-chain at
- 2026-06-09T02:17:00.194Z
- Anchored at
- —
- Block time
- —
Independent verification
- 1. Database (off-chain)
- 2G98QvgwXnoVbUYRH1532ZX71XiMUQWtyDDpsJuaAY9D
- 2. Recomputed (your browser)
- computing…
- 3. On-chain (Solana memo)
- fetching…
Canonical bytes hashed (1188 chars)
{"actor":"judge","decided_at":"2026-06-09T02:16:59.953Z","decision":"review_revise","investigation_id":"03d5d83f-6247-4200-998e-048db3536286","new_score":53,"page_slug":"ledger","prev_score":58,"reason":"The reviewer verified 31 claims and found zero actively disputed by opposing sources. 23 were fully confirmed by Tier 1 sources. The five partially_supported findings (claim_findings[10], [11], [20], [24], [25]) reflect methodology variance in loss estimates, a minor USD conversion discrepancy, and editorial omissions — none contradict core allegations. One stale finding (claim_findings[26]) is the most material issue: the page states Ledger was evaluating a US IPO above $4 billion as of early 2026, but as of May 2026 Ledger paused those plans indefinitely; this factual development is missing from the page. One unverifiable ARR figure (claim_findings[27]) traces only to a self-reported data aggregator with no Tier 1 corroboration. These items do not impugn the page's core security incident record but require editorial correction.","score_delta":-5,"sequence_num":3,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}