Markets
BTC— —
ETH— —
SOL— —
XRP— —
BNB— —
ADA— —
DOGE— —
MCap— —
BTC— —
ETH— —
SOL— —
XRP— —
BNB— —
ADA— —
DOGE— —
MCap— —
Tech

Solana's Two Independent Client Teams Both Picked the Same Post-Quantum Signature Scheme — and Both Already Have Code Live on GitHub

Anza and Jump Crypto's Firedancer reached the same conclusion on Falcon without coordinating, and the Solana Foundation has now adopted it as the network's planned post-quantum signature path.

By James Gray··4 min read
Solana's Two Independent Client Teams Both Picked the Same Post-Quantum Signature Scheme — and Both Already Have Code Live on GitHub

Key Points

  • Anza and Jump Crypto's Firedancer reached the same conclusion on Falcon without coordinating, and the Solana Foundation has now adopted it as the network's planned post-quantum signature path.

Solana's two leading client teams — Anza and Jump Crypto's Firedancer — have independently chosen the same post-quantum signature scheme, Falcon, and both have early implementations live on public GitHub repositories. The Solana Foundation outlined the plan on April 27, framing it as a precautionary roadmap rather than an immediate protocol upgrade, and described the duplicate result from two unaffiliated engineering teams as the strongest validation it could ask for.

Falcon was selected by the U.S. National Institute of Standards and Technology in 2022 as one of the approved post-quantum digital-signature algorithms, alongside Dilithium and SPHINCS+. The reason both Anza and Firedancer picked Falcon over its siblings is bandwidth, not security: Falcon's signatures are roughly half the size of Dilithium's, which matters disproportionately on a chain where transactions per second is the headline metric and every byte added to a signature compounds across the network's throughput. For Solana, big signatures are not just inefficient — they are an existential threat to the design.

The current schedule has three phases. Phase one is continued research into Falcon and adjacent schemes, which is already underway and where most of the public commits sit. Phase two introduces post-quantum signatures for new wallets if and when quantum risk escalates. Phase three migrates existing wallets, which is the hardest part of the entire process for any chain that did not build a key-rotation primitive into its base layer. Solana's foundation explicitly said "no change is required today or likely anytime soon" — the framing is precautionary, not urgent.

Advertisement

728×90

Quantum threat models in cryptography are notoriously slippery. Most credible academic estimates put a cryptographically relevant quantum computer somewhere between five and fifteen years away, depending on which qubit count and error-correction milestone you set as the bar. The recent demonstration in which a researcher broke a 15-bit elliptic-curve key on a quantum computer was not a near-term threat to Bitcoin or Solana — secp256k1 and Ed25519 use 256-bit keys — but it was the first time a real quantum machine had factored a non-toy elliptic-curve key in a peer-reviewed setup. The trajectory matters even if the absolute level does not.

Bitcoin and Ethereum, by comparison, have not formalised post-quantum migration paths. Bitcoin Core developers have discussed Falcon, Dilithium and even more exotic lattice schemes on the mailing list for years, but no BIP has reached consensus, and the political fight over which signature replaces ECDSA is likely to dwarf the technical one. Ethereum's roadmap mentions post-quantum cryptography as a long-term concern but defers concrete choices to post-Hegota upgrades. Solana, in publishing a phased plan with named primitives and working code, has put itself ahead of both — which is not something the network has been able to claim very often.

The cynical read on this is that announcing a quantum roadmap with no immediate implementation is closer to marketing than engineering. There is some truth to that. No L1 has had to deal with a real post-quantum migration yet, and the existing wallet-migration problem — moving billions of dollars of user funds onto new key formats without user error or front-running — is not solved by anyone. Solana's plan acknowledges this honestly: the foundation said new wallets would adopt Falcon first, with existing wallets migrated in a later phase, which is a polite way of saying nobody has worked out how to do that part yet.

What separates the announcement from pure signalling is the GitHub trail. Anza has been working on Falcon since at least January 2026 according to the project's commit history, and Firedancer's implementation is sitting in its repository as well. Two production-grade client teams shipping unrelated implementations of the same primitive is not a marketing exercise — it is the early plumbing of an upgrade that, when needed, can move from research to mainnet on a shorter timeline than starting from scratch.

Solana spent 2024 dealing with downtime and 2025 turning into the chain that institutions actually adopted; spot ETFs from Bitwise and Fidelity now hold over a billion dollars in SOL, and the network has been pulling the on-chain activity numbers Ethereum used to dominate. Quantum readiness is a different category of credibility — one that matters more to long-horizon institutional buyers than to the average retail trader. Publishing a roadmap with two competing client implementations checks a box that Bitcoin and Ethereum have not.

Both implementations are public on GitHub. Neither has been merged into mainnet client builds, and the Solana Foundation has not committed to a target activation block.

MiningPool content is intended for information and educational purposes only and does not constitute financial, investment, or legal advice.

Advertisement

728×90

Related Stories

Drift's Recovery Pool Pays About a Cent on Every Dollar Lost
Markets

The Drift Foundation issued one DFX token for each verified dollar taken in April's exploit, and the pool behind those 299.5 million tokens holds about $3.11 million. Tether and other partners have pledged up to $147.5 million more, none of which has arrived.

·MiningPool Staff
Buterin Expects Hegotá to Be Ethereum's Last Normal Fork
Tech

Buterin's post puts Ethereum's 2030 target at four to eight second slots and finality in eight to 32 seconds, against 12-second slots and about 13 minutes today. It also has nodes checking a proof instead of re-executing every block.

·MiningPool Staff
Bitget Says Its Own Approval Process Released $351.6 Million
Tech

The exchange's security notice declined to name an attack vector, and hours later its chief executive said the attacker spoofed transaction data through a compromised backend system, ruling out private key theft. Withdrawals remain suspended, and the loss is close to 76 percent of the User Protection Fund Bitget says covers it.

·MiningPool Staff
Only Agave Can Run Alpenglow as Solana Starts the Testnet Phase
Tech

Anza is targeting about 150 milliseconds to finality, down from the roughly 12.8 seconds it attributes to TowerBFT, but Firedancer and Frankendancer cannot run the code yet. No mainnet date has been announced, and September 28 is a feature-gate processing date rather than a confirmed Alpenglow launch.

·MiningPool Staff
Solana's Slots Are 250ms Now and Still Run About 16ms Long
Tech

Network-reported block times put the new slots at about 267 milliseconds on average, the same roughly 16-millisecond overhead that sat on top of the 400, 350 and 300 millisecond targets before it. Block limits fell in proportion, so throughput stays at 150 million compute units a second.

·MiningPool Staff

Stay informed

Verifiable crypto journalism, delivered to your inbox.

Weekday mornings. No hype. No financial advice. Just what happened and why it matters.

No spam. Unsubscribe anytime. Read our privacy policy.