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 · BonkBot
- Sequence
- #3
- Score
- 62 → 54 (-8)
- Cluster
- mainnet-beta
- Slot
- 423482130
- Off-chain at
- 2026-06-01T00:21:11.065Z
- Anchored at
- —
- Block time
- —
Independent verification
- 1. Database (off-chain)
- 7RVuB4EnNVnFBW2SrBX5pwSYDZj2RL6QyMHmFNQw8Aqr
- 2. Recomputed (your browser)
- computing…
- 3. On-chain (Solana memo)
- fetching…
Canonical bytes hashed (1423 chars)
{"actor":"judge","decided_at":"2026-06-01T00:21:10.791Z","decision":"review_revise","investigation_id":"691f4a75-e5d0-4cc7-a668-7a3042eef2ba","new_score":54,"page_slug":"bonkbot","prev_score":62,"reason":"The BonkBot page is well-sourced overall — 27 of 38 claims confirmed, no link rot, no stale citations, and all core incident and metric facts verified. However, two of the three disputed claims are concrete factual errors rather than omissions. First, claim_findings[24] states that '20% of purchased BONK tokens are immediately burned,' but three credible Tier 2 sources (Solana Compass, BONK DAO Medium, Coin360) consistently cite 10%; this is a high-priority correction on a financial product page. Second, claim_findings[31] creates an internal contradiction: the page cites BonkBot's own Terms of Service and then asserts no corporate entity name has been publicly disclosed, when that same ToS identifies Triple Spice AG (CHE-360.253.977, Zug, Switzerland). The third disputed claim — regarding the absence of a third-party security audit — is softer, as the reviewer could not retrieve the OtterSec report directly, but the page should acknowledge the known OtterSec engagement. These errors require targeted correction; no full revision or status change is warranted.","score_delta":-8,"sequence_num":3,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}