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_approve · Wrapped BTC (Portal)
- Sequence
- #4
- Score
- 71 → 71 (0)
- Cluster
- mainnet-beta
- Slot
- 462057182
- Off-chain at
- 2026-10-27T11:41:01.934Z
- Anchored at
- 2026-10-27T11:41:08.000Z
- Block time
- 2026-10-27T11:41:08.000Z
Independent verification
- 1. Database (off-chain)
- AdKgcWp2okHc5zGGVXTfq9FyYr5vbqhDh7JgvWWZw5pU
- 2. Recomputed (your browser)
- computing…
- 3. On-chain (Solana memo)
- fetching…
Canonical bytes hashed (1534 chars)
{"actor":"judge","artifact_identity":"d88f1259a7f65a3eda6071b87ab688d9","band_override":null,"blocked_count":1,"decided_at":"2026-10-27T11:41:01.335Z","decision":"review_approve","delist_requested":false,"disputed_pct":0,"investigation_id":"2a9c4df5-b7a0-4f63-98e9-7a13adc1e4d2","judge_def_hash":"8800307026131ea9d5da939d32b9a1f1884b2b84a5de33c8e87931d36f38d0f8","new_score":71,"page_slug":"wrapped-btc-portal","prev_score":71,"reason":"Of 7 claim findings, 1 (claim_findings[3], the Oasis/High Court claim) was unverifiable only because Blockworks returned HTTP 403, so it is excluded from the count and noted as a coverage limit rather than a defect. Of the remaining 6, none were disputed or unverifiable (0%), and four were confirmed against sources, including the Wormhole official notice (Tier 1) and the 2022 hack figures (Tier 2). claim_findings[2] (Jump Crypto replenishment) and claim_findings[6] (market cap about $195M versus a stated $200-$400M range, holder count not reproduced) were only partially supported and concern secondary details. The review found no shutdown, exploit of the token, or material omission. The high-priority gap on supply versus locked collateral is a suggestion for expansion, not a flaw in what the page states, so it does not change the verdict.","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}