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 · AudiA6
- Sequence
- #7
- Score
- 0 → 0 (-5)
- Cluster
- mainnet-beta
- Slot
- 462058264
- Off-chain at
- 2026-10-27T11:44:23.166Z
- Anchored at
- 2026-10-27T11:44:58.000Z
- Block time
- 2026-10-27T11:44:58.000Z
Independent verification
- 1. Database (off-chain)
- 5j4qsF9KooLJYrQTfe8i2WNFDpFoPkDijvS6wawnn1uw
- 2. Recomputed (your browser)
- computing…
- 3. On-chain (Solana memo)
- fetching…
Canonical bytes hashed (1557 chars)
{"actor":"judge","artifact_identity":"d4a61d60aa2f7b3220e62a90cd6e53af","band_override":null,"blocked_count":1,"decided_at":"2026-10-27T11:44:22.443Z","decision":"review_revise","delist_requested":false,"disputed_pct":0.2,"investigation_id":"ea89f009-d5f5-4c59-9b8e-d7cd672c067a","judge_def_hash":"8800307026131ea9d5da939d32b9a1f1884b2b84a5de33c8e87931d36f38d0f8","new_score":0,"page_slug":"audia6","prev_score":0,"reason":"The core allegations on this page (10,333 BTC / about $389 million, the two named defendants, EDPA charges, arrests in Batumi, seizure figures, extradition status) were confirmed against the DOJ release and BleepingComputer (claim_findings[0-2]). One of five scored findings, the 2021-11 timeline entry on the Intel 471 / BleepingComputer cryptomixer article, could not be checked because the reviewer did not fetch the article (claim_findings[4]), which puts the unverified share at 20%. The fake-Ledger section is otherwise supported by CoinDesk, but the app name 'Leva Heal' does not appear in that source (claim_findings[3]). The TRM Labs ransomware figures were not scored because the source blocked the reviewer (claim_findings[5]). The unverified items are peripheral and no omissions or status contradictions were found, so the penalty is kept at the low end of the minor band.","reviewer_def_hash":"bc11388ce4bc4deea1b064fea362663ae06e3f4f687f99604769044d6ffba770","score_delta":-5,"scored_claims":5,"sequence_num":7,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}