Cory Fields outlines three quantum-theft deterrents for Bitcoin

Bitcoin Core developer Cory Fields has outlined three conceptual mechanisms to deter quantum-enabled theft of Bitcoin (BTC): Quantum Landmines, Staked Auction and Sats Auction. The proposal remains at the design stage, with each mechanism requiring further development before implementation.

What are the three proposed deterrents?

Fields’ concepts intervene at different points in the proposed response. Quantum Landmines focuses on cryptographic verification, Staked Auction on removing vulnerable BTC, and Sats Auction on third-party competition for an attacker’s collateral.

• Quantum Landmines would use cryptographic proofs to protect funds, according to Fields. The outline leaves the proof type, its producer and the verification point unspecified, so implementation requirements remain open.
• Staked Auction would burn vulnerable BTC to reduce risk. Unlike a control that merely restricts movement, the stated mechanism destroys the designated balance and leaves the holder without spendable BTC from that position.
• Sats Auction would let third parties compete for an attacker’s collateral. It would add an auction-like allocation step after an attack and place outside participants inside the proposed deterrent.

What role does equal collateral play?

The earlier design supplies a more explicit condition. Fields previously outlined a design requiring equal collateral before vulnerable coins could be moved, making that prerequisite part of the transfer process rather than an after-theft remedy.

The Sats Auction description addresses a related but distinct stage. It says the proposed collateral requirements could apply when legacy BTC is spent after an attack, while third parties compete for the attacker’s collateral.

The timing limits the proposal’s stated scope: the source ties the collateral requirement to legacy BTC spent after an attack. It does not explain how a system would classify the relevant coins, calculate the required collateral or coordinate the requirement with ordinary Bitcoin payments.

What operational changes would implementation require?

If the ideas move into implementation, custodians, exchanges and wallet operators would face different work depending on the mechanism. Quantum Landmines would require proof creation and verification within fund-handling workflows; Staked Auction would require a burn process; Sats Auction would require collateral custody, bidding and settlement rules.

For users, the potential effects also differ. Proof requirements could add a condition to moving protected funds, a burn would remove vulnerable holdings from spendable use, and an auction could determine the disposition of collateral after an attack.

Fields presents none of the concepts as a completed Bitcoin protocol change. His outline provides names and broad functions, but not code, activation criteria, implementation dependencies or a deployment timetable. As a result, no present user, business or market-structure effect follows from the proposal alone.

What must be developed next?

Quantum Landmines needs a defined cryptographic proof and a rule for checking it before funds move. Staked Auction needs a precise burn procedure and an operational definition of vulnerable BTC. Sats Auction needs rules for holding and transferring attacker collateral, including how third parties would compete.

All three also need clearer boundaries around the assets they govern and the moments when their requirements would activate. The source does not specify how the proposals would coordinate with ordinary transactions or what would enforce each condition. Those unresolved questions determine whether the concepts can become implementable protocol rules rather than conceptual safeguards.

There is no stated deadline for that work. Until the mechanisms receive the further development Fields says they need, Bitcoin users should treat the three names as proposed design options, not active protections or settled changes to transaction rules.

The next observable milestone is therefore a deployable specification and implementation path; without that work, there is no activation date, enforcement window or protocol-level market-structure change to track.