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
review · KAITO
- Sequence
- #2
- Score
- 42 → 42 (0)
- Cluster
- mainnet-beta
- Slot
- 443525896
- Off-chain at
- 2026-08-27T12:05:42.206Z
- Anchored at
- —
- Block time
- —
Independent verification
- 1. Database (off-chain)
- 28Fo4iH6RnZRVdy97jt113FbH4HJ3r8iGjjKR6TimuuS
- 2. Recomputed (your browser)
- computing…
- 3. On-chain (Solana memo)
- fetching…
Canonical bytes hashed (1012 chars)
{"actor":"reviewer","decided_at":"2026-08-27T12:05:42.043Z","decision":"review","investigation_id":"44a5d100-c0ea-4ae1-8203-a34a434b2e24","new_score":42,"page_slug":"kaito","prev_score":42,"reason":"The page's per-section source lists are populated and largely check out against independent reporting, but the page-level `sources_used` array is empty and the summary is entirely uncited, meaning 'confirmed' here reflects independent verification rather than the page's own citation trail. Three findings are disputed: an internally inconsistent FDV figure (page's own $2.88 ATH times 1B supply implies ~$2.88B FDV, not the stated 'near $2 billion'), an ATH date placed on the wrong day (Feb 20 vs. the actual Feb 27, 2025), and a ZachXBT bounty date off by roughly 11 months (stated Jan 2025, actually Dec 2025). One citation (the official Kaito airdrop terms) is dead.","score_delta":0,"sequence_num":2,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}