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 · Bonk
- Sequence
- #2
- Score
- 45 → 45 (0)
- Cluster
- mainnet-beta
- Slot
- 443525322
- Off-chain at
- 2026-08-27T10:40:23.214Z
- Anchored at
- —
- Block time
- —
Independent verification
- 1. Database (off-chain)
- 8THonU5VunnW5Yp4AAw9pZqWyxvE3LhHRZKUEcprF6JG
- 2. Recomputed (your browser)
- computing…
- 3. On-chain (Solana memo)
- fetching…
Canonical bytes hashed (1046 chars)
{"actor":"reviewer","decided_at":"2026-08-27T10:40:22.787Z","decision":"review","investigation_id":"2a48b3c5-5a6f-4913-a093-0800cc23a7e9","new_score":45,"page_slug":"bonk","prev_score":45,"reason":"The page's historical claims about Bonk's December 2022 launch, airdrop mechanics, first-week price surge, and January 2023 team-token burn are well-supported by independent contemporaneous reporting. However, the page is thin relative to how heavily covered this token is: it omits a ~$20M BonkDAO governance-attack treasury drain and subsequent Upbit delisting (contradicting its own 'no protocol-level exploits recorded' claim), presents an already-resolved 1-trillion-token burn conditional as still pending, and describes the Safety Shot treasury position without noting the company's subsequent rebrand and expanded holdings. No tokenomics table, current market data, or on-chain analysis is present.","score_delta":0,"sequence_num":2,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}