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.

Sequence
#4
Score
0 → 0 (0)
Cluster
mainnet-beta
Slot
457712410
Off-chain at
2026-10-16T16:57:47.926Z
Anchored at
2026-10-16T16:58:12.649Z
Block time
—

Independent verification

1. Database (off-chain)
CgPKm9fUxN8gqTqevV5ngtPbWZeEoLK5zydH9jN15sTx
2. Recomputed (your browser)
computing…
3. On-chain (Solana memo)
fetching…
Canonical bytes hashed (2111 chars)
{"actor":"reviewer","artifact_identity":"4b95b922e8cbbcd9e159fad6255b61a2","decided_at":"2026-10-16T16:57:47.734Z","decision":"review","disputed_pct":0.125,"findings_hash":"AbipJsUQXwqkhu1LNNtPwtiWVdknwZQxp7KqYtcfLjuq","investigation_id":"07e63eaa-1d75-45b0-8fef-47a315a054fd","mode":"findings_only","new_score":0,"page_content_hash":"304e1ba7ec9530ace2213ac7fe2bfa374fe6d64790019e09681be118eb7dc4cf","page_slug":"cryptomus-xeltox-enterprises-ltd","prev_score":0,"reason":"The page's core claims — the record C$176.96 million FINTRAC penalty, its violation categories and counts, the Iran sanctions findings, the BCSC temporary order, the Federal Court appeal and corporate-separation defense, and TRM Labs' Cryptomus-Heleket linkage analysis — are all well-supported by the cited regulatory releases and reputable reporting (FINTRAC, BCSC, CBC, Globe and Mail, Krebs on Security, The Tyee, TRM Labs). Two identifiable errors were found: the prior FINTRAC record penalty against Peken Global/KuCoin is misdated to 'September 2024' when it was announced in September 2025, and the page twice gets the Cryptomus-Heleket sequencing backwards, implying Heleket launched after Cryptomus's KYC rollout when TRM's own reporting (and the page's own timeline) places Heleket's January 2025 launch a month before the February 2025 KYC implementation. One claim (the 56-exchange cash-out figure) is factually accurate but misattributed to TRM Labs rather than to Krebs on Security's reporting on researcher Richard Sanders. Minor unverifiable details remain around the exact legal name and hometown of Xeltox's director and the city attributed to Cryptomus's founder, both sourced to secondary reporting that stops short of the specificity on the page. The most significant gap is currency: the page's timeline ends in May 2026 and omits the UK's October 8, 2026 sanctions designation of Xeltox/Cryptomus/Heleket as a single entity, which is directly on-topic and highly material.","score_delta":0,"sequence_num":4,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}