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
- Sequence
- #2
- Score
- 0 → 0 (0)
- Cluster
- mainnet-beta
- Slot
- 443521915
- Off-chain at
- 2026-08-26T19:11:16.252Z
- Anchored at
- —
- Block time
- —
Independent verification
- 1. Database (off-chain)
- DDHgYxUdha8mxJYiTzNKmKVw5BRmBU7HNqkMGjqz58pb
- 2. Recomputed (your browser)
- computing…
- 3. On-chain (Solana memo)
- fetching…
Canonical bytes hashed (1372 chars)
{"actor":"reviewer","decided_at":"2026-08-26T19:11:15.940Z","decision":"review","investigation_id":"cc3a88d5-1ffa-41bd-b385-ee5e1f6acec5","new_score":0,"page_slug":"ofac-isis-k-134-address-sdn-batch-july-2026","prev_score":0,"reason":"The page's core, slug-defining figures (134 addresses = 131 TRON + 3 Monero, ~$2M moved) are corroborated across many independent outlets and are consistent with OFAC's own July 1, 2026 recent-action notice, though the page never cites OFAC's primary list update directly for the count. The June 22, 2026 facilitator action is accurately reconciled against Treasury's own press release, including correctly distinguishing newly-designated individuals from a previously-sanctioned one -- avoiding the entity/authority-bundling errors flagged elsewhere in this run. However, several specific dates in the timeline are wrong or unsupported by their own cited sources (Ali Shafiu's designation date, the Istanbul financier's arrest date, Ozgur Altun's capture date, and the 2022 on-chain-fundraising start date), and the crypto-specific characterization of Ozgur Altun and his wife Ayse Altun traces to a single source (TRM Labs) uncorroborated by dedicated journalistic profiles of the same arrest.","score_delta":0,"sequence_num":2,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}