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 · The Conversion Pros Inc.
- Sequence
- #3
- Score
- 2 → 0 (-18)
- Cluster
- mainnet-beta
- Slot
- 462043296
- Off-chain at
- 2026-10-27T10:51:35.519Z
- Anchored at
- 2026-10-27T10:51:51.000Z
- Block time
- 2026-10-27T10:51:51.000Z
Independent verification
- 1. Database (off-chain)
- 8dgqtXmy3ea6G6WmXBzNaQ1ecaQdTi7Gb4icSHSkAf2W
- 2. Recomputed (your browser)
- computing…
- 3. On-chain (Solana memo)
- fetching…
Canonical bytes hashed (2061 chars)
{"actor":"judge","artifact_identity":"8725434b2566384485aad1cbbf59b49b","band_override":null,"blocked_count":2,"decided_at":"2026-10-27T10:51:35.130Z","decision":"review_revise","delist_requested":false,"disputed_pct":0.3333,"investigation_id":"d6c86c4f-dd82-4bbd-9256-1f72ecbc9d26","judge_def_hash":"8800307026131ea9d5da939d32b9a1f1884b2b84a5de33c8e87931d36f38d0f8","new_score":0,"page_slug":"the-conversion-pros-inc","prev_score":2,"reason":"Most core allegations match the CFTC complaint: court, defendants, scheme dates, $950M, 400,000 accounts and the quoted message. Two findings are disputed (claim_findings[0] and [1]): the filing date is September 24, 2026 per the docket, not September 25. Four more are unverifiable and rest on tier-3 sources or could not be found (pricing and commission, other Pope entities, the January 2020 message, and the 2015 domain registration). Separately, the $15.4M is attributed to Pope personally when the complaint says 'Pope and/or TCP' (claim_findings[8] and [9]), 'verified' losses overstates an allegation, and the December 2024 ASIC action concerned the successor CFX Legacy. The page also omits Pope's alleged role as an official promoter, which the reviewer rated material. Two further findings were blocked by a 403 and were left out of the percentage, so that is a coverage limit and not a defect of the page.","reviewer_def_hash":"bc11388ce4bc4deea1b064fea362663ae06e3f4f687f99604769044d6ffba770","score_delta":-18,"scored_claims":18,"sequence_num":3,"severity_override":{"applied":true,"band":"significant","from_band":"significant","reason":"claim_findings: 6 of 18 counted findings are disputed or unverifiable (about 33%), which is the significant band. omission_findings[1] is material (Pope's alleged role as an official Cash FX promoter, and TCP never being registered with the CFTC). It is not covered on the page, so the verdict is held at the significant band and not moved down to minor."},"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}