A post-quantum signature does not migrate a digital-asset ecosystem by itself. In an October 13 analysis, Coinbase set out considerations for Bitcoin’s post-quantum readiness, including block-space constraints, independent node validation, institutional custody, ordinary wallets, multiparty computation, and funds that cannot or will not move.
Coinbase presents the article as input to an open discussion, not a final position or set of instructions. No Bitcoin-wide algorithm, activation plan, or migration deadline is established. That uncertainty is precisely why organizations holding or servicing digital assets need an inventory of dependencies before a protocol decision arrives.
The exposed asset is more than a coin balance
Quantum exposure depends partly on whether a public key is visible and whether the corresponding asset can be moved. Coinbase distinguishes old output types with permanently exposed public keys, reused keys, dormant but controlled funds, and holdings whose seeds or keys are lost.
For an institutional inventory, a useful record should connect:
- the network, address or script type, wallet, and accountable owner;
- whether the public key has been exposed on-chain;
- the signing algorithm, key origin, and custody boundary;
- hardware wallet, HSM, MPC, or other signing dependencies;
- backup, seed, recovery, and disaster-restoration procedures;
- transaction policy, approvals, and relying applications;
- mobility constraints, legal holds, and operational deadlines; and
- evidence date, confidence, and unresolved ownership questions.
This is not a recommendation to centralize secret key material. The system of record should track necessary metadata and evidence without collecting private keys or seeds.
Custody workflows constrain signature selection
Coinbase highlights compatibility with multiparty signing as an important institutional consideration. A signature scheme that is mathematically suitable and compact enough for the protocol may still be impractical if it cannot support the approval, segregation-of-duty, recovery, and signing workflows used by custodians.
Teams should therefore inventory the complete signing path: key generation, participant roles, quorum policy, hardware and software boundaries, transaction review, latency, audit trail, backup, participant replacement, and emergency recovery. Each dependency needs a target state and test plan.
A prototype signature verification does not prove that high-value custody can migrate safely. Operational controls must survive the algorithm change.
Dormant and inaccessible assets are governance questions
Adding a new output type can protect newly created funds and funds that actively migrate. It cannot make an unavailable owner appear. Proposals for rescue paths, deadlines, restrictions, or treatment of abandoned holdings affect property expectations, consensus, incentives, and security.
Organizations should separate technical capability from governance authority. A registry should record the proposal, sponsor, maturity, affected population, activation assumptions, challenge process, approval body, and unresolved legal or fiduciary questions. Research and debate must not be reported as an approved network change.
Internally, custodians can identify which controlled holdings are movable, which require customer action, which are subject to legal restrictions, and which recovery evidence has actually been tested.
Resource limits shape the migration window
Bitcoin’s block space and independent verification requirements make key and signature sizes operational concerns. Wallets and hardware devices add memory, bandwidth, power, and firmware constraints. Large migrations may also concentrate transactions and support demand into a limited period.
Pilots should measure transaction size, signing and verification performance, hardware compatibility, fee sensitivity, batching options, recovery, and failure behavior. Results should identify the exact algorithm, implementation, hardware, network conditions, and test population.
Migration planning should also model the rate at which assets and customers could realistically move, rather than assuming a deadline instantly changes every wallet.
What organizations should do next
First, inventory digital-asset cryptography by role and custody boundary. Include exposed public keys, wallet types, signing systems, backups, and ownership status.
Second, identify dependencies that an algorithm choice cannot solve: MPC protocols, hardware support, customer action, legal restrictions, block capacity, and recovery.
Third, test bounded signing and migration workflows without presenting them as activated network capability. Preserve performance, failure, and control evidence.
Fourth, separate protocol proposals, organizational policy, and deployed state. Assign reevaluation triggers as community work advances.
Finally, plan communications and support for a multi-year transition. A technically valid path can still fail if owners cannot understand or execute it safely.
How Vista Platform helps
Vista Platform is a self-hosted cryptographic system of record. Its operating loop—discovery, canonical inventory, evaluation, action, and proof—helps teams connect cryptographic assets with custody systems, owners, dependencies, decisions, remediation, exceptions, and evidence.
Vista Platform Core is free of charge and includes discovery, inventory, compliance and PQC assessment, and CBOM generation without asset, sensor, seat, or time caps. Vista tracks and governs post-quantum migration; it does not generate PQC keys or perform every migration. Selected-asset Active Scan is targeted, not indiscriminate network scanning. Vista is not a vulnerability scanner, and incomplete discovery is not proof of absence.
Learn more about Vista’s post-quantum migration and cryptographic inventory approach.
Where uncertainty remains
Coinbase’s article is one institutional perspective in an open ecosystem discussion. It does not establish consensus, an activation mechanism, or a selected signature scheme. Estimates of future quantum capability and exposed holdings also carry uncertainty. The durable operational point is that cryptographic migration must preserve custody, recovery, governance, and user safety—not merely pass a signature test.
Source
- Working Together on Bitcoin’s Post-Quantum Readiness, Coinbase, October 13, 2026.