iTechGuides is reader-supported. When you buy through links on our site, we may earn an affiliate commission. As an Amazon Associate I earn from qualifying purchases. Learn more
There is no activated Bitcoin post-quantum migration or published deadline today. BIP-361 is a draft informational soft-fork proposal, and BIP-360 is also a proposal. Their dates, block heights, wallet requirements, and treatment of vulnerable coins are not Bitcoin consensus rules.
The practical risk concerns Bitcoin’s current ECDSA and Schnorr spending assumptions. Coins whose public keys have already appeared on-chain have a different exposure profile from coins whose keys remain hidden behind a hash. A future migration would most likely require sending coins to a new post-quantum output type and paying normal network fees, but no fixed charge or production fee schedule has been established.
What Bitcoin’s post-quantum problem actually is
Bitcoin currently authorizes spending with ECDSA and Schnorr signatures. These systems depend on mathematical assumptions that a sufficiently capable quantum computer could attack more efficiently than a conventional computer. The concern described by the current proposals is not that every coin automatically becomes spendable by a quantum machine; it is that an attacker could derive or exploit signing keys quickly enough to authorize an unauthorized transaction.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
Why a revealed public key matters
Bitcoin normally protects a public key behind a hash until an output is spent. Once a transaction reveals the public key, the attacker no longer has to reverse that hash before attempting a public-key attack. BIP-361 focuses on this distinction and says that, as of March 1, 2026, more than 34% of all bitcoin had revealed a public key on-chain. That figure is an estimate stated by the BIP-361 authors, not an independently audited measurement.
#1 Best Overall
- BITCOIN EXCLUSIVE, PHONE VERIFICATION: Bitkey is designed from the ground up exclusively for bitcoin — a dedicated hardware wallet for secure bitcoin storage. Approve transactions with a tap using your phone and NFC. No device screen is required.
- SELF-CUSTODY, NO EXCHANGE OR CUSTODIAN REQUIRED: You hold two of the three keys in the Bitkey system – one on your phone and one on your Bitkey device. The third is stored on Bitkey’s server and cannot move your bitcoin on its own.
- NO SEED PHRASE: Set up and use Bitkey without creating or storing a seed phrase.
- 2-of-3 MULTISIG: Three keys are stored separately across your phone, Bitkey device, and Bitkey’s server. Any two keys are required to move your bitcoin.
- BUILT-IN RECOVERY: Encrypted backup and recovery tools can help you regain access if you lose your phone or Bitkey device. You can also designate a Recovery Contact.
Exposure is therefore output-specific. A coin in a legacy output with a revealed public key is not in the same situation as a coin whose public key remains hidden. The exact boundary between safe and unsafe spending will depend on the final protocol design, the attacker’s capabilities, and how quickly transactions can be confirmed.
What is not established
No cited source establishes an activated Bitcoin post-quantum upgrade, a working consumer quantum-safe wallet, or an imminent theft event. The proposals describe how Bitcoin might respond; they do not prove that a quantum attacker can currently steal coins.
When will Bitcoin require migration?
There is no live deadline
BIP-361 is labeled a Draft informational soft-fork proposal. BIP-360 is a proposal for a pay-to-merkle-root (P2MR) output design. Neither has been activated by Bitcoin consensus. A date mentioned in either document is contingent on adoption, implementation, signaling or activation rules, and the exact parameters ultimately chosen.
BIP-361’s illustrative phases
| Phase | What the proposal describes | Illustrative timing | Current status |
|---|---|---|---|
| Phase A | Permitted sends move from legacy ECDSA/Schnorr scripts to a post-quantum output type. | A horizon of 160,000 blocks, approximately three years, after activation. | Proposal parameter only; not a current deadline. |
| Phase B | Nodes tighten or stop accepting ECDSA/Schnorr verification at a predetermined height. | Described as about two years after Phase A activation. | Proposal parameter only; not scheduled on the live network. |
The BIP-361 abstract says: “This proposal follows the implementation of any post-quantum (PQ) output type and introduces a pre-announced sunset of legacy ECDSA/Schnorr signatures.” That wording describes a possible sequence, not a rule that wallets must follow now.
Rank #2
- Unparalleled Security: Protect your assets NDA-free EAL 6+ Secure Element, offering robust defense and complete transparency
- Simple & Secure Interface: Manage your digital assets easily with a clear OLED screen for secure on-device confirmations
- Supports 1000s of Coins & Tokens: Securely handle thousands of assets, including Bitcoin, Ethereum, and more, all in one wallet
- Effortless Asset Management: Monitor and transact seamlessly with Trezor Suite, our intuitive desktop and mobile app
- Enhanced Backup Solution: Rest assured with Multi-share Backup, eliminating single points of failure for secure cold wallet recovery
Why you should not move solely because of a date graphic
A wallet, exchange, social-media post, or service can display a countdown without having authority to change Bitcoin consensus. Until node software, wallet software, exchanges, miners and users support an activated rule, a claimed block height is not a migration deadline. A premature move can also create unnecessary fees, operational mistakes, or funds sent to an unsupported script.
How a real migration would probably work
The exact procedure cannot be finalized before Bitcoin adopts an output format and wallet standards. The likely mechanics are nevertheless straightforward: spend existing unspent transaction outputs (UTXOs) into a new output type that uses post-quantum authorization.
Before activation: prepare, do not improvise
- Record which wallets control your coins, including watch-only wallets and multisignature arrangements.
- Confirm that every seed, signing device, passphrase and recovery document is available and tested without exposing it online.
- Separate operational decisions from speculation. Do not import a seed into an unfamiliar “quantum-safe” application solely because it uses that label.
- Track the Bitcoin Core release notes, the final BIP text, and documentation from the wallet and exchange providers you actually use.
- Plan a small test transaction only after the destination output type, wallet support and recovery procedure are publicly documented.
After an activated rule and supported wallets
- Upgrade to wallet software that explicitly supports the activated post-quantum output and displays the resulting address or script type.
- Create a fresh destination under a documented recovery process. Keep the new backup separate from the old backup until the transaction is confirmed and tested.
- Choose UTXOs deliberately. Consolidating many inputs can increase transaction weight, while splitting transfers can create additional fees.
- Set a fee according to the prevailing fee market and the transaction’s estimated virtual size. Do not rely on a percentage-of-balance estimate.
- Broadcast through a compatible node, wallet or exchange, then verify confirmation and the output type in a block explorer or your own node.
- Update inheritance, multisignature, accounting and exchange records. A migration is incomplete if a co-signer, beneficiary or withdrawal system still expects the old format.
Those steps are a planning model, not a currently executable Bitcoin procedure. The final migration may use different scripts, wallet descriptors, relay rules or deadlines.
Windows Errors? Fix Them Before They Spread
Repair common Windows errors and clear accumulated junk for a smoother, more stable PC - no reinstall needed.Free scan · no reinstallCrashes, No Sound, or Screen Glitches?
Random freezes, missing sound and display glitches usually trace back to one bad driver. Find and replace yours safely.Free scan · under a minuteWill migrating Bitcoin require a fee?
If migration uses ordinary Bitcoin transactions, the cost would normally be the network fee for those transactions. The fee would depend on transaction size or weight, the number of inputs and outputs, and congestion when you broadcast. There is no fixed migration fee, published fee multiplier, or guaranteed subsidy in the cited proposals.
Rank #3
- Unparalleled Security: Protect your assets with EAL 6+ Secure Element, offering robust defense and complete transparency
- Simple & Secure Interface: Manage your digital assets easily with a clear OLED screen for secure on-device confirmations
- Supports 1000s of Coins & Tokens: Securely handle thousands of assets, including Bitcoin, Ethereum, and more, all in one wallet
- Effortless Asset Management: Monitor and transact seamlessly with Trezor Suite, our intuitive desktop and mobile app
- Enhanced Backup Solution: Multi-share Backup eliminates single points of failure for secure cold wallet recovery
What can make the transaction expensive
| Cost driver | Why it matters |
|---|---|
| Input count | Each UTXO adds data. Moving many small UTXOs can cost more than moving one large UTXO. |
| Output and script design | A post-quantum signature or script may be larger, affecting transaction weight. BIP-360 and BIP-361 do not provide a final production fee schedule. |
| Network congestion | When blocks are crowded, users generally need a higher fee rate for timely confirmation. |
| Replacement or acceleration | An underpriced transaction may require fee replacement or another supported recovery method, creating additional operational risk. |
Do not claim that migration will cost a particular percentage of holdings. That number cannot be calculated until the output format, signature sizes, wallet behavior and fee market are known. A prudent holder should keep a fee reserve and migrate in batches only when the software can estimate the actual transaction.
Are old coins already exposed?
“Old” is not a sufficient risk category. The important questions are which output type holds the coin and whether its public key has been revealed.
| Situation | What it means |
|---|---|
| Public key revealed on-chain | The coin has the exposure emphasized by BIP-361 because an attacker can target the public-key/signature assumptions directly. |
| Public key still hidden behind a hash | The attacker faces an additional hash-related step. This may provide a different safety margin, but it is not a permanent guarantee against a future protocol or cryptographic breakthrough. |
| Coin already spent | Its former exposure does not matter; assess the current unspent output that received the value. |
| Multisignature or unusual script | Risk depends on which keys and signatures the script reveals. Do not assume a multisignature arrangement is automatically post-quantum. |
Repeatedly moving a coin can reveal additional keys and create fees, so “move everything now” is not automatically safer. Wait for an adopted design unless you have a separate, well-understood security reason to transact.
What happens to lost Bitcoin?
Lost coins create the hardest policy question because the owner cannot sign a migration transaction. BIP-361 calls this a redistribution dilemma and describes competing approaches rather than a settled rule.
Rank #4
- Dual-chip architecture for maximum protection: The next-gen, fully auditable TROPIC01 chip works alongside a certified EAL6+ Secure Element—completely NDA-free—to deliver radically transparent, industry-leading defense against physical attacks.
- Quantum-ready security: Get protection against future threats with the first-ever hardware wallet designed with quantum-ready architecture.
- See every detail with confidence: Our largest high-resolution color touchscreen makes it easy to navigate your assets, review transactions and manage your coins with clarity.
- Wireless freedom with encrypted Bluetooth control: Manage, buy, swap and stake securely using Trezor Suite on desktop or mobile. Qi2-compatible wireless charging keeps your Trezor powered up. No cables required—security meets convenience.
- Works seamlessly with Android, iOS and desktop: Connect wirelessly or via USB-C to your phone or computer. Manage your crypto anywhere with our companion Trezor Suite app.
| Policy family described by BIP-361 | Potential result | What is known |
|---|---|---|
| Permit anyone to take vulnerable coins | A quantum attacker, or another party, could claim coins whose keys are considered vulnerable. | Listed as a possible policy, not adopted. |
| Permit throttled recovery | Recovery might be rate-limited or constrained to reduce theft, but could cause fee and replacement conflicts. | Listed as a possible policy, with unresolved engineering and governance issues. |
| Permit no one to take them | Vulnerable coins could remain permanently unspendable rather than be redistributed. | Listed as a possible policy, not adopted. |
A new wallet cannot recreate a missing seed
If you have lost the seed, private key or required signing credentials, installing a future post-quantum wallet will not by itself make the coins spendable. Recovery would depend on the final consensus rules and whatever recovery credentials those rules require. Anyone promising automatic recovery of a lost seed is making a claim that is not established by these proposals.
Where OP_VAULT fits
BIP-345’s OP_VAULT describes delayed spending and a prespecified recovery path. It is relevant background because a vault can mitigate the worst outcome of key compromise, which the proposal calls “coin loss.” It is not a post-quantum migration activation and cannot restore a seed that has already been destroyed or forgotten. A vault helps only when its recovery path was configured in advance and the required credentials still exist.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.Can you buy a post-quantum hardware wallet?
No cited source identifies an adopted, Bitcoin-compatible post-quantum hardware wallet. A hardware wallet can protect private keys from malware and make signing more deliberate, while a metal backup can improve physical durability. Neither changes ECDSA or Schnorr into a post-quantum signature scheme by itself.
Free tools Windows power users keep installed
One-click scans. No signup required.
Evaluate any future device against the actual Bitcoin output type it creates, the wallet descriptor it uses, firmware reproducibility, independent audits, multisignature compatibility, backup and recovery instructions, exchange interoperability, and the activation status of the underlying consensus rule. A product that merely advertises “quantum resistance” without naming the Bitcoin script and signing algorithm is not enough evidence.
Best Value
- Effortlessly build your crypto portfolio via the all in one Ledger Wallet app: buy, sell, send, receive, swap, stake and more across popular blockchains. 15,000+ coins & tokens in a single dashboard. Keep a close eye on the market. Compare service providers. Track performance. Get timely alerts. Build your portfolio with confidence.
- Enjoy Bluetooth connectivity, iOS access, and hours of battery use with this mobile-first, secure backup signer. Freedom you can depend on.
- Genuine Check: confirm your signer is authentic during setup with the Ledger Wallet app.
- Protect your signer: keep it in mint condition at all times with a bespoke Pod or Case to avoid scratches and everyday wear and tear.
What should Bitcoin holders do now?
- Protect existing backups. Keep seeds and passphrases offline, maintain more than one physically secure copy, and test restoration with a watch-only or spare environment.
- Inventory exposed outputs. Identify addresses and UTXOs whose public keys have appeared on-chain, but avoid unnecessary spending just to change their appearance.
- Use supported software only. Treat an unrecognized address prefix, script type or wallet import request as a stop signal until independently documented.
- Monitor consensus changes. Look for an activated BIP, released node and wallet support, and clear exchange deposit and withdrawal compatibility—not just a proposal number.
- Budget for ordinary fees. Keep liquidity for network fees, especially if you control many small UTXOs or expect to migrate during congestion.
- Plan shared custody. Coordinate co-signers, trustees, beneficiaries and business accounting before moving a multisignature or institutional balance.
- Ignore recovery guarantees. A future upgrade cannot compensate for a missing seed unless the adopted rules explicitly provide a recovery mechanism that you can satisfy.
How to compare future migration options
When real alternatives appear, compare them on the same evidence rather than choosing by marketing language.
| Comparison axis | Questions to ask |
|---|---|
| Activation and support | Is the rule activated on Bitcoin mainnet? Which node, wallet and exchange versions support it? |
| Signature and address design | Which post-quantum algorithm and output type are used? How are descriptors, backups and multisignature policies represented? |
| Transaction weight and fees | How large are signatures and scripts in practice, and how does the wallet estimate fees under congestion? |
| Lost-coin treatment | Are vulnerable unspendable outputs frozen, recoverable under constraints, or open to competing claims? |
| Interoperability | Can major exchanges, payment processors, hardware devices and self-hosted nodes send and receive the output? |
| Security evidence | Are the implementation, cryptography and firmware independently audited, and are vulnerability disclosures public? |
| Migration window | What exact activation event starts the clock, and what happens to transactions sent after the window closes? |
What NIST standards do—and do not—tell you
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, wallet, hardware device or migration schedule. Bitcoin still needs a consensus-approved output design, implementation and operational rollout before those ideas become a user action.
Bottom line for holders
Do not rush Bitcoin into an unverified wallet because of a claimed deadline. As of the available evidence, BIP-361 and BIP-360 remain proposals, migration timing is contingent, fees would be ordinary variable network fees, and the treatment of lost coins is unresolved. Preserve your keys, understand which outputs reveal public keys, and wait for an activated rule with audited wallet and exchange support before performing a large migration.
Quick wins for a faster PC:
Scan for outdated or missing drivers - takes under a minuteDriver Scan →Repair Windows errors before they cause bigger problemsFix Now →Fix the driver behind crashes, sound loss and screen glitchesFind Drivers →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.
