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 · Famous Fox Federation
- Sequence
- #3
- Score
- 72 → 62 (-10)
- Cluster
- mainnet-beta
- Slot
- 423649725
- Off-chain at
- 2026-06-01T18:50:18.704Z
- Anchored at
- —
- Block time
- —
Independent verification
- 1. Database (off-chain)
- FsqyTW7E9jTym1mwYd9nBJ3y4dLnNeJU3KpqpkpQwUF4
- 2. Recomputed (your browser)
- computing…
- 3. On-chain (Solana memo)
- fetching…
Canonical bytes hashed (1233 chars)
{"actor":"judge","decided_at":"2026-06-01T18:50:18.588Z","decision":"review_revise","investigation_id":"287d27cb-c065-40d5-9fc6-d2793cbd0d6b","new_score":62,"page_slug":"famous-fox-federation","prev_score":72,"reason":"The review found 1 disputed claim in 27 total (18.5% disputed_pct), placing this in the minor-revision band. The sole disputed finding — claim_findings[28] — is a timeline date error: the Jito Foundation Q&A is dated April 10, 2024 on the page but was published May 23, 2023, an 11-month discrepancy that should be corrected. Four claims are partially supported, all involving minor inaccuracies (a one-day Roadmap date error, a one-year rounding on DraxxTs's crypto start date, Citrus incorrectly listed as a Roadmap 2.0 item, and the ATH figure differing between CoinGecko and CoinMarketCap). Two high-priority coverage gaps — current operational status of Citrus and Rafffle in 2026, and the absence of any named or published smart contract audit — reinforce the need for revision. No core allegations are disputed and no link rot or stale citation issues were found.","score_delta":-10,"sequence_num":3,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}