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 · Base Chain Vault Hack (October 2026)
- Sequence
- #3
- Score
- 5 → 0 (-8)
- Cluster
- mainnet-beta
- Slot
- 462055348
- Off-chain at
- 2026-10-27T11:34:13.292Z
- Anchored at
- 2026-10-27T11:34:37.000Z
- Block time
- 2026-10-27T11:34:37.000Z
Independent verification
- 1. Database (off-chain)
- 6NQDBpRk26tL83jXqjfNWsg9ZWg8csg5Ht1eHnaAQNTF
- 2. Recomputed (your browser)
- computing…
- 3. On-chain (Solana memo)
- fetching…
Canonical bytes hashed (2034 chars)
{"actor":"judge","artifact_identity":"72e31a586cadcdf9a1fc2d53eb8b3c62","band_override":null,"blocked_count":1,"decided_at":"2026-10-27T11:34:12.735Z","decision":"review_revise","delist_requested":false,"disputed_pct":0,"investigation_id":"bd7ff93e-3a99-43f0-86f2-f30168ec78d8","judge_def_hash":"8800307026131ea9d5da939d32b9a1f1884b2b84a5de33c8e87931d36f38d0f8","new_score":0,"page_slug":"base-chain-vault-hack-october-2026","prev_score":5,"reason":"Every checkable claim on the page held up: 0 of 10 counted claim findings were disputed or unverifiable (one finding, claim_findings[2], was excluded because the cited CryptoTimes source blocked the reviewer). The amount, addresses, Safe 3-of-7 setup and Blockaid timing match independent reporting. The verdict is revised rather than approved because the page leaves out that roughly $31.7M reportedly remains in the vault (omission_findings[0], material). Smaller issues are three month-only timeline dates (claim_findings[8-10]) and a causal explanation for the loss revision that the sources do not state (claim_findings[4]). The unverified items in claim_findings[2] (remove/re-add framing, 09:04 UTC borrow time, ECDSA statement) are a coverage limit and should be rechecked via the archive link.","reviewer_def_hash":"bc11388ce4bc4deea1b064fea362663ae06e3f4f687f99604769044d6ffba770","score_delta":-8,"scored_claims":10,"sequence_num":3,"severity_override":{"applied":true,"band":"minor","from_band":"approve","reason":"omission_findings[0] is rated material: several outlets report about $31.7M still sits in the unclaimed vault, and the page does not mention this ongoing exposure. The claim percentage alone (0%) would approve the page, so it is escalated one band to minor. A harsher band is not warranted because the page's claims themselves hold up and the omission does not contradict the page's 'unresolved' framing (subject_status.contradicts_page is false)."},"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}