Bitcoin Quantum Attacks: Quantum Landmines Now (2026) ⚡
Learn Bitcoin quantum attacks and quantum landmines (2026): see how auctions could raise theft costs and what’s still unresolved for quantum-resistant Bitcoin.

Could Bitcoin Quantum Landmines Make Theft Too Expensive?
A sufficiently powerful quantum computer could, eventually, threaten some Bitcoin wallets by deriving a private key from its corresponding public key. Today, there's no publicly demonstrated machine that can do this. And the timing of that risk - often called "Q-Day" - is unknown. Still, the problem is hard to ignore: Bitcoin can't tell whether a valid signature came from the rightful owner or from an attacker who managed to get the same key.
Bitcoin developer Cory Fields has proposed a way to change the incentives. His "quantum landmines" would let prepared wallet owners claim an attacker's collateral if someone tries to move their vulnerable coins. Two auction-style designs address a tougher case: coins whose owners may be gone, offline, or unable to respond. These are thought experiments, not features available in Bitcoin. To understand them, it helps to look at what they might solve, what they could cost legitimate users, and what a real implementation would still require.
Why could quantum computers threaten Bitcoin?
Bitcoin transactions are authorized with private keys. A public key lets the network check that a signature is valid without revealing the private key. With today's computers, calculating the private key from the public key isn't considered practically feasible. But a sufficiently capable quantum computer could change that by using Shor's algorithm to solve the relevant mathematical problem.
Not every Bitcoin address is equally exposed. Some older outputs have public keys visible on the blockchain. Other address types generally reveal the public key when the owner spends, which changes the exposure timeline. The practical risk depends on the output type, how it's used, and whether a capable quantum computer actually exists.
What is Q-Day, and is it imminent?
"Q-Day" is shorthand for the hypothetical moment when a quantum computer can perform cryptographic attacks at a useful scale. No publicly demonstrated quantum computer can steal Bitcoin this way today. Estimates about when such a system might exist vary, and there's no reliable date to plan around.
That uncertainty matters. A protocol response has to be designed before an emergency, but rushing changes based on a distant or poorly understood threat can create its own problems. Bitcoin developers would need to weigh the likelihood and timing of quantum attacks against the cost of changing the rules that govern funds held by millions of users.
Why can't Bitcoin identify the rightful owner?
If a thief can produce a signature that satisfies Bitcoin's current rules, the network has no built-in way to distinguish that signature from one made by the original owner. The chain verifies cryptographic conditions, not identity, intent, or how a key was obtained.
That's the design constraint behind Fields's proposal. Instead of trying to recognize a quantum thief directly, the idea changes what happens when a vulnerable coin is spent. Under the proposed approach, an attempted spend could require collateral, allow a challenge period, or trigger an auction. These mechanisms may change an attacker's payoff - but they also add extra rules and costs for honest owners.
How would a quantum landmine work?
A landmine is a hidden, pre-arranged claim an owner can use if someone later tries to spend their vulnerable Bitcoin. The owner would set it up before Q-Day, while they can still prove control of the original private key without facing the hypothetical quantum threat.
In simplified terms, the owner creates a small, separate quantum-safe output that includes a hidden proof tied to the vulnerable coins. The proof is intended to be opaque to outsiders: it shouldn't reveal its contents or even advertise that it creates a trap. If someone later tries to move the old coins, that proof could give the original owner a way to challenge the transaction under new consensus rules.
The collateral-and-challenge sequence
Fields's example can be understood as a chain of conditions:
- Prepare in advance. The owner creates the hidden proof and commits to a quantum-safe destination for any recovered funds.
- An attacker attempts a spend. The attacker uses a quantum computer to recover the old private key and tries to move the vulnerable coin.
- The spend requires collateral. Under the proposed rules, the attacker would need to add an equal amount of Bitcoin from a quantum-safe wallet. For a 1 BTC target, that means 1 BTC in collateral.
- The transaction enters a restricted state. The target coin and collateral are locked together during a challenge period. Fields uses 30 days as an example, not a fixed parameter.
- The prepared owner challenges. If the owner reveals the pre-Q-Day proof within the window, the rules could allow them to move the combined amount to the previously committed safe destination.
The incentive is simple: the attacker may turn a potential win into a loss. They also can't reliably predict which vulnerable wallets have prepared hidden claims, so even a key recovery might not lead to a profitable spend.
The collateral problem for legitimate holders
This approach doesn't only affect thieves. If an honest owner wants to move legacy coins after Q-Day, they may face the same collateral requirement. In the example, moving 1 BTC could require access to another 1 BTC in a quantum-safe wallet.
That's a real liquidity and access issue. Someone whose savings are concentrated in an old wallet might not have spare Bitcoin available to post. Others may have lost access to the wallets needed to prepare commitments, lack the technical ability to set things up, or simply miss the change in time. In other words, a rule meant to deter theft could make migration harder - or impossible - for some legitimate holders.
And the landmine depends on preparation and response. Owners must create the proof before the threat arrives, and they must notice an attempted spend during the challenge period. It doesn't help someone who has lost their key, never prepared a commitment, or can't act before the deadline.
How could auctions address abandoned coins?
A landmine only works when an owner can prepare and respond. That leaves a hard category: coins that look abandoned, including holdings where the key may already be lost. If no one is available to challenge a spend, the landmine has nothing to trigger. Fields lays out two auction approaches intended to make theft less attractive even when a presumed owner can't intervene.
These ideas don't restore access to a missing owner. Instead, they try to change who benefits from a theft attempt and how much the attacker stands to lose. That distinction matters: stopping a quantum thief from keeping coins isn't the same thing as returning coins to the person who originally held them.
Staked auction: challenge with a prior commitment
In a staked auction, a participant would lock up quantum-safe Bitcoin before Q-Day and secretly register a bid tied to a specific old wallet they think could be targeted. The participant puts value at risk in advance so they can challenge a future attempt to spend those coins.
Say an apparently abandoned wallet contains 50 BTC. A future attacker tries to move it and posts 50 BTC as collateral. During the auction window, someone who registered a bid in advance can challenge the attempt. In Fields's example, a successful challenger receives part of the attacker's collateral, while the vulnerable coins are destroyed rather than paid out to the bidder.
The point is deliberately different from a conventional recovery process. The challenger isn't claiming to be the lost owner. The goal is to deprive the thief of a reliable payday, even if the original coins don't end up back with anyone.
That raises practical questions. How would bids be registered and kept secret? How much collateral would a challenger need? What portion of the attacker's stake would be paid out, and what happens to the rest? Fields's post doesn't fill in these gaps. In other words, it's an incentive proposal, not a complete market design or consensus spec.
Sats auction: make bidders risk losing their bids
The second idea - a sats auction - doesn't require participants to stake funds ahead of time. Instead, a spend of vulnerable coins would trigger a contest. The highest bidder would receive the coins minus their bid, and the runner-up would pay their bid and receive nothing.
This structure is meant to make participation costly even for people who don't win. A would-be attacker could face bids from others who might prefer paying to stop the theft rather than letting the attacker keep the funds. But it's not a guarantee the attacker loses; the result depends on the bidding rules, participant incentives, and the value of the coins.
The setup resembles an all-pay auction, where even losing bidders pay. These can make contests expensive - but they can also create weird, hard-to-predict incentives. If bidders expect the coins to be very valuable, competition could drive bids higher. If they don't, the attacker might face little pushback. The rules would still need to spell out how bidding works, who's allowed to join, and how the proceeds are handled.
Both auction ideas aim to cover the gap left by owner-dependent landmines. Their trade-off is that they can impose losses on participants and may destroy or redistribute value rather than helping the original owner. That might still be preferable to an attacker taking a windfall, but it's a policy choice Bitcoin users and developers would have to face directly.
What would Bitcoin need before these ideas could work?
None of these protections exists in Bitcoin today. Fields describes the concepts as thought experiments, and there's no published implementation or activation schedule in the source proposal. They shouldn't be treated as a wallet feature, an announced upgrade, or evidence that vulnerable coins are already protected.
A working design would require multiple moving parts. First, users would need a quantum-safe way to hold and spend Bitcoin. Then wallets would have to create and manage hidden ownership commitments. Finally, Bitcoin's consensus rules would need to validate collateral, enforce challenge periods, and determine outcomes for special recovery transactions and auctions.
The rule-change and coordination problem
Consensus changes affect how nodes decide which transactions and blocks are valid. So this isn't just a wallet update. Users, businesses, miners, and node operators would need to agree on the new rules and on how the changes would be activated. Fields suggests that some mechanics might be possible with a soft fork, but that's not a finished deployment plan. Detailed design work and community agreement would still be necessary.
Several parameters have real economic consequences:
- Collateral amount: Equal collateral could deter theft, but it could also block legitimate holders who don't have spare funds.
- Challenge window: A longer period gives owners more time to respond, but it also keeps funds locked up longer and could complicate payment expectations.
- Auction payouts: The rules must say what challengers, losing bidders, and other participants receive - or lose.
- Inactive owners: You'd need a policy for what happens when a legitimate holder is alive but offline, unaware, or unable to act.
- Quantum-safe migration: People need a practical destination and a secure way to move funds before or after the threat emerges.
These aren't details you can safely postpone. They determine who bears the cost when Bitcoin can't tell a rightful owner from a quantum-capable key thief. For example, a hard migration deadline might reduce exposure but permanently lock out anyone who misses it. Letting legacy coins remain spendable might preserve an exit route, but it could make every attempted transfer subject to challenges, collateral demands, or destruction of funds.
A practical way to assess the proposal
For now, a reasonable approach is to treat this as a mechanism to be tested - not as a default protection. Judge it by three questions:
- Does it improve expected outcomes for honest owners? Deterring theft only helps if normal migration doesn't become inaccessible to the people the rule is meant to protect.
- Can the rules be applied predictably? Collateral, deadlines, and auction outcomes need to be clear enough that wallets and users can act without guessing how a challenge resolves.
- Can Bitcoin users agree to the trade-off? A protocol rule that burns coins, redistributes collateral, or limits spending would require broad, explicit agreement about which losses are acceptable.
The proposal's strength is that it treats quantum theft as both an incentive problem and a cryptography problem. Its weakness is equally clear: incentives don't remove the need to protect legitimate holders - especially people who are offline or unable to prepare. Any serious design would need to model attacker behavior and the ordinary user who just wants to move their savings safely.
Conclusion
Quantum landmines are a provocative answer to a difficult protocol problem: if Bitcoin can't tell a rightful signature from one produced by a quantum-capable thief, it might make theft costly and contestable instead. Auctions extend that idea to coins whose owners may not be able to respond.
But these mechanisms aren't plug-and-play protections. They shift risk rather than eliminate it. They could deter attackers while also creating collateral burdens, missed challenge windows, and losses for legitimate holders. The real test for any future design is whether it protects prepared owners, leaves a fair path for everyone else, and makes the cost of each choice obvious.