Skip to main content
Sign in
← 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 · AudiA6 Crypto Laundering Network
View on Solana ↗
Sequence
#2
Score
0 → 0 (0)
Cluster
mainnet-beta
Slot
443561100
Off-chain at
2026-09-02T00:35:54.039Z
Anchored at
—
Block time
—

Independent verification

1. Database (off-chain)
4ywZXn9S2kr8e8HNhcqCYNJc71Essh7pS1jgwxHYRBVb
2. Recomputed (your browser)
computing…
3. On-chain (Solana memo)
fetching…
Canonical bytes hashed (1177 chars)
{"actor":"reviewer","artifact_identity":"6b60992870eb4d3c372460e6243a671b","decided_at":"2026-09-02T00:35:53.960Z","decision":"review","disputed_pct":0,"investigation_id":"255371db-55cc-4c52-9538-13b49927f4ef","new_score":0,"page_slug":"audia6-crypto-laundering-network","prev_score":0,"reason":"The page's claims are extensively and consistently corroborated across primary (DOJ, Secret Service, Europol, TRM Labs, Chainalysis) and secondary (The Hacker News, Help Net Security, Cryptopolitan, Protos) sources, with dollar figures, dates, names, and seizure statistics matching to a high degree of precision. Two claims were marked partially_supported due to minor internal inconsistency in the LastPass/Wasabi Wallet tracing date and intermediary naming, not because the underlying figures were wrong. No disputed, unverifiable, or link-rot findings were identified, though direct government-domain fetches were blocked by 403 responses and had to be corroborated via search-engine snippets and independent secondary sources instead.","score_delta":0,"sequence_num":2,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}