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 · BTC24H
- Sequence
- #4
- Score
- 26 → 26 (0)
- Cluster
- mainnet-beta
- Slot
- 462185070
- Off-chain at
- 2026-10-27T19:14:13.230Z
- Anchored at
- 2026-10-27T19:14:22.000Z
- Block time
- 2026-10-27T19:14:22.000Z
Independent verification
- 1. Database (off-chain)
- DjextTcsgpryQKmoVoazcs2PfyziKZbKDySMbJ3bTLkW
- 2. Recomputed (your browser)
- computing…
- 3. On-chain (Solana memo)
- fetching…
Canonical bytes hashed (1459 chars)
{"actor":"judge","artifact_identity":"c752ec75dbd4ec85a09e19594728f982","band_override":null,"blocked_count":1,"decided_at":"2026-10-27T19:14:12.913Z","decision":"review_revise","delist_requested":false,"disputed_pct":0.3333,"investigation_id":"989aead3-c953-49ff-a28f-846df2c9bc83","judge_def_hash":"8800307026131ea9d5da939d32b9a1f1884b2b84a5de33c8e87931d36f38d0f8","new_score":26,"page_slug":"btc24h","prev_score":26,"reason":"Of 7 claims checked, 1 could not be assessed because the source blocked the reviewer and was left out, leaving 6. Two of those 6 (33%) could not be verified: the ZachXBT flag (claim_findings[5]), which the page asserts while admitting it found no supporting post, and the 2025-01-27 Quadriga publication date (claim_findings[1]). The core exploit claims (missing eligibility check, about $85,700 loss) and the Scamadviser findings were confirmed, and a quotation attributed to Quadriga is actually a paraphrase (claim_findings[4]). The penalty sits at the low end of the band because reviewer confidence is moderate-to-low (0.5) and the page's central allegations hold up. On-chain and market-data claims could not be read, which is a coverage limit rather than a defect of the page.","reviewer_def_hash":"bc11388ce4bc4deea1b064fea362663ae06e3f4f687f99604769044d6ffba770","score_delta":0,"scored_claims":6,"sequence_num":4,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}