Solana is pitching a post-quantum bolt-on for its new consensus protocol—calling it “Quantumglow”—as part of a broader push to harden the network against future quantum attacks while keeping the sub-second finality Alpenglow promises.
What Solana announced
- On Oct. 22 Solana developers posted a video explaining Quantumglow as a proposed post-quantum adaptation of Alpenglow that would protect validator consensus against quantum-enabled forgeries while preserving fast finality. The Solana account promoted the explainer and said the network “has been early in quantum readiness and remains ahead in its preparation.”
- The announcement outlined the proposal but did not include an activation date or a dedicated Solana Improvement Document (SIMD) for Quantumglow. The work is presented as a research-driven adaptation rather than an immediate on-chain upgrade.
Where the research comes from
- The technical foundation predates the video. Anza published a Quantumglow overview on July 30 (authors: Quentin Kniep, Kobi Sliwinski and Roger Wattenhofer) and pointed readers to Section 5 of an updated Alpenglow whitepaper.
- Anza’s work identifies two core obstacles to swapping in post-quantum cryptography: (1) post-quantum signatures are much larger, and (2) Alpenglow’s compact signature-aggregation model has no direct post-quantum analog that meets the protocol’s constraints.
Key technical ideas in the proposal
- Ax (Alpenglow XMSS): a tailored, hash-based signature scheme. To reduce bandwidth and on-chain bloat, validators would pre-exchange and cache one-time public-key material ahead of use, so later signatures carry less extra data.
- Block authentication by commitment: instead of attaching a large post-quantum signature to every block payload, nodes would sign a commitment covering the payload and rely on authenticated channels—reducing per-block signature overhead.
- Distributed-quorum-signature adaptation: researchers (Kniep, Jakub Sliwinski and Wattenhofer) propose moving certificates out of network messages into locally recorded events once a node has gathered sufficient evidence. Their design uses ordinary signatures and an “approval-broadcast” mechanism, separating evidence that supports safety from that which supports liveness.
- Performance claims: the authors say message sizes remain constant per message regardless of node count, though total communication grows quadratically; these are design claims and have not been validated on mainnet.
Where Alpenglow stands now
- The Solana Foundation lists Alpenglow as active on mainnet after activation in epoch 1064 on Oct. 21. Alpenglow’s finality target is roughly 150 milliseconds (compared with Tower BFT’s approx. 12.8 seconds).
- The Foundation records Alpenglow consensus starting at slot 459,653,000, with the genesis block certified by votes from 446 of 654 validators.
- The deployed parts of Alpenglow include Votor (voting). Rotor (data distribution) is reserved for a later release and will be covered in a separate SIMD. SIMD-0326 specifies the Votor portions and references Alpenglow whitepaper v1.1.
- Migration notes: validators need compatible software and sufficient vote-account funding to participate. For ordinary users, the Foundation says transaction signing, sending and approval behavior does not change.
- Analytics impact: removing on-chain vote transactions requires block explorers and metrics providers to reset or adjust metrics that previously counted validator votes alongside user transactions.
Security context and related work
- Anza’s April 27 security assessment flagged quantum vulnerabilities across accounts, block propagation, consensus and user programs. Researchers Max Resnick and Sam Kim warned that a quantum-capable attacker able to break Ed25519 could forge account signatures and consensus votes, enabling conflicting confirmations.
- The assessment calls for account migration tooling, post-quantum transaction verification, networking updates and program-level crypto primitives, but it does not endorse a single post-quantum signature standard.
- Earlier experiments: Anza and Firedancer tested early Falcon implementations (reported April 28) as one candidate option.
- Anza also prototyped an account-migration proof that binds an existing account to a new post-quantum public key, noting that vault-style approaches alone can’t fully secure consensus, networking and all applications that rely on vulnerable signatures.
Broader industry parallels
- Bitcoin developers have considered similar mitigations. BIP-360 (a draft by Hunter Beast, Ethan Heilman and Isabel Foxen Duke) proposes Pay-to-Merkle-Root outputs to remove long-exposed key-path spending in Taproot—protecting against keys exposed for long time horizons. The draft separates that protection from attacks during the short confirmation window, which might still require post-quantum signatures. The timeline for a cryptographically relevant quantum computer remains uncertain.
Bottom line
Quantumglow is a researched roadmap for making Alpenglow post-quantum resilient without sacrificing the rapid finality Solana targets. It stacks several complementary ideas—hash-based signatures, cached one-time key material, signed commitments, and a different approach to quorum evidence—but it’s still a proposal rather than an activated upgrade. With Alpenglow already live on mainnet, Quantumglow-style changes represent the next phase of research and engineering for long-term quantum resistance across accounts, consensus, networking and application code.
What Solana announced
- On Oct. 22 Solana developers posted a video explaining Quantumglow as a proposed post-quantum adaptation of Alpenglow that would protect validator consensus against quantum-enabled forgeries while preserving fast finality. The Solana account promoted the explainer and said the network “has been early in quantum readiness and remains ahead in its preparation.”
- The announcement outlined the proposal but did not include an activation date or a dedicated Solana Improvement Document (SIMD) for Quantumglow. The work is presented as a research-driven adaptation rather than an immediate on-chain upgrade.
Where the research comes from
- The technical foundation predates the video. Anza published a Quantumglow overview on July 30 (authors: Quentin Kniep, Kobi Sliwinski and Roger Wattenhofer) and pointed readers to Section 5 of an updated Alpenglow whitepaper.
- Anza’s work identifies two core obstacles to swapping in post-quantum cryptography: (1) post-quantum signatures are much larger, and (2) Alpenglow’s compact signature-aggregation model has no direct post-quantum analog that meets the protocol’s constraints.
Key technical ideas in the proposal
- Ax (Alpenglow XMSS): a tailored, hash-based signature scheme. To reduce bandwidth and on-chain bloat, validators would pre-exchange and cache one-time public-key material ahead of use, so later signatures carry less extra data.
- Block authentication by commitment: instead of attaching a large post-quantum signature to every block payload, nodes would sign a commitment covering the payload and rely on authenticated channels—reducing per-block signature overhead.
- Distributed-quorum-signature adaptation: researchers (Kniep, Jakub Sliwinski and Wattenhofer) propose moving certificates out of network messages into locally recorded events once a node has gathered sufficient evidence. Their design uses ordinary signatures and an “approval-broadcast” mechanism, separating evidence that supports safety from that which supports liveness.
- Performance claims: the authors say message sizes remain constant per message regardless of node count, though total communication grows quadratically; these are design claims and have not been validated on mainnet.
Where Alpenglow stands now
- The Solana Foundation lists Alpenglow as active on mainnet after activation in epoch 1064 on Oct. 21. Alpenglow’s finality target is roughly 150 milliseconds (compared with Tower BFT’s approx. 12.8 seconds).
- The Foundation records Alpenglow consensus starting at slot 459,653,000, with the genesis block certified by votes from 446 of 654 validators.
- The deployed parts of Alpenglow include Votor (voting). Rotor (data distribution) is reserved for a later release and will be covered in a separate SIMD. SIMD-0326 specifies the Votor portions and references Alpenglow whitepaper v1.1.
- Migration notes: validators need compatible software and sufficient vote-account funding to participate. For ordinary users, the Foundation says transaction signing, sending and approval behavior does not change.
- Analytics impact: removing on-chain vote transactions requires block explorers and metrics providers to reset or adjust metrics that previously counted validator votes alongside user transactions.
Security context and related work
- Anza’s April 27 security assessment flagged quantum vulnerabilities across accounts, block propagation, consensus and user programs. Researchers Max Resnick and Sam Kim warned that a quantum-capable attacker able to break Ed25519 could forge account signatures and consensus votes, enabling conflicting confirmations.
- The assessment calls for account migration tooling, post-quantum transaction verification, networking updates and program-level crypto primitives, but it does not endorse a single post-quantum signature standard.
- Earlier experiments: Anza and Firedancer tested early Falcon implementations (reported April 28) as one candidate option.
- Anza also prototyped an account-migration proof that binds an existing account to a new post-quantum public key, noting that vault-style approaches alone can’t fully secure consensus, networking and all applications that rely on vulnerable signatures.
Broader industry parallels
- Bitcoin developers have considered similar mitigations. BIP-360 (a draft by Hunter Beast, Ethan Heilman and Isabel Foxen Duke) proposes Pay-to-Merkle-Root outputs to remove long-exposed key-path spending in Taproot—protecting against keys exposed for long time horizons. The draft separates that protection from attacks during the short confirmation window, which might still require post-quantum signatures. The timeline for a cryptographically relevant quantum computer remains uncertain.
Bottom line
Quantumglow is a researched roadmap for making Alpenglow post-quantum resilient without sacrificing the rapid finality Solana targets. It stacks several complementary ideas—hash-based signatures, cached one-time key material, signed commitments, and a different approach to quorum evidence—but it’s still a proposal rather than an activated upgrade. With Alpenglow already live on mainnet, Quantumglow-style changes represent the next phase of research and engineering for long-term quantum resistance across accounts, consensus, networking and application code.