Skip to main content
Sign in
← avoid.net

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

  1. 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.
  2. 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.
  3. 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
View on Solana ↗
Sequence
#4
Score
68 → 68 (0)
Cluster
mainnet-beta
Slot
424166687
Off-chain at
2026-06-04T03:57:52.613Z
Anchored at
—
Block time
—

Independent verification

1. Database (off-chain)
HPuSeNra6UdzznQDp3Kbi7cYGmfUGLMhXikCaqgEnP8f
2. Recomputed (your browser)
computing…
3. On-chain (Solana memo)
fetching…
Canonical bytes hashed (1224 chars)
{"actor":"reviewer","decided_at":"2026-06-04T03:57:52.499Z","decision":"review","investigation_id":"e4410d80-971b-417f-8de2-3283603d1536","new_score":68,"page_slug":"firedancer","prev_score":68,"reason":"The investigation page is broadly accurate and well-sourced, with no fabricated or disputed claims identified. The recurring material inaccuracy is the Wormhole hack loss amount: the page states $325 million in two locations, while authoritative contemporaneous sources (CoinDesk, CNBC, Chainalysis) consistently report approximately $320 million. A second structural issue is the announcement timeline entry dated 2022-01-01, when the actual public announcement occurred at Solana Breakpoint in November 2022. Two cited URLs (blockworks.com/news/jump-crypto-wormhole-hack-recovery and unchainedcrypto.com/jump-cryptos-firedancer-goes-live-on-solana-mainnet/) returned HTTP 403 errors during link checking. A notable coverage gap is the omission of the Firedancer V1 Immunefi audit competition that ran April-May 2026, which is directly relevant to the security posture section.","score_delta":0,"sequence_num":4,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}