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.
- Sequence
- #2
- Score
- 8 → 8 (0)
- Cluster
- mainnet-beta
- Slot
- 443515388
- Off-chain at
- 2026-08-25T17:04:43.782Z
- Anchored at
- —
- Block time
- —
Independent verification
- 1. Database (off-chain)
- 5mnRa8brcETR6p4q3SUVnHraVEiBh3z92fPdNLVJ7HHT
- 2. Recomputed (your browser)
- computing…
- 3. On-chain (Solana memo)
- fetching…
Canonical bytes hashed (1162 chars)
{"actor":"reviewer","decided_at":"2026-08-25T17:04:43.636Z","decision":"review","investigation_id":"93c361f5-3120-4191-bbf7-1dd0d214cf18","new_score":8,"page_slug":"mica-non-compliant-exchange-risk-cluster-post-july-1-2026","prev_score":8,"reason":"The large majority of the page's factual claims about the MiCA deadline, register counts, and individual exchange timelines were independently confirmed against ESMA, national-regulator, and reputable press sources. However, the review found four disputed claims of note: an overstated Article 111 penalty figure (EUR 15M/12.5% vs. the actual EUR 5M/5% for unauthorised CASP operation), a false claim that Binance France received AMF authorisation when it is only pending, an inverted claim about MiCA mandating an 'investor compensation guarantee' for crypto-assets when MiCA explicitly excludes them from such schemes, and most seriously, KuCoin's placement in the 'non-compliant operators' cluster despite holding an active MiCA CASP authorisation since November 2025.","score_delta":0,"sequence_num":2,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}