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 · Cryptomus / Xeltox Enterprises Ltd.
- Sequence
- #5
- Score
- 0 → 0 (0)
- Cluster
- mainnet-beta
- Slot
- 462759675
- Off-chain at
- 2026-10-29T05:16:28.830Z
- Anchored at
- 2026-10-29T05:16:31.000Z
- Block time
- 2026-10-29T05:16:31.000Z
Independent verification
- 1. Database (off-chain)
- Fb5UvaG4ZSdgDTMQtW25nk2Cubeoia5v3DCMagbgRoYK
- 2. Recomputed (your browser)
- computing…
- 3. On-chain (Solana memo)
- fetching…
Canonical bytes hashed (2498 chars)
{"actor":"reviewer","artifact_identity":"6226b7330893a10a35b9e59639bbc897","decided_at":"2026-10-29T05:16:28.699Z","decision":"review","disputed_pct":0.2308,"findings_hash":"4XHXkB5Ec5KbHUUxzgqTurCgrqwR6QcynsxvEWyEah8q","investigation_id":"07e63eaa-1d75-45b0-8fef-47a315a054fd","mode":"findings_only","new_score":0,"omissions":{"material":1,"total":2},"page_content_hash":"304e1ba7ec9530ace2213ac7fe2bfa374fe6d64790019e09681be118eb7dc4cf","page_slug":"cryptomus-xeltox-enterprises-ltd","prev_score":0,"reason":"The large majority of this page's factual claims are well supported by the cited primary and secondary sources: the FINTRAC penalty amount, dates, violation counts, the BCSC temporary order, the Federal Court appeal details, and the TRM Labs findings on Iran-linked transactions and the Heleket successor-platform theory all check out against the sources cited. Two defects stand out: (1) the page states the previous FINTRAC penalty record (KuCoin/Peken Global) was set 'in September 2024,' when FINTRAC's own release shows it was imposed in July 2025 and announced in September 2025 — a one-year factual error; and (2) the page claims Heleket launched 'the same month' as, or 'shortly after,' Cryptomus's KYC rollout, when the cited TRM Labs article itself places Heleket's launch in January 2025 and the KYC rollout in February 2025 — a month apart, with Heleket preceding KYC rather than following it, which actually inverts the page's implied causal sequence. A few granular details (Berdieva's city of Bukhara, Berdiev's residence in Tashkent, a specific '56 exchanges' Russian-bank cash-out figure, a specific January 16 date for Heleket's first Garantex funding, and a precise count of MSBs at the Olympic Village address) could not be verified in the cited sources or elsewhere and may be unsupported additions. Most significantly, the page omits the UK's October 8, 2026 sanctions designation of Xeltox/Cryptomus/Heleket/Certa Payments Ltd., which post-dates the page's sources but represents the single largest escalation in the entity's regulatory history since the FINTRAC penalty, and its absence is a critical omission for any reader assessing the entity's current standing.","reviewer_def_hash":"bc11388ce4bc4deea1b064fea362663ae06e3f4f687f99604769044d6ffba770","score_delta":0,"sequence_num":5,"subject_status":"sanctioned","subject_status_contradicts_page":true,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}