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 · BTC24H
- Sequence
- #3
- Score
- 26 → 26 (0)
- Cluster
- mainnet-beta
- Slot
- 462185065
- Off-chain at
- 2026-10-27T19:14:13.058Z
- Anchored at
- 2026-10-27T19:14:21.000Z
- Block time
- 2026-10-27T19:14:21.000Z
Independent verification
- 1. Database (off-chain)
- H1JcCSXPTRkVsWQ9u4vwokYC65hkTqSP7FZzTzeEZRBT
- 2. Recomputed (your browser)
- computing…
- 3. On-chain (Solana memo)
- fetching…
Canonical bytes hashed (1368 chars)
{"actor":"reviewer","artifact_identity":"c752ec75dbd4ec85a09e19594728f982","blocked_count":1,"decided_at":"2026-10-27T19:14:12.913Z","decision":"review","disputed_pct":0.3333,"findings_hash":"79uX4nsbhP8fQ3fbJDGBSNQHP92DYtFytrcNt7B3piej","investigation_id":"989aead3-c953-49ff-a28f-846df2c9bc83","judge_def_hash":"8800307026131ea9d5da939d32b9a1f1884b2b84a5de33c8e87931d36f38d0f8","new_score":26,"page_content_hash":"957f330f3cb3b25884b7b7db6d66a9368736369d40f70fa66a960ca7f0b3633e","page_slug":"btc24h","prev_score":26,"reason":"The core exploit claims (missing eligibility check, about $85,700 loss, tx hash) and the Scamadviser findings on bitcoin24h.net match the sources I fetched. Problems: the ZachXBT flag is asserted though the page admits it has no evidence; a paraphrase is put in quotation marks as a Quadriga quote; the Jan 27 Quadriga publication date and the exact Dec 16-17 dates are not backed by the case study. On-chain and market-data claims could not be read and are not scored. I found no information on the project's current status.","reviewer_def_hash":"bc11388ce4bc4deea1b064fea362663ae06e3f4f687f99604769044d6ffba770","score_delta":0,"scored_claims":6,"sequence_num":3,"subject_status":"unknown","subject_status_contradicts_page":false,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}