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_revise · Cozy V2
- Sequence
- #5
- Score
- 59 → 59 (0)
- Cluster
- mainnet-beta
- Slot
- 464276114
- Off-chain at
- 2026-11-01T23:25:20.188Z
- Anchored at
- 2026-11-01T23:25:47.000Z
- Block time
- 2026-11-01T23:25:47.000Z
Independent verification
- 1. Database (off-chain)
- Ac86iCYbtonVcbQWbq5VjhY6tPNkp7edaV2HiMLttZjH
- 2. Recomputed (your browser)
- computing…
- 3. On-chain (Solana memo)
- fetching…
Canonical bytes hashed (1916 chars)
{"actor":"judge","artifact_identity":"cbe170a9efc188a989707ae1993e306e","band_override":null,"blocked_count":1,"decided_at":"2026-11-01T23:25:19.961Z","decision":"review_revise","delist_requested":false,"disputed_pct":0.3333,"investigation_id":"97186db0-8236-479e-9311-19e65b30abae","judge_def_hash":"8800307026131ea9d5da939d32b9a1f1884b2b84a5de33c8e87931d36f38d0f8","new_score":59,"page_slug":"cozy-v2","prev_score":59,"reason":"Of the seven claim findings, one was blocked at the source and is left out of the count. Two of the remaining six are not supported: claim_findings[0] shows the Verichains post-mortem was published on 2025-10-15, not 2025-08-30, and claim_findings[4] (Seattle incorporation) was not found in the cited source. That gives a 33% disputed rate. The core August 2025 exploit facts (date, amount, root cause) are confirmed (claim_findings[2]). However, the page does not mention a second exploit on 2026-09-07 (about $170,000) or the later collapse in total value locked, so its current-status picture is misleading. Reviewer confidence is moderate (0.6), and the Tornado Cash laundering claim could not be checked because its source was blocked, so the penalty stays in the middle of the band and the page is not denied.","reviewer_def_hash":"bc11388ce4bc4deea1b064fea362663ae06e3f4f687f99604769044d6ffba770","score_delta":0,"scored_claims":6,"sequence_num":5,"severity_override":{"applied":true,"band":"significant","from_band":"significant","reason":"The review reports a critical omission (a second exploit on 2026-09-07, about $170,000) and a material omission (TVL collapse to about $5k), and subject_status.contradicts_page is true. The percentage band is already significant (2 of 6 scoped findings, 33%), so the omission confirms that band and rules out a lenient reading."},"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}