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
- 50 → 50 (0)
- Cluster
- mainnet-beta
- Slot
- 457565721
- Off-chain at
- 2026-10-16T08:10:16.613Z
- Anchored at
- 2026-10-16T08:10:31.667Z
- Block time
- —
Independent verification
- 1. Database (off-chain)
- Eg1rJWeoX8ctUJU41RsWqY3XwD71PvfQJw737Zt4Tc4S
- 2. Recomputed (your browser)
- computing…
- 3. On-chain (Solana memo)
- fetching…
Canonical bytes hashed (1634 chars)
{"actor":"reviewer","artifact_identity":"dce3f9719a2572d73e0e56759eff8c06","decided_at":"2026-10-16T08:10:16.453Z","decision":"review","disputed_pct":0.25,"findings_hash":"A3MxntTqtYZmAhR9g12raFnVWkeAwTmxfDQUYYQedTXN","investigation_id":"af4b83b2-f0cf-4a10-835e-9210b2b08166","mode":"findings_only","new_score":50,"page_content_hash":"f8df3b0031220dd2beb7980fdea9627cb69f4d56c8f2482c5dc982fdf0d45f17","page_slug":"0xdf8c3a7ffbdc144f462687120e4ae4c4e5e55abe","prev_score":50,"reason":"This is a minimal, low-stakes page about a dormant Ethereum EOA with zero transaction history, and its core claims hold up well: live re-verification on Etherscan confirms 0 ETH balance, 0 transactions, EOA status, and no name tags or ENS name, and an independent web search for the bare address string turned up nothing, consistent with the page's negative findings across OFAC, ChainAbuse, SEC/DOJ and Arkham. The one concrete factual slip is the claim that Etherscan's multichain portfolio tool covers '33+ chains' — it currently shows 31. Several negative-result claims (Ethplorer history, ChainAbuse reports, Arkham attribution) could not be independently re-run due to JS rendering or access gating, so they are marked unverifiable rather than confirmed, though nothing contradicts them. No accepted community submissions exist to cross-check. The page appropriately hedges its own limitations (proprietary tools not queried, trust score framed as a neutral baseline) rather than overstating certainty.","score_delta":0,"sequence_num":4,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}