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
- 40 → 40 (0)
- Cluster
- mainnet-beta
- Slot
- 425418092
- Off-chain at
- 2026-06-09T22:26:37.934Z
- Anchored at
- —
- Block time
- —
Independent verification
- 1. Database (off-chain)
- Gs9QtYnh5Z6MFNAiQqwnm3k3fr1FmTmm4ECaQ6LM9HPV
- 2. Recomputed (your browser)
- computing…
- 3. On-chain (Solana memo)
- fetching…
Canonical bytes hashed (1075 chars)
{"actor":"reviewer","decided_at":"2026-06-09T22:26:37.749Z","decision":"review","investigation_id":"0ab4a937-de5a-4e31-b57a-29b1ee03248a","new_score":40,"page_slug":"bc1qtkv6qcgq3qhqcdsk88wey50je0wk07s6erjrr9","prev_score":40,"reason":"The majority of on-chain claims are accurate and directly verifiable against the Blockstream API. Two material errors were identified: the fan-out transaction upstream of this address had 41 output addresses (not 20), and the Risk Indicators section states '85 BTC' where the correct value is 0.851 BTC — a 100x overstatement of the transaction scale. These errors likely share a common root cause: vout index 20 being misread as '20 outputs', and 85,104,474 satoshis being misread as 85 BTC. The larger output percentage (claimed 93.9%) is also slightly imprecise. None of the core address-level facts (balance, tx count, inbound/outbound amounts, fees, block heights, timestamps) contain errors.","score_delta":0,"sequence_num":2,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}