News Bitcoin basics Wallets and security

Bitcoin quantum landmines would make thieves post collateral

Bitcoin Core developer Cory Fields outlined an idea on 4 November 2026 intended to make future quantum theft risky for the attacker: anyone moving vulnerable coins would have to supply collateral, which an owner who prepared in advance could claim. Published on the bitcoin-dev mailing list, it is a thought experiment, not an active rule, a software release or a feature that holders can enable in a wallet today.

Checked on 6 November 2026.

Blank orange coin on a navy platform with a hidden trapdoor and abstract waves
Illustration: a coin above a concealed geometric trap with abstract waves. AI-generated artwork, not a diagram of an operating protocol.

Fields, who works at MIT's Digital Currency Initiative, starts with an economic question inside a security problem. If an attacker could eventually derive a private key from a public key, could attempting the theft cost the attacker money? His proposed answer depends on advance preparation and rules that remain unwritten. The post gives no forecast for when a capable quantum computer might arrive.

The risk concerns public keys, not simply the age of a wallet

Bitcoin transactions use digital signatures to demonstrate authority to spend coins. A private key creates a signature, while a public key allows it to be checked. The quantum threat discussed here is the possibility that a sufficiently capable computer could calculate the private key from the public one. That does not mean any existing quantum computer can do it, or that every address exposes keys in the same way.

Some older output types reveal public keys from the outset. Reusing keys after spending can also leave coins protected by a public key that has already been disclosed. Taproot exposes a public key too, so the distinction is more complicated than old wallets versus new ones. The BIP 360 development document distinguishes this prolonged exposure from the shorter period when a spending transaction awaits confirmation.

That distinction matters because a hypothetical attacker has more time to work on a key visible for years. An attack that must finish during a transaction's confirmation window presents a different requirement. Understanding private keys, recovery phrases and control of funds is a better starting point than assuming each quantum-computing headline requires immediate action.

How Fields' landmine would work

In his message to the bitcoin-dev mailing list (Opens in a new tab), Fields assumes a new output type resistant to the relevant quantum attack already exists. Before the threat becomes practical, an owner uses it to prepare a hidden commitment demonstrating earlier knowledge of the old key. The commitment is not fully revealed until needed, so an attacker should not know in advance which coins have this protection.

His example requires someone moving 1 BTC from a vulnerable output to contribute another 1 BTC from a quantum-safe output as collateral. The combined funds move into a new output with special spending conditions. A spender without advance proof would have to wait, for example, 30 days. These figures illustrate a possible design; they are not protocol requirements or terms offered by an existing service.

If an attacker attempts the transfer, the owner could notice during the waiting period and reveal the proof prepared earlier. Under the hypothetical rules, the owner could claim both the original coin and the attacker's collateral. The trap is economic: an attempt to take someone else's money could instead cost the thief the money brought to the transaction.

The hidden element supplies the possible deterrent. An attacker might know a public key is exposed without knowing whether the owner has prepared a claim. But this is a desired property of the design, not a demonstrated operational result. The owner still needs to prepare in time, retain the necessary material and respond within the period when the proof permits intervention.

Honest owners need collateral too, and lost keys remain a problem

The network cannot identify someone as a thief merely because a key was obtained in a new way. If a signature looks valid, additional rules are needed to distinguish earlier possession from later recovery of the key. In Fields' example, the legitimate owner moving old coins must therefore provide collateral too. That is a real usability cost, not a minor implementation detail.

An owner whose entire balance sits in vulnerable outputs might need another source of collateral. Nor can a landmine solve the loss of a private key: someone without that key cannot use it to prepare advance proof. Discussion of old coins, including coins attributed to Satoshi Nakamoto, does not establish that their keys have been lost. Inactivity alone cannot answer that question.

Fields also sketches auction ideas for vulnerable coins without this protection. In one alternative, participants prepare commitments and bids in advance that could undermine the economics of an attack; the original coins may be burned while the reward comes from the attacker's collateral. This is not a way to recover a missing key or automatically compensate an absent owner, and the incentive design remains open.

What separates a developer's message from a network change

The concept first needs quantum-safe infrastructure and then validation and enforcement rules. Fields said he believes the ideas could be implemented through a soft fork, a tightening of transaction acceptance rules, but left the implementation mechanics for future work. The message supplies no landmine BIP specification, production-ready code or activation timetable.

The accessible archive showed no follow-up replies when checked on 6 November. That is neither developer agreement nor evidence that the idea has been rejected. Evaluating such a mechanism requires detailed questions about recognising advance commitments, waiting periods, additional capital and treatment of owners who did not prepare in time. A headline cannot settle those design choices.

For readers in Israel, the message creates no new transfer instruction or deadline for changing wallets. It is a technical discussion with potential implications for a global network, not a local regulatory change. As with post-quantum research involving Lightning, the useful questions are what a proposal protects and what it assumes already exists. Here the contribution is an attempt to put a price on an attack alongside the cryptographic work still required.

Correction and clarification

Found an error? Contact the editors

Share article Back to top