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_approve · Mass Address Poisoning Campaign (Ethereum 2025-2026)
- Sequence
- #3
- Score
- 0 → 0 (0)
- Cluster
- mainnet-beta
- Slot
- 426249541
- Off-chain at
- 2026-06-13T18:03:41.462Z
- Anchored at
- —
- Block time
- —
Independent verification
- 1. Database (off-chain)
- GcREYZUAMsf4usPzfPEQufLLYywq77BqTq8nYWLc89W9
- 2. Recomputed (your browser)
- computing…
- 3. On-chain (Solana memo)
- fetching…
Canonical bytes hashed (1567 chars)
{"actor":"judge","decided_at":"2026-06-13T18:03:40.616Z","decision":"review_approve","investigation_id":"4f53560f-9177-4599-9e66-fbe56adbef66","new_score":0,"page_slug":"mass-address-poisoning-campaign-ethereum-2025-2026","prev_score":0,"reason":"The reviewer examined 26 claims and found 18 confirmed, 5 partially supported, and 1 unverifiable — yielding a disputed_pct of 3.8%, well within the 0–10% approval band. All core allegations (Fusaka upgrade date and fee reduction, the December 2025 $50M theft sequence, the January 2026 $12.4M OTC incident, Blockaid's aggregated volume statistics, and the Tsuchiya et al. academic dataset) are confirmed by Tier 1 or consistent Tier 2 sources. The five partially-supported findings involve minor rounding differences, a six-day publication date discrepancy (claim_findings[21]), a characterization of the May 2024 WBTC recovery as 'partial' when sources indicate near-complete return (claim_findings[22]), and a $185K single-transaction advertisement verified only through Blockaid's own blog (claim_findings[3]). The one unverifiable claim (claim_findings[10], specific daily dust transaction counts) is a secondary supporting metric, not a core allegation. No Tier 1 source disputes any claim. One high-priority coverage gap — absence of on-chain wallet cluster analysis for campaign operators — is noted for future expansion but does not impair the page's factual integrity.","score_delta":0,"sequence_num":3,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}