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 · ZRX (0x Protocol)
- Sequence
- #2
- Score
- 62 → 62 (0)
- Cluster
- mainnet-beta
- Slot
- 443520832
- Off-chain at
- 2026-08-26T11:58:05.647Z
- Anchored at
- —
- Block time
- —
Independent verification
- 1. Database (off-chain)
- 8Z5EJzGTehHnAR8krVamBRirXriKSX5GvDNci6ptTz18
- 2. Recomputed (your browser)
- computing…
- 3. On-chain (Solana memo)
- fetching…
Canonical bytes hashed (1277 chars)
{"actor":"reviewer","decided_at":"2026-08-26T11:58:05.416Z","decision":"review","investigation_id":"69488b83-ebdf-40f0-8308-e1d2007a0d7b","new_score":62,"page_slug":"zrx-0x-protocol","prev_score":62,"reason":"The page's core historical narrative — the 2017 ICO and tokenomics, the 2019 v2.0 exchange vulnerability and its responsible-disclosure/remediation framing, and the September 2023 CFTC settlement — is accurately and thoroughly supported by primary and reputable secondary sources. However, three specific claims are directly contradicted by evidence: the 0x v4 governance vote is dated two years too late (January 2023 vs. the actual January 2021), the SwapNet post-incident analysis is attributed to the wrong security firm (Verichains vs. the cited source's actual CertiK/PeckShield attribution), and the description of ZRX's market-cap rank as 'well outside the top 200' is contradicted by current data placing it just inside the top 200. The Token Utility section also presents ZRX governance and staking as live functions without disclosing their 2024-2026 dormancy. No accepted community submissions exist for this page.","score_delta":0,"sequence_num":2,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}