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_approve · Bunni Protocol
- Sequence
- #3
- Score
- 28 → 28 (0)
- Cluster
- mainnet-beta
- Slot
- 425023544
- Off-chain at
- 2026-06-08T02:49:36.765Z
- Anchored at
- —
- Block time
- —
Independent verification
- 1. Database (off-chain)
- C7JNA9GKbYdEemoBPMbFR9DBup4295hwZC5U6DSz9Qjg
- 2. Recomputed (your browser)
- computing…
- 3. On-chain (Solana memo)
- fetching…
Canonical bytes hashed (1264 chars)
{"actor":"judge","decided_at":"2026-06-08T02:49:36.535Z","decision":"review_approve","investigation_id":"02b3a7ef-82a4-4774-be3b-e9477ae03a55","new_score":28,"page_slug":"bunni-protocol","prev_score":28,"reason":"The reviewer found 0 disputed claims across 25 total claims checked, yielding a disputed_pct of 4% — well within the approve threshold. The 6 partially-supported findings (claim_findings[3], [5], [10], [13], [17], [23]) each involve minor precision issues — a one-day launch date ambiguity, an intermediate vs. peak TVL framing, an unverified audit count due to document truncation, and an incomplete description of Tornado Cash use — none of which challenge the page's core allegations about the exploit mechanism, amounts, or shutdown rationale. The one link-rot instance (claim_findings[3], HTTP 402 on the X launch post) is corroborated by multiple independent Tier 1 and Tier 2 sources. The high-priority coverage gap recommends adding on-chain transaction hashes and wallet addresses for independent verification — this is an expansion suggestion, not a factual correction, and does not warrant penalty.","score_delta":0,"sequence_num":3,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}