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 · Zero Network (Zerion L2)
- Sequence
- #2
- Score
- 38 → 38 (0)
- Cluster
- mainnet-beta
- Slot
- 443517596
- Off-chain at
- 2026-08-25T22:28:43.127Z
- Anchored at
- —
- Block time
- —
Independent verification
- 1. Database (off-chain)
- DRCxzfjjiCeq1fs2KFhwLnkiXDdm1RhMufh3PmhjfYr
- 2. Recomputed (your browser)
- computing…
- 3. On-chain (Solana memo)
- fetching…
Canonical bytes hashed (1493 chars)
{"actor":"reviewer","decided_at":"2026-08-25T22:28:42.895Z","decision":"review","investigation_id":"4febd78d-1f92-43e6-84bc-943ea9e9a95e","new_score":38,"page_slug":"zero-network-zerion-l2","prev_score":38,"reason":"The page's central narrative -- Zero Network's launch, the December 2025 outage, the May 2026 shutdown announcement and July 31 deadline, the lack of a disclosed recovery mechanism, and the L2Beat Stage-0/centralization risk factors -- is well-supported by independently verifiable primary and secondary sources, including a direct match against Zerion's own X announcement and near-verbatim language from L2Beat's risk page. The main weaknesses are two overstated causal claims (that the December outage is 'widely cited' as a factor in the shutdown, and that it 'validated' the proposer-centralization risk 'in practice'), which are not supported by the reporting that actually explains the wind-down decision, plus one timeline claim from March 2024 that a contemporaneous source contradicts (Zerion had explicitly not committed to ZK Stack at that time). The page does not level unsupported accusations at Zerion as a company and generally distinguishes documented incidents from architectural risk common to most L2s, though it slightly overreaches in tying the specific outage to the specific proposer-whitelisting risk category.","score_delta":0,"sequence_num":2,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}