Skip to main content
AVOID.NET
← avoid.net

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

  1. 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.
  2. 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.
  3. 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
View on Solana ↗
Sequence
#5
Score
69 → 69 (0)
Cluster
mainnet-beta
Slot
455532056
Off-chain at
2026-10-11T05:14:49.961Z
Anchored at
2026-10-11T05:15:17.499Z
Block time
—

Independent verification

1. Database (off-chain)
B6hjWJgkeQf1FjPaGLWuJ3oVxEs3sEjqeomoyokYVNUG
2. Recomputed (your browser)
computing…
3. On-chain (Solana memo)
fetching…
Canonical bytes hashed (1525 chars)
{"actor":"reviewer","artifact_identity":"860333eff45799b342a6ea73f9922b51","decided_at":"2026-10-11T05:14:49.854Z","decision":"review","disputed_pct":0,"findings_hash":"B2BK212njANpN47XQEjSD1MeHVEvtNFWKQWdRYx8HHvN","investigation_id":"2a48b3c5-5a6f-4913-a093-0800cc23a7e9","mode":"findings_only","new_score":69,"page_content_hash":"4709c78f860e99b7301ebb5758cd23c8274511ced3f1e845323f1ab1c668171b","page_slug":"bonk","prev_score":69,"reason":"The page's core narrative -- Bonk's Christmas 2022 launch, 50% community airdrop, January 2023 team-token burn, and Safety Shot's September 2025 treasury purchase -- is factually accurate and corroborated by independent reporting. However, several of the page's own citations do not actually support what they are cited for: the CoinMarketCap source gives a conflicting 2021 launch date, the Atomic Wallet source never mentions Safety Shot at all despite being the sole citation for that claim, and the Blockchain Council source doesn't mention a Bonk DAO despite being cited in a sentence referencing one. More materially, the page's blanket claim of 'no protocol-level exploits recorded' is now stale: a July 2026 BonkDAO governance attack drained roughly $20M from the project's treasury, an incident the page omits entirely. No disputed (outright-contradicted) claims were found, and no accepted community submissions existed to review.","score_delta":0,"sequence_num":5,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}