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 · Volo Vault
- Sequence
- #3
- Score
- 59 → 59 (0)
- Cluster
- mainnet-beta
- Slot
- 464345120
- Off-chain at
- 2026-11-02T03:31:44.855Z
- Anchored at
- 2026-11-02T03:32:08.000Z
- Block time
- 2026-11-02T03:32:08.000Z
Independent verification
- 1. Database (off-chain)
- HVhzZM8CTrCQXzya2XURYq15wGMKjo3AML8vbTJXP8q2
- 2. Recomputed (your browser)
- computing…
- 3. On-chain (Solana memo)
- fetching…
Canonical bytes hashed (1343 chars)
{"actor":"reviewer","artifact_identity":"cc435d7a1a11a5f982e891e828fde527","decided_at":"2026-11-02T03:31:44.807Z","decision":"review","disputed_pct":0.5,"findings_hash":"CJhNpg4YRoo26TPTbxSvvEEEGZXoXQBbEgVViuCfbNrg","investigation_id":"7b231e4d-87b8-4e9b-a6ab-480fa5c4a1dd","judge_def_hash":"8800307026131ea9d5da939d32b9a1f1884b2b84a5de33c8e87931d36f38d0f8","new_score":59,"omissions":{"material":1,"total":3},"page_content_hash":"a8ebb13b28f906b0e8ac156a03fb7eaa78d78d042cec0e430fdbe2410e88c36c","page_slug":"volo-vault","prev_score":59,"reason":"The core incident facts hold up against the sources I fetched: $3.5M lost across three vaults, a compromised admin key, the attacker address, the function name, the blocked 19.6 WBTC bridge and the roughly 90% recovery. The net loss figure of about $200K has been superseded by later reporting of about $60K. The ZachXBT claim was not found in the cited source, and the post-mortem and regulatory claims cannot be confirmed. The corporate-history, TVL and broader-context claims were not checked.","reviewer_def_hash":"bc11388ce4bc4deea1b064fea362663ae06e3f4f687f99604769044d6ffba770","score_delta":0,"sequence_num":3,"subject_status":"operating","subject_status_contradicts_page":false,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}