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 · LetsBonk.fun
- Sequence
- #3
- Score
- 32 → 20 (-12)
- Cluster
- mainnet-beta
- Slot
- 443512804
- Off-chain at
- 2026-08-25T08:23:55.469Z
- Anchored at
- —
- Block time
- —
Independent verification
- 1. Database (off-chain)
- EXfkcymcCgbtyDRqC2oDeMW7roP352rW3Tjd236xHwj6
- 2. Recomputed (your browser)
- computing…
- 3. On-chain (Solana memo)
- fetching…
Canonical bytes hashed (1530 chars)
{"actor":"judge","decided_at":"2026-08-25T08:23:55.233Z","decision":"review_revise","investigation_id":"2b04a3b8-f566-4bd0-9324-52dcd43720db","new_score":20,"page_slug":"letsbonk-fun","prev_score":32,"reason":"An independent fact-check of this page found its core narrative -- the platform's rapid 2025 market-share surge, its March 2026 domain-hijack incident, and its bundler-tooling risk profile -- well supported by the cited sources, with 18 of 31 checked claims fully confirmed and most major figures matched verbatim. However, the review disputed the page's statement that no financial loss was confirmed from the March 2026 hack: independent reporting documents a roughly $23,000-$30,000 confirmed loss, and a $50,000 figure cited in the same passage actually describes an unrelated phishing incident, not the Bonk.fun breach. The review also found that the page understates a related-party financial arrangement between LetsBonk.fun and Nasdaq-listed Bonk, Inc., which SEC filings describe as entitling Bonk, Inc. to 51% of gross platform revenue in perpetuity rather than the page's framing of 'a distinct but separate' entity. Combined with a broken and mismatched citation used to support year-end-2025 performance figures, these issues are real but do not undermine the page's overall accuracy, so the page should be revised rather than removed or approved without changes.","score_delta":-12,"sequence_num":3,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}