Short answer: Bitcoin has not activated a post-quantum migration, and no consensus deadline exists today. BIP-361 and BIP-360 are proposals, not live rules. If a future upgrade requires moving coins, you would likely send them to a new output type and pay ordinary, variable Bitcoin network fees. How vulnerable or recoverable lost coins would be is still unresolved, and no currently verified consumer hardware wallet replaces Bitcoin’s ECDSA or Schnorr signatures with post-quantum cryptography.
The practical issue is not that every bitcoin is already exposed. Quantum attacks described by the proposals target the public-key and signature assumptions used when coins are spent. Coins whose public keys have appeared on-chain have a different risk profile from coins still protected by hashed public keys. The final migration boundary, timetable, wallet support and lost-coin policy will depend on Bitcoin consensus decisions that have not yet occurred.
As an Amazon Associate I earn from qualifying purchases.
The current answers to the four questions most holders ask
| Question | What is established now | What remains undecided |
|---|---|---|
| When must I move my BTC? | There is no activated migration and no current deadline. | Any dates in BIP-361 begin only after activation and could change before adoption. |
| Will migration have a fee? | A transaction to a new output would normally pay the prevailing network fee for its size. | No fixed fee, percentage, multiplier or guaranteed fee schedule has been published. |
| Can quantum computers steal lost bitcoin? | The policy for vulnerable, inaccessible coins is unresolved. | Bitcoin could freeze them, permit constrained recovery, or adopt another rule. |
| Is there a post-quantum hardware wallet? | No product is established in the cited material as an adopted Bitcoin-compatible post-quantum wallet. | Wallet, exchange and custody support would have to follow an activated protocol. |
These answers distinguish a protocol proposal from a deployed feature. A wallet advertisement, a new cryptography standard or a hardware backup device cannot by itself change Bitcoin’s consensus rules.
Free tools Windows power users keep installed
One-click scans. No signup required.
What quantum computing threatens in Bitcoin
ECDSA and Schnorr are the assumptions under discussion
Current Bitcoin spending relies on digital-signature systems based on ECDSA and Schnorr. A sufficiently capable quantum computer could undermine the public-key and signature assumptions that let the network verify that a spender controls a private key. BIP-361 describes its objective as following implementation of a post-quantum output type and then introducing a pre-announced sunset of legacy ECDSA/Schnorr signatures.
#1 Best Overall
BIP-360 proposes P2MR, a pay-to-merkle-root design intended to reduce quantum exposure. Its authors also note that more sophisticated attacks, including recovering a public key while a transaction is waiting in the mempool, may require post-quantum signatures rather than only a change in address construction. The proposals therefore address both how coins are locked and how spending signatures are verified.
Revealed public keys are the important distinction
A coin is not described as equally exposed at every stage. Some output types keep a public key behind a hash until the owner spends. Other historical or already-spent patterns have put a public key on-chain. BIP-361 states that, as of March 1, 2026, over 34% of all bitcoin had revealed a public key on-chain. That is a figure reported by the BIP-361 authors in their 2026 proposal, not an independently audited measurement established here.
For a holder, the useful distinction is whether the public key protecting a particular unspent output has been revealed, not whether the owner uses a hardware wallet or a particular app. A quantum-capable attacker would target the exposed public-key and signature assumptions. The exact point at which an output becomes unsafe, and which outputs must move first, depends on the final output design and consensus rules.
PC Slower Than It Used to Be?
A free scan shows the junk files, broken settings and background clutter dragging Windows down - then fixes them in one click.Free scan · Windows 10 & 11Outdated Drivers Are Slowing You Down
One free scan finds every outdated or missing driver and matches the right update for your exact hardware.Free scan · exact hardware matchWhen would Bitcoin migration happen?
There is no live activation date
BIP-361 is labeled a Draft informational soft-fork proposal, and BIP-360 is also a proposal. Neither establishes an activated Bitcoin rule. No cited source supplies a block height at which all users must move, a date when legacy coins expire, or a wallet-support deadline that is currently enforceable.
Rank #2
- Ideal for Gifting
- Ideal for a bookworm
- Compact for travelling
Any website presenting a countdown as the Bitcoin migration deadline is making a conditional claim unless the Bitcoin network has actually adopted and activated the relevant consensus changes. Activation would require the normal development, review, implementation, coordination and consensus process. Until then, moving coins solely because of an alleged fixed deadline is not supported by these proposals.
How BIP-361’s illustrative phases work
BIP-361 gives an example timetable that starts only after activation:
- Phase A: permitted sends would move from legacy scripts to post-quantum scripts. The proposal gives a horizon of 160,000 blocks, approximately three years, after activation.
- Phase B: nodes would tighten ECDSA/Schnorr verification at a predetermined height described as two years after Phase A activation.
Those intervals are proposal parameters, not a promise that Bitcoin will follow them. A final implementation could alter the block counts, definitions, exemptions, activation mechanism or treatment of outputs. The phrase “three years” cannot be converted into a calendar date until an activation event and starting height exist.
Quick wins for a faster PC:
Scan for outdated or missing drivers - takes under a minuteDriver Scan →Clear out junk files and repair common Windows errorsFree Scan →What a future migration transaction would involve
If Bitcoin adopts a new post-quantum output type, migration would normally mean spending an existing UTXO and creating a replacement output controlled by a post-quantum script. The exact wallet screens and transaction format do not yet exist as a verified consumer workflow, but the operational sequence would likely look like this:
- Confirm the rule and support. Check that the network has activated a specified output type and that your wallet, exchange or custodian supports it. A label such as “quantum-resistant” is not proof of Bitcoin consensus compatibility.
- Inventory your UTXOs. Determine which addresses and outputs you control, which public keys have been revealed, and whether any outputs are held by an exchange or other custodian. Prioritization could depend on the final rules, not simply on the age or value of a coin.
- Back up the recovery material. Preserve the seed and any required passphrase or signing policy before changing addresses. A post-quantum output does not remove the need for secure key management.
- Create the new output. Use a supported wallet to generate the post-quantum destination and send the selected UTXOs to it. Keep the transaction record and verify the destination on a trusted device.
- Wait for confirmation. A migration transaction is still a Bitcoin transaction. It may remain unconfirmed during congestion and should be checked against the network’s finality and replacement rules.
- Repeat for remaining outputs. Consolidation, dust limits, custodial withdrawal policies and any phase-specific restrictions could affect how many transactions are needed.
This is a planning model, not a currently available migration procedure. Do not enter a seed phrase into an unverified “migration” website or sign a transaction solely because a message claims that an emergency quantum deadline has arrived.
How much would migration cost?
The fee would be a network-market cost
The cited proposals do not publish a fixed migration fee, a fee multiplier or a guaranteed percentage increase. If you move a UTXO to a new output, the transaction would normally pay Bitcoin’s prevailing fee market for its transaction size and chosen confirmation target. The amount could therefore differ by block, wallet, regionally available exchange service and urgency.
| Cost driver | Why it matters | What is known today |
|---|---|---|
| Transaction weight | More inputs, outputs or larger signatures consume more block space. | Post-quantum signatures or scripts could be larger, but final production sizes are not specified by the cited BIPs. |
| Network congestion | Busy periods generally require a higher fee rate for the same confirmation target. | No migration-specific fee market exists before activation. |
| Number of UTXOs | Moving many separate outputs can require multiple transactions or a larger transaction. | Your wallet’s coin selection and the final protocol rules would determine the practical count. |
| Custodian charges | An exchange or service may add a withdrawal or processing charge. | No universal custodial fee is established by BIP-360 or BIP-361. |
It is therefore not accurate to say migration will cost a particular percentage of your holdings. The sensible financial preparation is to keep a reserve for ordinary network fees and to avoid waiting until a possible deadline creates a rush. That is general fee planning, not a prediction of a future price.
What happens to lost or abandoned coins?
The proposals identify a redistribution dilemma
Lost coins create a conflict if legacy outputs become vulnerable. If nobody can spend them, they may remain frozen forever. If the rules allow someone else to spend them, the change could transfer wealth from absent owners to whoever performs the recovery. BIP-361 describes three broad policy families:
Rank #4
- Unrestricted theft or recovery: anyone able to exploit a vulnerable output could claim it.
- Throttled recovery: recovery could be constrained by time or rate limits, but this may create fee competition and transaction-replacement conflicts.
- No recovery by others: vulnerable coins could be frozen so that no new party can take them.
BIP-361 lists these competing choices without declaring a final rule. A future consensus change could also use a different mechanism. Until Bitcoin adopts one, no one can honestly promise that every lost coin will be recoverable or that every vulnerable coin will be permanently protected.
A new wallet cannot recreate a lost seed
If you no longer possess the private key, seed, passphrase or other credentials required by the final spending policy, installing a future wallet will not restore access. A protocol upgrade can change which signatures the network accepts; it cannot mathematically reconstruct a missing secret. Recovery would depend on whatever credentials and special rules the activated design requires.
Why OP_VAULT is relevant but not a quantum migration
BIP-345 OP_VAULT is background for recovery design. It describes delayed spending and a pre-specified recovery path and says the mechanism can mitigate the worst-case outcome of key compromise, “coin loss.” It is not a post-quantum migration activation and does not restore a lost seed. Its relevance is conceptual: a recovery path must be established in advance and enforced by consensus or wallet policy, rather than improvised after a key has disappeared.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
Is there a post-quantum hardware wallet you can buy?
No cited product is established as an adopted, Bitcoin-compatible post-quantum wallet. A hardware wallet can isolate keys, display transaction details and reduce some operational risks, but hardware protection does not replace ECDSA or Schnorr with post-quantum signatures. A metal seed backup can improve physical durability, yet it also remains a backup of the existing key material rather than a protocol migration.
Best Value
- It can be a gift option
- Comes with secure packaging
- Helpful in various ways
When products eventually claim support, verify the exact Bitcoin output type, the network activation they rely on, whether signing is performed with an adopted post-quantum algorithm, how firmware is audited, and whether exchanges and recovery tools recognize the resulting addresses. “Quantum-safe” used for a backup device, password manager or general cryptography product is not the same as a live Bitcoin-compatible output.
What NIST standards do—and do not—establish
NIST says it has released three post-quantum cryptography standards that can be implemented now to secure electronic information. Those standards provide general cryptographic building blocks. They do not certify a Bitcoin address format, approve a wallet, set a Bitcoin activation height or define how existing UTXOs migrate. Bitcoin developers would still have to select algorithms, design scripts and signatures, specify transaction rules, and obtain network adoption.
What holders should do before any activation
- Keep current seed phrases, passphrases and multisignature records backed up and test that your documented recovery process works.
- Track formal Bitcoin Improvement Proposal status rather than social-media countdowns. Treat BIP-360 and BIP-361 as proposals unless the network has activated a specific rule.
- Record which funds are self-custodied and which are held by a custodian; custodial migration may require a separate withdrawal process.
- Avoid signing unsolicited transactions or entering seed words into sites claiming to perform an urgent quantum migration.
- Plan liquidity for ordinary network fees, but do not prepay a service for a migration that Bitcoin has not activated.
- After an activation announcement, compare options on activation status, signature and address design, transaction weight, fee impact, lost-coin treatment, wallet and exchange interoperability, audit history and the length of the migration window.
The most useful preparation is custody hygiene and source verification, not prematurely moving coins to an unrecognized address format.
Recommended Free Tools
How to judge future migration options
If multiple implementations become available, use the same questions for each one:
| Evaluation area | Questions to ask |
|---|---|
| Activation and support | Is the rule activated on the Bitcoin network, and do the wallet, exchange and hardware devices you use implement it? |
| Cryptography and address design | Which post-quantum signature and output type are actually used, and what legacy assumptions remain? |
| Transaction economics | How large are signatures and scripts, how much block space do they consume, and how are fees estimated? |
| Recovery policy | What happens to coins with exposed keys, abandoned outputs or missing credentials? |
| Interoperability | Can funds move between major wallet, exchange and custody systems without proprietary lock-in? |
| Security evidence | Are the implementation, firmware and cryptographic libraries independently audited, and are upgrade and rollback procedures documented? |
| Deadlines | Is the migration window a consensus rule with a block height, or merely a vendor recommendation? |
Until those answers are tied to an activated Bitcoin rule, comparisons are forecasts rather than established consumer choices.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
