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_revise · Adam22 (Adam John Grandmaison) — $CUCK Meme Coin
- Sequence
- #3
- Score
- 12 → 0 (-13)
- Cluster
- mainnet-beta
- Slot
- 443510880
- Off-chain at
- 2026-08-25T03:13:58.266Z
- Anchored at
- —
- Block time
- —
Independent verification
- 1. Database (off-chain)
- 3oMDfejmQJueFjEsybz1v6Q8K6D83EbBibavTSMASCLe
- 2. Recomputed (your browser)
- computing…
- 3. On-chain (Solana memo)
- fetching…
Canonical bytes hashed (1522 chars)
{"actor":"judge","decided_at":"2026-08-25T03:13:57.990Z","decision":"review_revise","investigation_id":"49204961-1f88-4638-9aed-2adb69c8a49a","new_score":0,"page_slug":"adam22-adam-john-grandmaison-cuck-meme-coin","prev_score":12,"reason":"The reviewer confirmed 21 of 28 claims, including the core narrative that Adam22 was warned in advance, promoted $CUCK anyway, the token collapsed, and he later said he did not regret it (claim_findings[11], [13], [14]). Four claims were disputed: the same underlying figure — a '200% surge' to a '$1.5 million peak' market cap — appears three times on the page (claim_findings[2], [9], [22]) and conflicts with the page's own cited Bitget source ($5M peak/$90k trough) and Wikipedia ($4M peak/$100k trough); the qualitative surge-then-collapse pattern holds, but the specific numbers do not. Separately, the page inaccurately implies both Kim Kardashian and Floyd Mayweather faced SEC enforcement over EthereumMax, when only Kardashian was SEC-charged (claim_findings[18]) — a factual error about a named third party who is not the page's subject. Two high-priority coverage gaps reinforce the market-cap discrepancy as an unresolved reconciliation issue. Given a 17.9% disputed rate, no evidence of fabrication or misidentification, and moderate-high reviewer confidence (0.72), this warrants correction rather than removal or takedown.","score_delta":-13,"sequence_num":3,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}