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 · XT Exchange
- Sequence
- #3
- Score
- 22 → 7 (-15)
- Cluster
- mainnet-beta
- Slot
- 462186576
- Off-chain at
- 2026-10-27T19:19:35.362Z
- Anchored at
- 2026-10-27T19:19:43.000Z
- Block time
- 2026-10-27T19:19:43.000Z
Independent verification
- 1. Database (off-chain)
- A5KQzkEw1S35rzGmzkitU3C6QTKrtpXpbbHx2QDVyhoJ
- 2. Recomputed (your browser)
- computing…
- 3. On-chain (Solana memo)
- fetching…
Canonical bytes hashed (1521 chars)
{"actor":"judge","artifact_identity":"db3950763ca4d80913902e4dc6ba305a","band_override":null,"blocked_count":1,"decided_at":"2026-10-27T19:19:35.047Z","decision":"review_revise","delist_requested":false,"disputed_pct":0.375,"investigation_id":"1e2ac659-6a87-484f-acda-a0f0d7c781fa","judge_def_hash":"8800307026131ea9d5da939d32b9a1f1884b2b84a5de33c8e87931d36f38d0f8","new_score":7,"page_slug":"xt-exchange","prev_score":22,"reason":"Of 9 claims checked, none were disputed, but 3 of the 8 counted claims (37.5%, excluding one Trustpilot claim the source blocked) could not be verified: the 12-hour withdrawal halt (claim_findings[2]), the Seychelles FSA notice date (claim_findings[6]) and the ZachXBT section (claim_findings[8]), which cites only generic channel and profile URLs. The core allegations were confirmed by primary or reputable sources: the $1.7M hack (claim_findings[0]) and the FCA, VARA and Thai SEC actions (claim_findings[3], [4], [5]). Because the confirmed core and the reviewer's moderate confidence point to a mild penalty, the delta sits at the lighter end of the band. The page also states the hack cause as fact when Halborn says 'most likely' (claim_findings[1]), and describes the Thai block as having happened when sources say it was scheduled.","reviewer_def_hash":"bc11388ce4bc4deea1b064fea362663ae06e3f4f687f99604769044d6ffba770","score_delta":-15,"scored_claims":8,"sequence_num":3,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}