← Firedancer1 decision on this page
Audit log
Every state-changing event for Firedancer: moderation decisions on community submissions, plus corrections and updates from the news pipeline. URL-based decisions carry three independent witnesses — the original source, an Internet Archive snapshot taken at submission time, and a Solana memo signed by our publicly-disclosed publisher key.
- #1publishby system:backfill2026-06-01 03:22:26ZScore: ? → ? (no score change)anchoranchored
- chain
- ●mainnet-betaslot 423,509,483
- sig
5PpxwjyvimjG…oCMxSmUgexplorer ↗- hash
5BTKndGLAyYU…GK2vriwdsha256 → base58
verifying row…full verify ↗canonical bytes (25216 B) ▸
{"actor":"system:backfill","investigation_id":"e4410d80-971b-417f-8de2-3283603d1536","kind":"publish","page_slug":"firedancer","published_at":"2026-06-01T03:22:26.635Z","sequence_num":1,"snapshot":{"content_type":"investigation","entity_name":"Firedancer","sections":[{"content":"Firedancer is a complete ground-up rewrite of the Solana validator client in the C programming language, developed by Jump Crypto — the crypto division of Chicago-based proprietary trading firm Jump Trading Group. The project was announced in 2022 and describes itself as drawing its concurrency model from low-latency trading system design, applying high-frequency-trading-style architecture to blockchain consensus software. The codebase is available at https://github.com/firedancer-io/firedancer under the Apache 2.0 license. The project produces two distinct validator implementations from a shared codebase: 'Frankendancer,' a hybrid client combining Firedancer's networking and block-production stack with the existing Rust-based Agave runtime (available on mainnet since September 2024); and the pure 'Firedancer' client, which was confirmed live on mainnet in late 2024 and into 2025. Official documentation is maintained at https://docs.firedancer.io. The client requires a Linux environment with kernel v4.18 or newer and must be compiled from source. As of May 2026, the GitHub repository shows approximately 1,500 stars and 485 forks.","heading":"Project Overview","severity":"low","sources":[{"credibility":1,"name":"GitHub - firedancer-io/firedancer","type":"official","url":"https://github.com/firedancer-io/firedancer"},{"credibility":1,"name":"Why is Jump Trading Group creating Firedancer? (official docs)","type":"official","url":"https://docs.firedancer.io/guide/firedancer.html"},{"credibility":2,"name":"Jump Crypto's Firedancer hits Solana mainnet — The Block","type":"news_article","url":"https://www.theblock.co/post/382411/jump-cryptos-firedancer-hits-solana-mainnet-as-the-network-aims-to-unlock-1-million-tps"}]},{"content":"Firedancer is funded and staffed by Jump Crypto, the crypto arm of Jump Trading Group, one of the largest proprietary trading and market-making firms in traditional and digital asset markets. Jump Trading is a named, well-known entity with decades of institutional history. Jump Crypto's involvement provides significant credibility and resources: the firm absorbed a $325 million loss from the February 2022 Wormhole bridge hack on its own balance sheet to protect the ecosystem. However, the backer carries material regulatory risk. In December 2024, Tai Mo Shan Limited — a Jump Crypto subsidiary — agreed to pay $123 million to settle SEC charges that it had negligently misled investors about the stability of TerraUSD (UST) in 2021, specifically by secretly purchasing $20 million of UST to maintain its dollar peg without public disclosure, and by acting as an unregistered underwriter for LUNA tokens. The settlement included $73.45 million in disgorgement, $12.9 million in prejudgment interest, and a $36.7 million civil penalty. Separately, Bloomberg and Fortune reported in June 2024 that the U.S. CFTC was investigating Jump Crypto's trading and investment activities; Kanav Kariya, who had led Jump Crypto, stepped down that same month. As of May 2026, no public outcome or resolution of the CFTC investigation has been disclosed. These regulatory actions concern Jump Crypto's trading and financial activities and are not directly connected to Firedancer's software or operation, but they constitute a material counterparty risk signal for entities evaluating trust in the backer.","heading":"Backer: Jump Crypto / Jump Trading Group","severity":"medium","sources":[{"credibility":1,"name":"SEC: Tai Mo Shan to Pay $123 Million for Negligently Misleading Investors About TerraUSD (press release)","type":"regulatory","url":"https://www.sec.gov/newsroom/press-releases/2024-212"},{"credibility":1,"name":"Bloomberg: Jump Trading's Tai Mo Shan to Pay $123 Million in SEC Settlement","type":"news_article","url":"https://www.bnnbloomberg.ca/business/company-news/2024/12/20/jump-tradings-tai-mo-shan-to-pay-123-million-in-sec-settlement/"},{"credibility":2,"name":"The Block: SEC fines Jump Trading subsidiary $123 million over TerraUSD","type":"news_article","url":"https://www.theblock.co/post/332096/sec-fines-jump-trading-subsidiary-123-million-for-propping-up-terrausd-stablecoin-during-depeg"},{"credibility":2,"name":"CFTC is probing Jump Crypto (Yahoo Finance / Fortune)","type":"news_article","url":"https://finance.yahoo.com/news/cftc-probing-jump-crypto-previously-154527304.html"},{"credibility":2,"name":"Blockworks: Jump Crypto covered Wormhole $325M hack loss","type":"news_article","url":"https://blockworks.com/news/jump-crypto-wormhole-hack-recovery"}]},{"content":"Firedancer is fully open source under the Apache 2.0 license, hosted at https://github.com/firedancer-io/firedancer. The primary codebase is written approximately 94% in C, reflecting the team's emphasis on low-level hardware optimization. The organization also maintains a protocol specifications repository at https://github.com/firedancer-io/specs, and public audit reports are tracked at https://github.com/firedancer-io/audits. Contributions are accepted from the public per the project's README. The open-source release allows independent review of the code and is consistent with the project's stated goal of improving Solana network resilience through client diversity. No proprietary components, closed-source runtime modules, or paywalled dependencies have been identified.","heading":"Open-Source Status","severity":"low","sources":[{"credibility":1,"name":"GitHub - firedancer-io/firedancer (Apache 2.0 license)","type":"official","url":"https://github.com/firedancer-io/firedancer"},{"credibility":1,"name":"GitHub - firedancer-io/audits","type":"official","url":"https://github.com/firedancer-io/audits"},{"credibility":1,"name":"GitHub - firedancer-io/specs","type":"official","url":"https://github.com/firedancer-io/specs"}]},{"content":"Firedancer has undergone multiple published third-party security audits and a public bug-bounty competition. The audits repository (https://github.com/firedancer-io/audits) contains reports from Atredis Partners (v0.1), Cure53 (GUI/HTTP interface and metrics subsystems), and Neodyme AG (v0.1 and v0.4). The Neodyme v0.1 audit found no remote code execution (RCE) vulnerabilities but identified two high-severity issues, one of which would allow a remote attacker to crash the Firedancer process. The Neodyme v0.4 audit (February–March 2025) found no RCE vulnerabilities; most findings were denial-of-service scenarios, particularly in the QUIC networking stack, with one high-severity issue related to an unintuitive Agave feature activation; all issues were addressed and the fixes were verified by Neodyme. In addition, Firedancer ran an Immunefi audit competition from July 10 to August 21, 2024, offering a $1 million bug bounty pool — the largest in the pre-mainnet phase. Firedancer founding engineer Ritchie Patel stated in May 2026 that the completed competition gave Jump 'additional confidence' in expanding the rollout, but added: 'We don't want everybody to run it yet. If half the network upgrades before we've done full security audits, that would be a bit much.' An ongoing Immunefi bug bounty program with tiered rewards remains active. The security posture is consistent with a responsible, institutionally backed open-source infrastructure project, though full network-wide deployment remains contingent on the completion of further audits.","heading":"Security Audits and Testing Track Record","severity":"medium","sources":[{"credibility":2,"name":"Neodyme: Security Audit — Firedancer v0.4","type":"research","url":"https://neodyme.io/reports/Firedancer-v0.4.pdf"},{"credibility":2,"name":"Neodyme: Security Audit — Firedancer v0.1","type":"research","url":"https://neodyme.io/reports/Firedancer.pdf"},{"credibility":2,"name":"Immunefi: Firedancer v0.1 Bug Bounty Audit Comp","type":"other","url":"https://immunefi.com/audit-competition/firedancer-boost/information/"},{"credibility":2,"name":"Immunefi: Firedancer ongoing bug bounty program","type":"other","url":"https://immunefi.com/bug-bounty/firedancer/information/"},{"credibility":2,"name":"CoinDesk: Firedancer taking slow-and-steady approach (May 2026)","type":"news_article","url":"https://www.coindesk.com/tech/2026/05/16/jump-crypto-s-firedancer-is-taking-a-slow-and-steady-approach-to-its-long-awaited-solana-infrastructure-rollout"},{"credibility":1,"name":"GitHub - firedancer-io/audits (audit index)","type":"official","url":"https://github.com/firedancer-io/audits"}]},{"content":"Prior to the emergence of Firedancer, Solana operated in a near-monoculture: approximately 72% of staking power ran Jito-Agave (itself a fork of the Agave client from Anza), meaning a single implementation bug could theoretically disable the majority of the network's stake. Solana experienced seven network outages in its first five years of operation, with at least five attributable to validator or client-level bugs rather than fundamental protocol flaws. Firedancer is written in a different language (C vs. Rust), by a different team, with no shared codebase with Agave or Jito — creating a genuinely independent failure domain. As of early 2026, approximately 20% of Solana validators (around 207 of roughly 992 active validators) had adopted Firedancer or Frankendancer, representing approximately 20% of total staked SOL. Solana's stated target is 50% Firedancer stake by Q2–Q3 2026, at which point the network would become resilient against any single-implementation failure. Until that threshold is reached, Agave and its derivatives still represent a supermajority of the network's stake. Separately, critics have noted that while Firedancer improves client diversity, it concentrates the second major client in a single entity — Jump Crypto — rather than distributing its development across multiple independent teams as Ethereum has done. This is a structural risk signal, though one mitigated by the Apache 2.0 open-source licensing.","heading":"Client Diversity and Network Centralization","severity":"medium","sources":[{"credibility":2,"name":"CryptoSlate: Firedancer is live but Solana is violating the one safety rule Ethereum treats as non-negotiable","type":"news_article","url":"https://cryptoslate.com/firedancer-is-live-but-solana-is-violating-the-one-safety-rule-ethereum-treats-as-non-negotiable/"},{"credibility":2,"name":"BlockEden: Solana Client Diversity — Firedancer, Agave, and the Race to 1M TPS (March 2026)","type":"research","url":"https://blockeden.xyz/blog/2026/03/16/solana-client-diversity-agave-firedancer-1m-tps-mainnet-validator-ecosystem/"},{"credibility":3,"name":"OpenPR: Firedancer reaches 20% validator adoption","type":"news_article","url":"https://www.openpr.com/news/4438349/solana-sol-firedancer-reaches-20-validator-adoption-smart"},{"credibility":3,"name":"Wen Firedancer — adoption tracker","type":"other","url":"https://www.wenfiredancer.com/"}]},{"content":"Firedancer's architecture is modeled after high-frequency trading (HFT) system design. Key technical characteristics include: (1) a modular 'tile' architecture that runs each subsystem as an isolated process with sandboxed system calls, reducing attack surface and improving fault isolation; (2) a custom QUIC/UDP networking stack using kernel-bypass techniques, which in testing demonstrated packet ingress and block distribution capacity exceeding one million transactions per second; (3) a custom AVX512-accelerated Ed25519 signature verification routine enabling massively parallel cryptographic checks across CPU cores; and (4) complete independence from the Agave Rust codebase, sharing no library dependencies or language runtime. During pre-mainnet testing in Breakpoint 2024 workshop demonstrations, a globally distributed Frankendancer testnet across London, New York, Frankfurt, and Singapore processed approximately 1.04 million TPS with the leader node sustaining 5.12 Gbps of outbound traffic at peak. These benchmarks have not been independently replicated under full mainnet conditions as of May 2026. The full pure-Firedancer client, as distinguished from Frankendancer, targets but has not yet achieved verified 1M TPS in production.","heading":"Performance Claims and Technical Design","severity":"low","sources":[{"credibility":2,"name":"Solana Compass: Frankendancer 1M TPS Breakpoint 2024 workshop","type":"other","url":"https://solanacompass.com/learn/breakpoint-24/breakpoint-2024-workshop-cranking-up-frankendancer"},{"credibility":2,"name":"Blockdaemon: Solana Firedancer Validator Client Deep Dive","type":"research","url":"https://www.blockdaemon.com/blog/solanas-firedancer-validator-client-deep-dive"},{"credibility":2,"name":"Backpack Exchange: What Is Firedancer and Why It Matters for Solana","type":"other","url":"https://learn.backpack.exchange/articles/what-is-firedancer"}]},{"content":"Frankendancer (the hybrid Firedancer/Agave client) launched on Solana mainnet in September 2024 with early validator adopters. The full Firedancer client began quietly producing mainnet blocks in late 2024, having first produced a testnet block on July 10, 2024. As of May 2026, founding engineer Ritchie Patel confirmed to CoinDesk that Firedancer was 'live and running in production,' having processed tens of millions of transactions. The team is pursuing a deliberately gradual rollout: further broad adoption has been held pending completion of comprehensive third-party security audits. The Solana Foundation worked collaboratively with Jump Crypto and Anza on the rollout timeline. The client does not currently support Windows or macOS, and requires a Linux environment with kernel 4.18 or later and must be compiled from source, which raises the operational barrier relative to Agave. No emergency halts, chain splits, or consensus failures attributable to Firedancer have been reported on mainnet as of this writing.","heading":"Mainnet Rollout and Deployment Status","severity":"low","sources":[{"credibility":2,"name":"CoinDesk: Firedancer taking slow-and-steady approach (May 2026)","type":"news_article","url":"https://www.coindesk.com/tech/2026/05/16/jump-crypto-s-firedancer-is-taking-a-slow-and-steady-approach-to-its-long-awaited-solana-infrastructure-rollout"},{"credibility":2,"name":"Unchained: Jump Crypto's Firedancer Goes Live on Solana Mainnet","type":"news_article","url":"https://unchainedcrypto.com/jump-cryptos-firedancer-goes-live-on-solana-mainnet/"},{"credibility":2,"name":"Crypto.news: Firedancer quietly hits Solana mainnet, but validators must wait","type":"news_article","url":"https://crypto.news/firedancer-quietly-hits-solana-mainnet-but-validators-must-wait/"},{"credibility":1,"name":"Firedancer official docs: Getting Started","type":"official","url":"https://docs.firedancer.io/guide/getting-started.html"}]},{"content":"Firedancer is widely viewed within the Solana ecosystem as a net positive for network resilience and a significant infrastructure achievement. The Solana Foundation has publicly supported and collaborated with the team. Independent analysts and infrastructure providers such as Blockdaemon and Cherry Servers have published favorable technical assessments. The project has no known history of rug pulls, fund misappropriation, or user harm. Jump Crypto's pivot toward infrastructure (Firedancer, Pyth, Wormhole, DoubleZero) has been noted by industry observers as a possible repositioning following the reputational fallout from the Tai Mo Shan SEC settlement and Kanav Kariya's departure. The main concerns cited in independent commentary are: (1) the concentration of Solana's second major client in a single profit-driven trading firm; (2) the incomplete state of security audits relative to full network deployment; and (3) the ongoing but unresolved CFTC investigation into Jump Crypto's trading activities. None of these concerns involve allegations of fraud or misuse of user funds in connection with Firedancer itself.","heading":"Reputation and Ecosystem Relationships","severity":"low","sources":[{"credibility":2,"name":"PANews: From crypto-quant giant to infrastructure hermit, Jump Crypto's transformation","type":"news_article","url":"https://www.panewslab.com/en/articles/gsm6ee1j"},{"credibility":2,"name":"Blockdaemon: Solana Firedancer Validator Client Deep Dive","type":"research","url":"https://www.blockdaemon.com/blog/solanas-firedancer-validator-client-deep-dive"},{"credibility":2,"name":"CoinDesk: Firedancer taking slow-and-steady approach (May 2026)","type":"news_article","url":"https://www.coindesk.com/tech/2026/05/16/jump-crypto-s-firedancer-is-taking-a-slow-and-steady-approach-to-its-long-awaited-solana-infrastructure-rollout"}]}],"sources_used":[{"credibility":1,"name":"GitHub - firedancer-io/firedancer","type":"official","url":"https://github.com/firedancer-io/firedancer"},{"credibility":1,"name":"Firedancer official documentation","type":"official","url":"https://docs.firedancer.io/"},{"credibility":1,"name":"SEC: Tai Mo Shan to Pay $123 Million for Negligently Misleading Investors About TerraUSD","type":"regulatory","url":"https://www.sec.gov/newsroom/press-releases/2024-212"},{"credibility":1,"name":"Bloomberg / BNN Bloomberg: Jump Trading's Tai Mo Shan to Pay $123 Million in SEC Settlement","type":"news_article","url":"https://www.bnnbloomberg.ca/business/company-news/2024/12/20/jump-tradings-tai-mo-shan-to-pay-123-million-in-sec-settlement/"},{"credibility":2,"name":"The Block: SEC fines Jump Trading subsidiary $123 million over TerraUSD","type":"news_article","url":"https://www.theblock.co/post/332096/sec-fines-jump-trading-subsidiary-123-million-for-propping-up-terrausd-stablecoin-during-depeg"},{"credibility":2,"name":"The Block: Jump Crypto's Firedancer hits Solana mainnet","type":"news_article","url":"https://www.theblock.co/post/382411/jump-cryptos-firedancer-hits-solana-mainnet-as-the-network-aims-to-unlock-1-million-tps"},{"credibility":2,"name":"CoinDesk: Firedancer taking slow-and-steady approach (May 2026)","type":"news_article","url":"https://www.coindesk.com/tech/2026/05/16/jump-crypto-s-firedancer-is-taking-a-slow-and-steady-approach-to-its-long-awaited-solana-infrastructure-rollout"},{"credibility":2,"name":"Unchained: Jump Crypto's Firedancer Goes Live on Solana Mainnet","type":"news_article","url":"https://unchainedcrypto.com/jump-cryptos-firedancer-goes-live-on-solana-mainnet/"},{"credibility":2,"name":"Neodyme AG: Security Audit — Firedancer v0.4","type":"research","url":"https://neodyme.io/reports/Firedancer-v0.4.pdf"},{"credibility":2,"name":"Neodyme AG: Security Audit — Firedancer v0.1","type":"research","url":"https://neodyme.io/reports/Firedancer.pdf"},{"credibility":2,"name":"Immunefi: Firedancer v0.1 Bug Bounty Audit Competition","type":"other","url":"https://immunefi.com/audit-competition/firedancer-boost/information/"},{"credibility":1,"name":"GitHub - firedancer-io/audits","type":"official","url":"https://github.com/firedancer-io/audits"},{"credibility":2,"name":"CryptoSlate: Firedancer is live, Solana client diversity risk analysis","type":"news_article","url":"https://cryptoslate.com/firedancer-is-live-but-solana-is-violating-the-one-safety-rule-ethereum-treats-as-non-negotiable/"},{"credibility":2,"name":"BlockEden: Solana Client Diversity — Agave and Firedancer (March 2026)","type":"research","url":"https://blockeden.xyz/blog/2026/03/16/solana-client-diversity-agave-firedancer-1m-tps-mainnet-validator-ecosystem/"},{"credibility":2,"name":"Yahoo Finance / Fortune: CFTC probing Jump Crypto","type":"news_article","url":"https://finance.yahoo.com/news/cftc-probing-jump-crypto-previously-154527304.html"},{"credibility":2,"name":"Blockworks: Jump Crypto covered Wormhole $325M hack","type":"news_article","url":"https://blockworks.com/news/jump-crypto-wormhole-hack-recovery"},{"credibility":2,"name":"Solana Compass: Breakpoint 2024 — Firedancer keynote (Kevin Bowers)","type":"other","url":"https://solanacompass.com/learn/breakpoint-24/breakpoint-2024-keynote-fast-forward-from-frankendancer-to-firedancer-kevin-bowers"},{"credibility":2,"name":"Blockdaemon: Solana's Firedancer Validator Client Deep Dive","type":"research","url":"https://www.blockdaemon.com/blog/solanas-firedancer-validator-client-deep-dive"},{"credibility":2,"name":"crypto.news: Firedancer quietly hits Solana mainnet","type":"news_article","url":"https://crypto.news/firedancer-quietly-hits-solana-mainnet-but-validators-must-wait/"},{"credibility":2,"name":"Unchained: $1 Million Bounty On Offer for Finding Bugs in Firedancer","type":"news_article","url":"https://unchainedcrypto.com/1-million-bounty-on-offer-for-finding-bugs-on-solana-validator-client-firedancer/"}],"summary":"Firedancer is an independent, high-performance Solana validator client developed by Jump Crypto (Jump Trading Group), written from scratch in C primarily by a team led by Chief Science Officer Dr. Kevin Bowers and founding engineer Ritchie Patel. Released under the Apache 2.0 open-source license, it aims to increase Solana's throughput toward one million transactions per second while improving network resilience through client diversity. As of May 2026, the client is live on Solana mainnet with roughly 20% of validators running it, though full rollout remains cautious pending completion of comprehensive third-party security audits. The project carries a notable backer-risk signal: Jump Crypto's parent subsidiary Tai Mo Shan settled SEC charges for $123 million in December 2024 over TerraUSD manipulation, and a separate CFTC investigation was reported in 2024 with no publicly disclosed outcome as of this writing.","timeline":[{"date":"2022-01-01","event":"Jump Crypto publicly announces Firedancer, a ground-up rewrite of the Solana validator client in C.","source":"Jump Crypto / various crypto news coverage","source_url":"https://jumpcrypto.com/build/firedancer"},{"date":"2022-02-02","event":"Wormhole bridge (associated with Jump Crypto) exploited for approximately $325 million; Jump Crypto covers the loss from its own balance sheet.","source":"Blockworks","source_url":"https://blockworks.com/news/jump-crypto-wormhole-hack-recovery"},{"date":"2024-07-10","event":"Firedancer produces its first testnet block, demonstrating end-to-end consensus capability on Solana testnet.","source":"Various crypto news / Immunefi audit competition announcement","source_url":"https://immunefi.com/audit-competition/firedancer-boost/information/"},{"date":"2024-07-10","event":"Immunefi public audit competition for Firedancer v0.1 begins, with a $1 million bug bounty pool; competition runs through August 21, 2024.","source":"Unchained / Immunefi","source_url":"https://unchainedcrypto.com/1-million-bounty-on-offer-for-finding-bugs-on-solana-validator-client-firedancer/"},{"date":"2024-06-24","event":"Bloomberg reports CFTC is investigating Jump Crypto's trading activities; Jump Crypto president Kanav Kariya steps down.","source":"Bloomberg / Yahoo Finance","source_url":"https://finance.yahoo.com/news/cftc-probing-jump-crypto-previously-154527304.html"},{"date":"2024-09-01","event":"Frankendancer (hybrid Firedancer/Agave client) launches on Solana mainnet with early adopters.","source":"The Block","source_url":"https://www.theblock.co/post/382411/jump-cryptos-firedancer-hits-solana-mainnet-as-the-network-aims-to-unlock-1-million-tps"},{"date":"2024-12-20","event":"SEC announces $123 million settlement with Tai Mo Shan Limited (Jump Crypto subsidiary) for negligently misleading investors about TerraUSD stability in 2021.","source":"SEC.gov press release","source_url":"https://www.sec.gov/newsroom/press-releases/2024-212"},{"date":"2024-12-01","event":"Full Firedancer client begins producing blocks on Solana mainnet after approximately 100 days of pre-launch testing generating 50,000+ blocks.","source":"Unchained / CryptoSlate","source_url":"https://unchainedcrypto.com/jump-cryptos-firedancer-goes-live-on-solana-mainnet/"},{"date":"2025-02-01","event":"Neodyme AG conducts security audit of Firedancer v0.4; finds one high-severity DoS issue in QUIC stack (no RCE vulnerabilities); all issues addressed.","source":"Neodyme AG audit report","source_url":"https://neodyme.io/reports/Firedancer-v0.4.pdf"},{"date":"2025-10-01","event":"Approximately 207 of 992 Solana validators (roughly 21% of stake) running Firedancer or Frankendancer, per adoption tracker data.","source":"BlockEden / Wenfiredancer.com","source_url":"https://blockeden.xyz/blog/2026/03/16/solana-client-diversity-agave-firedancer-1m-tps-mainnet-validator-ecosystem/"},{"date":"2026-05-16","event":"CoinDesk reports Firedancer is live on mainnet with tens of millions of transactions processed; founding engineer Ritchie Patel confirms cautious, audit-gated rollout strategy.","source":"CoinDesk","source_url":"https://www.coindesk.com/tech/2026/05/16/jump-crypto-s-firedancer-is-taking-a-slow-and-steady-approach-to-its-long-awaited-solana-infrastructure-rollout"}]},"v":1}Verify offline (run on your own machine)python -m src.verify_decision 146340f8-17a4-404e-8200-51907023d6d4
How verification works. The “Row integrity” check above is computed in your browser — your machine recomputes the SHA-256 of the canonical bytes and compares against the stored hash. No avoid.net server can fake that check. The “full verify” link goes one level deeper: your browser fetches the on-chain transaction from a Solana RPC node and confirms the same hash is in the memo. If you don’t want to trust either avoid.net or the public RPC, run the CLI verifier on your own machine —
python -m src.verify_decision <event_id>.