How to Assess Post-Quantum Readiness for a Blockchain

Discussions about post-quantum security in blockchain often begin with cryptographic algorithms. Which signature scheme should replace an existing one? How large are the public keys and signatures? How expensive is verification? Can the scheme fit within current transaction and block constraints?

Those questions are important, but choosing a post-quantum primitive is only one part of preparing a blockchain ecosystem for quantum-era threats.

A blockchain can support a post-quantum signature scheme at the protocol level while still depending on vulnerable cryptography across wallets, custody systems, hardware, account recovery, bridges, exchanges, and other infrastructure.

A useful assessment of post-quantum readiness therefore needs to cover the full path between cryptographic primitives and deployed systems.

1. Cryptography

The first layer starts with a cryptographic inventory: identifying the cryptography an ecosystem actually depends on, where it is used, and which components are exposed to quantum risk.

For a blockchain, that inventory may include transaction and account signatures, validator or consensus keys, wallet key derivation, multisignature systems, bridges, custody infrastructure, authentication mechanisms, cryptographic libraries, and other systems that rely on public-key cryptography.

From there, teams can assess which dependencies need to migrate and evaluate potential replacements. For digital signatures, this may involve schemes such as ML-DSA, SLH-DSA, and other constructions, with tradeoffs around security assumptions, key and signature sizes, implementation complexity, verification cost, and suitability for the protocol.

These tradeoffs are particularly important for blockchains because cryptographic data is replicated and verified across many participants. A signature that is acceptable in another environment may create meaningful bandwidth, storage, or execution costs when used at blockchain scale.

2. Protocol

Once the cryptographic dependencies are understood, the next question is what the protocol needs to change to support them.

Post-quantum signatures may require larger transactions, new address or account types, different verification logic, additional opcodes or precompiles, and changes to serialization or fee calculation.

Existing assets may also be controlled by keys whose public information has already been exposed on-chain, so migration mechanisms have to account for those funds and how their exposure changes as quantum capabilities develop.

Protocol readiness also means understanding how a migration interacts with existing consensus rules, transaction validation, network resource limits, and backwards compatibility. Supporting a post-quantum algorithm is useful only if the surrounding protocol can deploy and operate it safely at scale.

3. Wallets, Key Management, and Authorization

Supporting post-quantum cryptography also requires looking at how keys are generated, stored, recovered, and ultimately used to authorize activity.

Wallets may rely on more than a single transaction-signing key. Multisignature policies, smart contract wallets, recovery keys, session keys, delegated permissions, hardware-backed credentials, and administrative keys can introduce additional cryptographic dependencies.

A quantum-safe assessment therefore needs to trace the full authorization path. Upgrading the primary transaction signature while leaving a recovery, administrative, or delegated key dependent on quantum-vulnerable cryptography can leave an alternative path to the same assets or permissions exposed.

New schemes may also affect key generation, backups, signing interfaces, address derivation, hardware wallet support, secure-element storage, air-gapped signing, and transaction transmission.

4. Infrastructure

Blockchain ecosystems extend far beyond nodes and wallets.

Exchanges, custodians, bridges, payment processors, indexers, RPC providers, institutional signing systems, developer SDKs, block explorers, and hardware manufacturers may all encode assumptions about existing keys, signatures, addresses, or transaction formats.

Institutional infrastructure can be particularly important because migration timelines may depend on external certification, hardware replacement cycles, custody policies, and operational approval processes.

Mapping these dependencies early helps identify where technically supported migrations could encounter deployment bottlenecks.

5. Migration Strategy

A post-quantum upgrade also needs a migration strategy.

An ecosystem may need to support classical and post-quantum authorization simultaneously for some period. Hybrid approaches can reduce certain transition risks, but they introduce their own costs and implementation requirements.

Important questions include when users should migrate, how long legacy credentials remain valid, whether inactive funds require special treatment, how exchanges and custodians coordinate upgrades, and what happens when assets remain associated with vulnerable keys.

Migration design also has to consider incentives. Users rarely move assets simply because a safer cryptographic option exists. Wallet support, fees, deadlines, defaults, and ecosystem communication can strongly influence adoption.

6. Ecosystem Readiness

The final layer looks at readiness across the ecosystem as a whole.

A blockchain ecosystem can contain thousands of independent applications, service providers, infrastructure operators, and users, and they will not all migrate at the same time.

Readiness therefore needs measurable indicators. An ecosystem might track the percentage of assets protected by quantum-resistant authorization, wallet support, custody support, infrastructure compatibility, remaining vulnerable value, and dependencies that have not yet completed migration.

These measurements can provide a more realistic picture of exposure than protocol support alone.

A Practical Readiness Model

Post-quantum readiness can be evaluated across six connected layers:

Weakness at any layer can leave part of the ecosystem exposed or make migration significantly harder to execute.

For blockchain ecosystems beginning this work today, a useful starting point is a quantum-safe assessment built around a cryptographic inventory. Teams need to know what cryptography they currently rely on, where it appears across the protocol and surrounding infrastructure, which dependencies are vulnerable to quantum attacks, and which systems would need to change.

From there, dependency mapping can connect those findings to wallets, custody systems, exchanges, bridges, hardware, developer infrastructure, and other parts of the ecosystem. This makes it possible to identify migration blockers, compare technical proposals, prioritize engineering work, estimate operational impact, and define measurable readiness milestones.

The result should be a concrete view of current quantum exposure and a migration path that extends from cryptographic primitives all the way to deployed infrastructure and users.

Valens Research works with blockchain ecosystems, startups, and infrastructure teams on post-quantum readiness, cryptographic dependency mapping, and independent technical research. For research partnerships or technical assessments, get in touch at hello@valens.me.