Skip to main content
AVOID.NET
← 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 · Jump Trading
View on Solana ↗
Sequence
#4
Score
42 → 42 (0)
Cluster
mainnet-beta
Slot
457429064
Off-chain at
2026-10-15T23:58:13.056Z
Anchored at
2026-10-15T23:58:20.754Z
Block time
—

Independent verification

1. Database (off-chain)
FEnY4JYEbGQhoCgzMu1ex7zj5tqPgJRSVAPeEZuvHynM
2. Recomputed (your browser)
computing…
3. On-chain (Solana memo)
fetching…
Canonical bytes hashed (2016 chars)
{"actor":"reviewer","artifact_identity":"5ecb831cf239806d25a3a16567fb5cec","decided_at":"2026-10-15T23:58:12.875Z","decision":"review","disputed_pct":0.2308,"findings_hash":"F4pQfdDh2re7khbkQ3sDeiWZPhjajd7UM5cW7jTAfq8X","investigation_id":"43717013-cdf9-4ce2-b641-b43d4f40cf9b","mode":"findings_only","new_score":42,"page_content_hash":"2fc08024079eca8ee92716ad16a41fd1cd493fa4421c9ce13a9170ab0eea4ca8","page_slug":"jump-trading","prev_score":42,"reason":"The page is substantially well-sourced: the large majority of claims checked against primary or high-tier secondary sources (SEC press release, NYSE Chicago disciplinary order, CoinDesk, Bloomberg, The Block, DLNews, Protos, Blockworks) were confirmed verbatim or near-verbatim, including the exact SEC settlement figures, the FTX loss breakdown, the Wormhole hack and Oasis recovery amounts, and Jump's quoted response to the Terraform lawsuit. Two defects stand out: the Firedancer section conflates the hybrid 'Frankendancer' client's September 2024 launch and 26% adoption share with the full Firedancer client, which the page's own cited source dates to December 2025; and the NYSE Chicago $250,000 fine is dated to May 2018 (the date of the underlying incident) in both the section text and timeline, when the primary disciplinary order shows the sanction was actually issued in September 2019. A handful of recent on-chain and VC-investment claims (the $677M/47% Solana snapshot, the December 2025 USD1-to-BitGo transfer, and the Pumpcade investment date) are either unverifiable from indexed sources or, in the Pumpcade case, appear to be off by about a month against the best-attested reporting. The 61.4 million LUNA/$1.28 billion figure attributed to the December 2025 Terraform lawsuit is plausible but traces most clearly to reporting on the earlier 2023 class action rather than the new complaint itself.","score_delta":0,"sequence_num":4,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}