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 · DuelBits
View on Solana ↗
Sequence
#5
Score
60 → 60 (0)
Cluster
mainnet-beta
Slot
457654375
Off-chain at
2026-10-16T13:28:39.948Z
Anchored at
2026-10-16T13:28:59.130Z
Block time
—

Independent verification

1. Database (off-chain)
2xXabKyLorHvhU87Ejaifi7o5Utc6qU3VBu4AkiBbvbP
2. Recomputed (your browser)
computing…
3. On-chain (Solana memo)
fetching…
Canonical bytes hashed (1729 chars)
{"actor":"reviewer","artifact_identity":"e59ae019c4b845da6a8055d13f071db7","decided_at":"2026-10-16T13:28:39.674Z","decision":"review","disputed_pct":0.1905,"findings_hash":"9sdyr69wMwaNvYYNHzYNucGEAR572qxULpFN3z87VQvg","investigation_id":"6eb30c9d-a37f-4690-ad1c-c7b0998cad2e","mode":"findings_only","new_score":60,"page_content_hash":"f4ae927d3592c22937f7d53cd6afcf56801684dfe711bfe3828b42e0941ec8cb","page_slug":"duelbits","prev_score":60,"reason":"The page's core narrative — the February 2024 $4.6M private-key compromise, the 2022 Twitch ban, and the late-2025 sponsorship news — is well sourced and mostly confirmed against independently fetched primary and secondary sources. Two defects stand out: the sentence (repeated in a section and a timeline entry) claiming DuelBits 'acknowledged the exploit and paused operations' after the Feb 2024 hack is contradicted by contemporary reporting, which says the company did not respond at the time; and the Curacao license number cited twice (GLH-OCCHKTW076092020) does not match the current official Curacao Gaming Control Board certificate (OGL/2024/1507/0838, effective Nov 2024), making it a stale/superseded figure. Several user-complaint figures in the 'User Complaints' section partially match AskGamblers listings but diverge on specifics (currency, ban details) or could not be located at all. The most serious gap is that the page omits a larger, more recent (September 2026) DuelBits hack and non-US regulatory actions (UK AML-related market exit, Swedish prohibition order), leaving the risk picture materially out of date.","score_delta":0,"sequence_num":5,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}