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 · Cozy V2
- Sequence
- #4
- Score
- 59 → 59 (0)
- Cluster
- mainnet-beta
- Slot
- 464276109
- Off-chain at
- 2026-11-01T23:25:20.025Z
- Anchored at
- 2026-11-01T23:25:46.000Z
- Block time
- 2026-11-01T23:25:46.000Z
Independent verification
- 1. Database (off-chain)
- 9yLQbjZgJFLDi4ZR1eHSwBNthrXSSizb67dLJbEHY73L
- 2. Recomputed (your browser)
- computing…
- 3. On-chain (Solana memo)
- fetching…
Canonical bytes hashed (1325 chars)
{"actor":"reviewer","artifact_identity":"cbe170a9efc188a989707ae1993e306e","blocked_count":1,"decided_at":"2026-11-01T23:25:19.961Z","decision":"review","disputed_pct":0.3333,"findings_hash":"E8kT7vbTMHGPpJHbL59utwvBqbX2jBfkgkv71hgKWAbg","investigation_id":"97186db0-8236-479e-9311-19e65b30abae","judge_def_hash":"8800307026131ea9d5da939d32b9a1f1884b2b84a5de33c8e87931d36f38d0f8","new_score":59,"omissions":{"material":2,"total":2},"page_content_hash":"8f258fdd273030f6b4cd77afb809bd37beb787d8fa9e5c6b03c2c20db249e26c","page_slug":"cozy-v2","prev_score":59,"reason":"The August 2025 exploit facts (date, amount, root cause, redemption details) and 2020 funding facts match readable sources. The Verichains post-mortem date in the timeline is wrong (published 2025-10-15, not 2025-08-30), and the Tornado Cash and bridging claim could not be confirmed from readable sources. The page omits a second exploit on 2026-09-07 (~$170K) and a subsequent TVL collapse, which makes its current-status picture misleading.","reviewer_def_hash":"bc11388ce4bc4deea1b064fea362663ae06e3f4f687f99604769044d6ffba770","score_delta":0,"scored_claims":6,"sequence_num":4,"subject_status":"exploited","subject_status_contradicts_page":true,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}