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 · Firedancer
- Sequence
- #5
- Score
- 68 → 63 (-5)
- Cluster
- mainnet-beta
- Slot
- 424166690
- Off-chain at
- 2026-06-04T03:57:52.729Z
- Anchored at
- —
- Block time
- —
Independent verification
- 1. Database (off-chain)
- 9j3CP2SBsMiUp3YW2HB5HLVXp7E7mEC5uq6zseXszgCJ
- 2. Recomputed (your browser)
- computing…
- 3. On-chain (Solana memo)
- fetching…
Canonical bytes hashed (1398 chars)
{"actor":"judge","decided_at":"2026-06-04T03:57:52.499Z","decision":"review_approve","investigation_id":"e4410d80-971b-417f-8de2-3283603d1536","new_score":63,"page_slug":"firedancer","prev_score":68,"reason":"The review found zero disputed claims across 29 checked (0% disputed rate), placing this page clearly in the approve band. No fabricated or outright false claims were identified. A small score reduction is warranted because the Wormhole hack loss amount is stated as $325 million in both sections[1] and timeline[1], while Tier 1 contemporaneous sources (CoinDesk, CNBC) consistently report approximately $320 million — a recurring inaccuracy contradicted by the highest-credibility sources (claim_findings[8] and claim_findings[24]). Additionally, the summary's use of 'manipulation' slightly mischaracterizes the SEC's negligence-based finding (claim_findings[3]), and the announcement timeline entry carries a placeholder date of 2022-01-01 rather than the documented November 2022 Breakpoint announcement (claim_findings[22]). A high-priority coverage gap exists: the Firedancer V1 Immunefi audit competition (April-May 2026) is not mentioned in the security section, which materially affects the completeness of the audit posture assessment.","score_delta":-5,"sequence_num":5,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}