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 · Ronald Pope
- Sequence
- #4
- Score
- 26 → 26 (0)
- Cluster
- mainnet-beta
- Slot
- 462169996
- Off-chain at
- 2026-10-27T18:20:53.231Z
- Anchored at
- 2026-10-27T18:21:04.000Z
- Block time
- 2026-10-27T18:21:04.000Z
Independent verification
- 1. Database (off-chain)
- 9N4J9HTKB6zVtKEnS2HKzce5Lkg57Qj9J213g5hvEAWC
- 2. Recomputed (your browser)
- computing…
- 3. On-chain (Solana memo)
- fetching…
Canonical bytes hashed (1632 chars)
{"actor":"judge","artifact_identity":"29905856ca6210882edbfb037b556382","band_override":null,"blocked_count":3,"decided_at":"2026-10-27T18:20:52.975Z","decision":"review_revise","delist_requested":false,"disputed_pct":0.3636,"investigation_id":"bc5dbae5-c6f2-477c-8b9b-6d7a57ba0a5f","judge_def_hash":"8800307026131ea9d5da939d32b9a1f1884b2b84a5de33c8e87931d36f38d0f8","new_score":26,"page_slug":"ronald-pope","prev_score":26,"reason":"Of 14 claim findings, 3 were set aside as unscored because the source (BehindMLM) refused the reviewer. Of the remaining 11, 4 were disputed or unverifiable (about 36%), which falls in the significant-issues band. Three of those four (claim_findings[0-2]) are one error: the CFTC filing date is given as September 25, 2026, but the complaint is stamped September 24 and September 25 is the press release date. The fourth (claim_findings[12]) is an unverifiable negative claim about Pope's response. The core allegations (amounts, dates, roles, quotes) were confirmed against the complaint. Two claims were only partly supported (claim_findings[5], [9]), and the CFX Legacy and UK investigation claims remain unchecked because the source was blocked. The penalty is set at the mildest end of the band because the disputed items are a one-day date error repeated in three places, the omissions are minor, and the page is properly framed as allegations.","reviewer_def_hash":"bc11388ce4bc4deea1b064fea362663ae06e3f4f687f99604769044d6ffba770","score_delta":0,"scored_claims":11,"sequence_num":4,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}