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 · BonkBot
- Sequence
- #6
- Score
- 49 → 49 (0)
- Cluster
- mainnet-beta
- Slot
- 425407972
- Off-chain at
- 2026-06-09T21:19:36.491Z
- Anchored at
- —
- Block time
- —
Independent verification
- 1. Database (off-chain)
- 5wx7Xf6FVedaFWodTGr45VPhV5PcjRecphcHRs1Yeroy
- 2. Recomputed (your browser)
- computing…
- 3. On-chain (Solana memo)
- fetching…
Canonical bytes hashed (1204 chars)
{"actor":"reviewer","decided_at":"2026-06-09T21:19:36.332Z","decision":"review","investigation_id":"691f4a75-e5d0-4cc7-a668-7a3042eef2ba","new_score":49,"page_slug":"bonkbot","prev_score":49,"reason":"The BonkBot investigation page is broadly accurate and well-sourced. Core factual claims — the March 2024 incident figures, corporate structure (Triple Spice AG), team pseudonyms, KMS announcement, competitive ranking, and regulatory non-action — are confirmed by independent sources. The principal accuracy issue is the '100% of fees to BONK buy/burn' claim, which appears to overstate the burn mechanism; BONK DAO's own documentation indicates only 10% of BonkBot fees reach the DAO treasury for burning, with the remainder allocation undocumented publicly. Volume and user count figures ($14.1B, 526K users) reflect mid-2025 Dune analytics snapshots and are inconsistent with the live homepage ($10.1B, 452K), suggesting the data may be from a peak period. The bonkbot.world FAQ URL is unreachable (ECONNREFUSED), representing one confirmed link rot finding.","score_delta":0,"sequence_num":6,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}