Algorand launched native Falcon-1024 accounts in August. Vet, an XRPL validator, responded sharply, noting that quantum‑secure wallets represent only one layer of protection. He added that Algorand is not yet fully quantum‑resistant, since much of its network continues to rely on Ed25519 signatures.
The core issue isn’t who first announced quantum‑day readiness on social media. It’s about which network is actively strengthening its signatures, consensus mechanisms, and validator infrastructure to withstand a future quantum computer capable of converting today’s public keys into compromised accounts.
Algorand Has Mainnet Ink. Consensus’s Still Hard
Algorand (ALGO) enjoys an early‑deployment advantage. Its state proofs have employed Falcon since 2022, and the v5.0.0 upgrade introduced native Falcon‑1024 accounts, which went live around August 20.
Initial metrics show roughly 1,800 quantum‑resilient accounts and over 1.2 million quantum‑resilient transactions in the opening weeks.
These accounts coexist with traditional Ed25519 addresses. Executing Falcon‑based transactions incurs higher fees—typically three times the standard cost. The foundation’s roadmap still targets 2027 for broader quantum resistance, which would encompass post‑quantum VRFs and consensus‑layer messaging.
Todd, an Algorand community member participating in the discussion, acknowledged the same point: two components are complete, with the most challenging element still pending.
Thus Algorand is ahead in delivering live post‑quantum account tools, yet it has not yet converted the entire stack to quantum‑resistant algorithms.
XRPL Is Auditing The Plumbing, Not Just The Keys
Vet’s observation explains why Ripple has commissioned Project Eleven to examine validators, custody, networking, and wallets—not just account signatures. Ripple’s published plan calls for hybrid testing circa 2027, aiming for full readiness by 2028. This timeline remains a contributor‑driven roadmap estimate and has not yet been ratified as an official amendment on the XRPL site.
Quantum secure accounts is just one part, Algorand is not fully quantum ready either. Lots of Ed25519 use on the network.
That’s why Project 11 is looking into Validators and other parts of the XRP Ledger as well to assess where we need to work on.
— Vet (@Vet_X0) September 9, 2026
XRPL’s most practical advantage lies in the RegularKey feature, which permits users to rotate signing keys while retaining the same address. If post‑quantum signatures such as ML‑DSA (or Dilithium) prove bulky—as Ripple’s benchmarks suggest—this key‑rotation capability becomes more valuable than any marketing slogan.
Today’s mainnet continues to rely on secp256k1 and Ed25519 keys. AlphaNet has been experimenting with ML‑DSA, but a production deployment has not yet been realized.
Ethereum’s public discussion still points to a 2029 timeline for quantum readiness, and no participant in this conversation has completed the transition.
What This Truly Means From a Broader Perspective
Quantum threats follow a harvest‑now, decrypt‑later model: adversaries can copy public keys today and decrypt them later once a sufficiently powerful quantum computer exists. Deploying Falcon accounts narrows the exposure window for users who actually migrate, whereas retaining elliptic‑curve consensus does not.
For Algorand, the narrative centers on being first to market with post‑quantum accounts and accruing early transaction volume. For XRP, the focus is on conducting a comprehensive audit of the ledger’s components, targeting a later mainnet rollout, and leveraging its built‑in key‑rotation mechanism. A cooperative approach would represent the mature path forward.
A triumphal claim of being “quantum‑proof” would be premature. Until the consensus layer itself adopts post‑quantum cryptography, both networks remain in the midst of an upgrade—one bearing more scars from mainnet exposure, the other facing a longer checklist of remaining tasks.
