Skip to main content
AVOID.NET
← avoid.net

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

  1. 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.
  2. 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.
  3. 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 · Kalshi
View on Solana ↗
Sequence
#4
Score
58 → 58 (0)
Cluster
mainnet-beta
Slot
462178764
Off-chain at
2026-10-27T18:51:40.367Z
Anchored at
2026-10-27T18:52:02.000Z
Block time
2026-10-27T18:52:02.000Z

Independent verification

1. Database (off-chain)
CXF79GR62vsEVCXCyAhdMSpD1bmfH8WRDjuZ1jstua1L
2. Recomputed (your browser)
computing…
3. On-chain (Solana memo)
fetching…
Canonical bytes hashed (2066 chars)
{"actor":"judge","artifact_identity":"33400a8e9998c09dd62c0f6f52b64774","band_override":null,"blocked_count":2,"decided_at":"2026-10-27T18:51:40.026Z","decision":"review_revise","delist_requested":false,"disputed_pct":0.2857,"investigation_id":"33d825d8-bc21-4e3d-b9a7-2fbecaccebc9","judge_def_hash":"8800307026131ea9d5da939d32b9a1f1884b2b84a5de33c8e87931d36f38d0f8","new_score":58,"page_slug":"kalshi","prev_score":58,"reason":"The page's core account of the New York suit, the Santos settlement and the state actions checked out, but the Series E funding round is dated March 2026 in both the prose and the timeline when it was announced in December 2025 (claim_findings[0], [1]). The Missouri enforcement status is out of date because the deadline has passed (claim_findings[2]). The page also omits the August 2026 Ninth Circuit ruling against Kalshi, a material omission on the central preemption question, and the summary implies the Army soldier case involved Kalshi when the body says the trades were on Polymarket (claim_findings[3]). Because the reviewer's confidence was moderate and several claims were not fully fetched, the penalty is set at the low end of the significant band.","reviewer_def_hash":"bc11388ce4bc4deea1b064fea362663ae06e3f4f687f99604769044d6ffba770","score_delta":0,"scored_claims":7,"sequence_num":4,"severity_override":{"applied":true,"band":"significant","from_band":"minor","reason":"claim_findings[0] and [1] are disputed (about 29% of the 7 scored findings, the minor band; 2 further findings were blocked and excluded). The review also reports a material omission, the unanimous Ninth Circuit ruling against Kalshi on 2026-08-28, which the page does not cover while presenting the Connecticut loss as the only appellate setback. A high-priority coverage gap on appellate rulings and a stale Missouri status (claim_findings[2]) add to this. The percentage alone understates the problem, so the significant band applies."},"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}