Quantum risk in blockchains is moving from abstract debate into engineering programmes. Coinbase’s 23 July 2026 custody roadmap and Ethereum’s recently updated public security roadmap point to the same conclusion: standardised post-quantum signatures are necessary, but coordinated migration is the harder problem.
This is not a claim that digital assets can be stolen by a quantum computer today. No publicly known cryptographically relevant quantum computer exists. The news is that custody providers and protocol communities are beginning to design the key-management, account and governance machinery they would need before the threat becomes operational.
The main exposure is authentication
Quantum discussions about blockchains often blur several cryptographic functions. Mining, hash-linked history and digital signatures do not face the same risk.
A sufficiently capable quantum computer would principally threaten the public-key signatures that prove control of accounts and authorise transactions. Public keys that are already visible on-chain may create earlier exposure than keys that remain hidden behind an address construction. Proof-of-stake systems also depend on signatures for validator duties.
Hash functions are affected differently and are not simply “broken” by the same attack. The practical migration question is therefore not whether an entire blockchain disappears at once. It is how wallets, validators, custody systems, hardware and protocol rules move to new authentication schemes without creating a weaker transition period.
Coinbase is building a crypto-agileCrypto-agilityBeing able to swap one encryption algorithm for another without rebuilding your systems. It is what turns the next migration into a configuration change instead of a project. signing layer
Coinbase says its current CoreKMS uses multi-party computation so no single party reconstructs a customer private key. Its announced PQ-CoreKMS programme starts with an automated signing pipeline that combines secure enclaves, secret sharing and threshold cryptography. The stated goal is to support post-quantum signature algorithms with key material separated across different environments.
The company targets that first pipeline within the next year, followed by two to three years of research toward full multi-party computation for lattice-based and potentially other post-quantum signatures. These are vendor roadmap statements, not completed capabilities, but the architecture choice is instructive: abstract the signing service so a blockchain’s future algorithm decision does not require rebuilding the custody control plane from scratch.
Coinbase also describes a company-wide cryptographic inventory ranked by system criticality, exposure and migration complexity, plus defined quantum-computing milestones that would trigger actual migrations. In parallel, it plans recurring working sessions with Bitcoin developers and contributions to open protocol work.
Ethereum is separating four migration surfaces
Ethereum’s roadmap identifies four areas that need post-quantum work: validator consensus signatures, data-availability commitments, account signatures and zero-knowledge proof systems. Treating them separately is important because each has different performance, upgrade and coordination constraints.
The Ethereum Foundation formed a dedicated Post-Quantum Security team in January 2026. Its public roadmap reports weekly interoperability development networks involving more than ten client teams, work on hash-based validator signatures and a small virtual machine to aggregate larger signatures efficiently.
Account migration may benefit from native account abstraction. The proposed EIP-8141 would let individual accounts select their own signature verification logic, potentially allowing users to adopt a quantum-resistant method before a single network-wide switch. It is under consideration for a future upgrade, not an active mainnet guarantee. The roadmap describes approximately 2029 as a planning target for core post-quantum infrastructure and warns that schedules may shift.
Why decentralised migration is unusually difficult
- Users must move. A protocol can add a safe address type while dormant, lost or abandoned wallets remain on the older scheme.
- Signatures are larger. Post-quantum signatures can change transaction size, fee economics, storage and hardware-wallet constraints.
- Consensus requires coordination. Exchanges, custodians, wallets, validators, nodes and application developers cannot upgrade in isolation.
- The transition itself creates risk. New code paths, dual support, fallback rules and emergency migration mechanisms expand the attack surface before they reduce it.
- Old assets create governance questions. Communities must decide how to treat accounts that never migrate without silently changing ownership expectations.
What custody and security teams should take from the news
- Separate quantum risk by cryptographic function: transaction signatures, validator signatures, encryption, commitments and proofs.
- Build algorithm abstraction at the signing-service boundary while preserving hardware-backed policy, separation of duties and audit evidence.
- Maintain an inventory that includes wallets, hardware devices, key ceremonies, recovery flows, address exposure and supplier dependencies.
- Define observable migration triggers and decision owners before a market event forces action.
- Test the operational edge cases: inactive accounts, larger transactions, rollback, mixed-algorithm support and incident recovery.
The credible signal is not that a quantum break is imminent. It is that serious teams are treating post-quantum readiness as a multi-year infrastructure and coordination programme. That is the right scale of response for any system in which signatures directly control valuable or irreversible actions.