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 · Zcash
- Sequence
- #2
- Score
- 62 → 62 (0)
- Cluster
- mainnet-beta
- Slot
- 425191265
- Off-chain at
- 2026-06-08T21:22:33.031Z
- Anchored at
- —
- Block time
- —
Independent verification
- 1. Database (off-chain)
- 5mW6L465yx6weVKZigiouWihdqPrxcpVTEXfZNEKfDUL
- 2. Recomputed (your browser)
- computing…
- 3. On-chain (Solana memo)
- fetching…
Canonical bytes hashed (1196 chars)
{"actor":"reviewer","decided_at":"2026-06-08T21:22:32.971Z","decision":"review","investigation_id":"c74f94ee-608e-40f1-ba08-8dde9224dc41","new_score":62,"page_slug":"zcash","prev_score":62,"reason":"The Zcash investigation page is well-sourced and factually accurate on the large majority of claims, with key historical events (counterfeiting vulnerability, SEC investigation, ECC governance crisis, ViaBTC 51% incident, ZIP 1014 mechanics) confirmed by cited sources. The six partially-supported findings are minor characterization issues rather than material errors. The most significant gap is a complete absence of the May 2026 Orchard soundness vulnerability and the NU6.2 emergency hard fork, which directly contradicts the page's claim that Halo 2 eliminated this class of counterfeiting risk and represents a major recent development with a 30%+ price impact. Cited source URLs generally loaded and supported their claims; the Blockworks and The Block URLs returned 403 errors but their content was independently verifiable through other sources.","score_delta":0,"sequence_num":2,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}