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 · Benjamin Paul Wiener
- Sequence
- #3
- Score
- 4 → 0 (-5)
- Cluster
- mainnet-beta
- Slot
- 461838410
- Off-chain at
- 2026-10-26T22:45:28.725Z
- Anchored at
- 2026-10-26T22:45:51.000Z
- Block time
- 2026-10-26T22:45:51.000Z
Independent verification
- 1. Database (off-chain)
- 4jWfNQUkwoH8TXANUvf9QPtQo6RfdTNTTbTZJ7koAxXu
- 2. Recomputed (your browser)
- computing…
- 3. On-chain (Solana memo)
- fetching…
Canonical bytes hashed (2556 chars)
{"actor":"judge","artifact_identity":"2496ce6a971d2d8d4c3881d28d4ad673","band_override":{"actual_delta":-5,"actual_verdict":"review_revise","disputed_pct":0,"expected_delta_range":[0,0],"expected_verdict":"review_approve","rationale":"The page's factual claims held up: of 10 countable claim findings (one blocked-source finding excluded), none were disputed or unverifiable, so disputed_pct is 0%. Core allegations (29 counts, plea date, judge, penalties, entities, the August 15, 2025 receiver order) match the IRS-CI release, Leagle order and news coverage (claim_findings[0], [1], [8]). The verdict moves to a minor revision only because of the high-priority coverage gap on criminal docket status: the reported September 15, 2026 trial date has passed with no outcome found, and the page still presents it as upcoming. The age of 43 (claim_findings[3]) and the $25.1M figure (claim_findings[6]) were only partly supported, though the page already hedges the latter. One Dakota Scout item could not be read because the source was blocked, which is a coverage limit and not a defect of the page."},"blocked_count":1,"decided_at":"2026-10-26T22:45:28.377Z","decision":"review_revise","delist_requested":false,"disputed_pct":0,"investigation_id":"96a72320-d999-48ba-9830-5555d5ecabd6","judge_def_hash":"8800307026131ea9d5da939d32b9a1f1884b2b84a5de33c8e87931d36f38d0f8","new_score":0,"page_slug":"benjamin-paul-wiener","prev_score":4,"reason":"The page's factual claims held up: of 10 countable claim findings (one blocked-source finding excluded), none were disputed or unverifiable, so disputed_pct is 0%. Core allegations (29 counts, plea date, judge, penalties, entities, the August 15, 2025 receiver order) match the IRS-CI release, Leagle order and news coverage (claim_findings[0], [1], [8]). The verdict moves to a minor revision only because of the high-priority coverage gap on criminal docket status: the reported September 15, 2026 trial date has passed with no outcome found, and the page still presents it as upcoming. The age of 43 (claim_findings[3]) and the $25.1M figure (claim_findings[6]) were only partly supported, though the page already hedges the latter. One Dakota Scout item could not be read because the source was blocked, which is a coverage limit and not a defect of the page.","reviewer_def_hash":"bc11388ce4bc4deea1b064fea362663ae06e3f4f687f99604769044d6ffba770","score_delta":-5,"scored_claims":11,"sequence_num":3,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}