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 · Zano (ZANO)
- Sequence
- #3
- Score
- 28 → 26 (-2)
- Cluster
- mainnet-beta
- Slot
- 462185900
- Off-chain at
- 2026-10-27T19:16:58.790Z
- Anchored at
- 2026-10-27T19:17:20.000Z
- Block time
- 2026-10-27T19:17:20.000Z
Independent verification
- 1. Database (off-chain)
- FEReLNVud4utWZqu1TzmY7HgzB7v2rFoJ31AAdKgjxAV
- 2. Recomputed (your browser)
- computing…
- 3. On-chain (Solana memo)
- fetching…
Canonical bytes hashed (1581 chars)
{"actor":"judge","artifact_identity":"59b462c7c10fcb3db2d0b237cec383cb","band_override":null,"decided_at":"2026-10-27T19:16:58.483Z","decision":"review_revise","delist_requested":false,"disputed_pct":0.2222,"investigation_id":"0e544160-e680-4c40-8e05-75c44969fd10","judge_def_hash":"8800307026131ea9d5da939d32b9a1f1884b2b84a5de33c8e87931d36f38d0f8","new_score":26,"page_slug":"zano-zano","prev_score":28,"reason":"The core exploit narrative (Gateway Address registration, two minting events, 36.9M unauthorized ZANO, rollback via release 2.2.3.600) was confirmed by a Tier 1 source (claim_findings[2]). Two of nine claims could not be verified, the market price and cap figures (claim_findings[7]) and the CoinCodex transaction statistics (claim_findings[8]), which gives a 22% disputed rate and a minor-issues band. Two claims were only partly supported: MEXC's suspension was of deposits and withdrawals, not trading (claim_findings[5]), and the description of block 3,833,000 is internally inconsistent (claim_findings[3]). A high-priority gap also remains, because the claims-process status dates from early October and may be out of date. The one omission, the Freedom Dollar team absorbing losses, is minor, so no escalation was applied.","reviewer_def_hash":"bc11388ce4bc4deea1b064fea362663ae06e3f4f687f99604769044d6ffba770","score_delta":-2,"score_limit":{"applied":-2,"limited":true,"proposed":-10,"rule":"limited_no_second_opinion","second":null},"sequence_num":3,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}