Two numbers are carrying this entire narrative: 2028 and 2029. One is bolted to the XRP Ledger. The other to Ethereum. Neither number arrives with a whitepaper, a named post-quantum algorithm, a filed Amendment, or a signed commit. That is the whole event. A target date, a comparison, and the claim that wallet holders will not have to change their addresses.
That should not be enough to move a mature market. Yet here we are. The XRP Ledger is said to be targeting a quantum-ready posture by 2028. Ethereum is slotted for 2029. The author of the original framing implies XRPL is ahead. The market reads it as a race. The liquidity structure reads it as a footnote — for now.
I want to be precise about what this is and what it is not, because the difference determines whether you are pricing an engineering milestone or a marketing calendar.
Context: what an account actually is on each chain
The XRPL account model is the reason this story exists. On the XRP Ledger, the Account ID — the address you send to — is not cryptographically welded to a single signing key. The protocol separates them. There is a Master Key and there is a Regular Key. There is also the multisign mechanism. In principle, you can rotate the key that authorizes transactions while the account identifier remains stable.
Ethereum does not work that way at the base layer. An externally owned account address is the last twenty bytes of the Keccak hash of the public key. Change the key, change the address. That binding is the reason a naive post-quantum swap on Ethereum is a state migration problem, not a wallet settings toggle.
Ethereum is not without exits. Account abstraction, EIP-7702, and smart contract wallets all create paths where a stable identifier routes to a swappable signing authority. The migration can be smooth. It just cannot always happen at the protocol primitive. That distinction is the entire substance behind the 2028-versus-2029 gap.
So when the source material claims XRPL plans to make wallets quantum-immune without forcing address changes, that claim is architecturally plausible in a way the Ethereum equivalent is not at the base layer. The claim is not the innovation. The pre-existing separation of account identifier and signing key is the innovation. It was designed for key rotation and recovery long before quantum computers were a marketing hook.
That is worth stating plainly. XRPL is not proposing a new consensus primitive. It is proposing to swap a signature algorithm underneath an account layer that was already modular. That is a config change at scale, not a rewrite of the ledger's core rules.
Core: the signature layer is the settlement layer
Here is the part the headlines skip. Migrating to post-quantum cryptography is not a branding exercise. It is a signature-size problem, a transaction-cost problem, and a validator-coordination problem.
Take the numbers that matter and notice they are missing. The source material names no algorithm. NIST's post-quantum standardization landed on lattice-based schemes like ML-DSA — derived from Dilithium — and hash-based options like SPHINCS+, alongside Falcon. A Dilithium-class public key and signature run into the low kilobytes. Ed25519 signatures are 64 bytes. That is not a rounding difference. It is a two-orders-of-magnitude expansion of the authorization payload.
Ask what that does to transaction size, to the fee market, to throughput. The source provides nothing. No signature benchmarks. No TPS impact. No fee delta. No wallet upgrade path. That silence is the story. A roadmap that does not quantify signature bloat is a direction, not a delivery schedule.
I have watched this movie before. In 2018, while finishing my MS in Financial Engineering, I spent three months auditing the 0x Protocol v2 smart contracts and submitted seven pull requests for edge-case vulnerabilities. What that exercise taught me is that key management is where systems die. Not in the happy path — in the rotation, the recovery, the multisig threshold change, the account that has already leaked its public key to the mempool. Anyone promising a clean signature migration has not stress-tested the edge cases.
The XRPL path has a real strength: the Amendment process. Protocol changes require validator supermajority and a defined activation window. That is a governed upgrade rail. It is also a bottleneck. No PQC signature scheme is live until validators vote it in, and no honest timeline exists until an Amendment is filed. Which brings the 2028 date under scrutiny. A target year without a filed Amendment is a press release, not a protocol change.
Now the exposure window, which almost nobody prices correctly. On both XRPL and Ethereum, a public key is revealed on-chain the moment an account signs its first outgoing transaction. The quantum clock does not start at adoption. It starts at first spend. An account with a decade of signing history has a decade of exposed public key material. Rotation preserves the address. It does not un-expose the key. The 'no address change' advantage is real for user experience. It is not a cryptographic reset button.
And the economic channel? Nearly empty. The source carries no supply data, no unlock schedule, no burn mechanics, no protocol revenue. XRP is a native ledger asset. ETH is a platform asset. A signature upgrade changes neither the issuance curve nor the fee-burn logic in any way I can model. There is no cash flow here to discount. There is a security narrative, and security narratives trade on sentiment, not on discounted future fees.
Contrarian: the race is mis-framed, and that mis-framing is the trade
The consensus reading is that XRPL outpaces Ethereum by a year. That framing is wrong in a way that is useful.
Ethereum's 2029 is not a slower team. It is a harder problem. Migrating the base-layer EOA primitive touches every address, every tool, every custody integration. That is why Ethereum would more likely route the transition through account abstraction and EIP-7702 — shifting the signature authority into contract logic where it can be swapped without abandoning the identifier. If that path works, Ethereum preserves address continuity too, and the 'gap' collapses to a footnote about implementation philosophy.
Meanwhile, my 2023 work simulating the digital euro's effect on Spanish bank deposits taught me how regulators model these transitions: they do not care about a chain's elegance, they care about holdings limits, redemption pressure, and settlement certainty. If institutional custody desks begin listing post-quantum readiness as a procurement requirement — and they will, eventually — the winner is not the chain with the earliest date. It is the chain with the audited, benchmarked, validator-ratified scheme. A calendar does not clear a custody risk review.
There is also the marketing asymmetry. The title 'outpaces Ethereum' is competitive positioning, and positioning spreads faster than engineering. The Ethereum date can be lifted out of context and simplified. The XRPL date can be amplified by its holders. Neither move prices against fundamentals. Liquidity does not lie — but it does wait for confirmations that do not yet exist.
Takeaway: what to actually watch
Ignore the years. Watch three things. First, an Amendment number on the XRPL network naming a specific post-quantum scheme. Second, published signature-size and fee-impact benchmarks from XRPL developers. Third, any statement from a major custodian that post-quantum support is a listing condition. Until one of those lands, this is a narrative with a calendar attached and no delivery receipt.
The deeper question is not who migrates first. It is whether any chain can migrate before a cryptographically relevant quantum computer exists — and whether the exposed keys of the last decade give the industry enough runway to matter. A roadmap is a liability until it clears a vote. Code audits, not calendars.
