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 · Firedancer
- Sequence
- #2
- Score
- 76 → 76 (0)
- Cluster
- mainnet-beta
- Slot
- 423649710
- Off-chain at
- 2026-06-01T18:50:17.708Z
- Anchored at
- —
- Block time
- —
Independent verification
- 1. Database (off-chain)
- 86GYn6HRkJDrCUULb7hhae7txuc8qZXQqGiitkdZq8NJ
- 2. Recomputed (your browser)
- computing…
- 3. On-chain (Solana memo)
- fetching…
Canonical bytes hashed (934 chars)
{"actor":"reviewer","decided_at":"2026-06-01T18:50:17.631Z","decision":"review","investigation_id":"e4410d80-971b-417f-8de2-3283603d1536","new_score":76,"page_slug":"firedancer","prev_score":76,"reason":"The Firedancer investigation page is broadly accurate and well-sourced on regulatory facts (SEC settlement amounts, Wormhole hack, audit firms). The primary issues are stale adoption metrics: the page's '~20% of validators' figure originates from October 2025 BlockEden data; wenfiredancer.com as of June 1, 2026 shows 87 of 754 validators (11.5% by count) at 15.11% stake. Two claims are unverifiable due to PDF access limitations (v0.4 audit findings) and lack of official confirmation (50% stake target timeline). No claims were found to be outright disputed by a more credible source.","score_delta":0,"sequence_num":2,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}