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 · Zerion Wallet
- Sequence
- #5
- Score
- 65 → 65 (0)
- Cluster
- mainnet-beta
- Slot
- 457650850
- Off-chain at
- 2026-10-16T13:16:13.150Z
- Anchored at
- 2026-10-16T13:16:18.958Z
- Block time
- —
Independent verification
- 1. Database (off-chain)
- AXKx2nUh23te1cy2Jm2Eys2rNo8TRuPoHukRgwemJXQa
- 2. Recomputed (your browser)
- computing…
- 3. On-chain (Solana memo)
- fetching…
Canonical bytes hashed (1924 chars)
{"actor":"reviewer","artifact_identity":"2d34092c72fee4201a81efc13fdc771b","decided_at":"2026-10-16T13:16:12.971Z","decision":"review","disputed_pct":0.4286,"findings_hash":"53YehfXDwwNkcirsxDquqRwfD28fQX29mYWMKize8wtz","investigation_id":"e7b1c6d3-ee40-43d0-ac0d-f80fea6d7508","mode":"findings_only","new_score":65,"page_content_hash":"775adcbde1521349c9cb73e4c5fe34214c57d42a26af14ea4d25ee1b3951187c","page_slug":"zerion-wallet","prev_score":65,"reason":"The page's event-level reporting on Zerion's three security incidents (Feb 2021 Balancer-clone phishing, June 2023 Twitter compromise, April 2026 North Korean-attributed social engineering breach) and the ZERO Network shutdown is well sourced and matches primary materials and independent press coverage closely, including exact dollar figures from Zerion's own post-mortems. However, the page gets Zerion's founding year wrong (claims 2016; company materials and CB Insights point to 2019) in three places (summary, overview section, timeline), misstates the ZERO Network's actual mainnet launch month (claims December 2024; multiple outlets date it to November 12, 2024), and misnames the firms behind Zerion's security audits (claims Cube53/PeckShield/Trail of Bits; the cited zerion.io/security page actually lists Cure53/SlowMist/Zokyo/Secfault Security). The security section also overstates that no incident ever involved loss of user funds, glossing over the Feb 2021 incident's $30,000 user loss (later reimbursed). One Scam Sniffer attribution detail could not be verified because the sole cited source (an X/Twitter post) was paywalled, and the one accessible primary source for that incident names a different firm for a related claim. A cited Bitget Academy source is a dead link (404) in two places on the page.","score_delta":0,"sequence_num":5,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}