On April 16, 2026, the Bitcoin technical community began a debate regarding the freezing of 74 billion dollars in vulnerable funds. This figure corresponds to “Satoshi era” wallets that lack protection against advanced decryption algorithms. According to ecosystem reports, developers are looking to mitigate the imminent threat posed by Bitcoin quantum computing to the network’s security.
The technical proposal suggests temporarily disabling old addresses that have not migrated to modern signature formats. This measure would affect approximately 1.1 million BTC mined during the protocol’s early years. Adam Back, CEO of Blockstream, has expressed a firm stance, pushing for quantum resistance updates to remain optional for users. His vision prioritizes individual sovereignty over a global algorithmic mandate that could set precedents for censorship.
Had a great time speaking at Paris Blockchain Week with @adam3us of @Blockstream 👏
We chatted Bitcoin institutional adoption and the potential threat of quantum computers! pic.twitter.com/1OEGmPFgNW
— Dan Held (@danheld) April 16, 2026
The risk is concentrated in Pay-to-Public-Key (P2PK) address types, commonly used by Satoshi Nakamoto. Unlike current formats, these expose the public key directly on the blockchain, allowing a quantum computer to derive the private key using Shor’s algorithm. One of the biggest unknowns today is determining exactly when a machine will reach the 20 million qubits needed to break this cryptography.
Voluntary migration as an alternative to freezing user funds
The controversy lies in the balance between collective security and property rights. If a freeze is implemented, funds that do not move before a specific date would become inaccessible. Adam Back argues that users must voluntarily migrate to secure addresses to maintain the integrity of their assets. This transition is not trivial; it requires the private key holder to perform an active transaction to a new output format compatible with post-quantum signatures.
From a structural impact perspective, Bitcoin faces a unique governance dilemma. If the network chooses to ignore these vulnerable coins, a quantum attacker could flood the market with one million BTC, causing an unprecedented liquidity collapse. On the other hand, preventively freezing assets challenges the immutability characteristic of the system. Historically, Bitcoin has avoided direct interventions on user balances, distinguishing itself from networks like Ethereum, where events like the DAO hack forced a restructuring of the history.
To understand the magnitude, the current value of these funds represents nearly 4% of the total circulating supply. The ASI Alliance is already working on infrastructures to mitigate quantum vulnerability through specialized circuits. However, the solution at the Bitcoin protocol level requires a broad consensus that currently seems distant. Back’s proposal seeks to avoid a contentious hard fork that would divide the community between those prioritizing security and those defending freedom of movement.
On-chain data analysis shows that over 60% of the BTC at risk has not moved in over a decade. This suggests that a significant portion of those 74 billion dollars could belong to users who lost their keys or have passed away. Enforcing a mandatory change would force declaring lost these coins permanently, altering the perception of the asset’s programmed scarcity. The derivatives market already reflects some caution, with a slight increase in volatility for options expiring in late 2026.
Implementing Lamport signatures or lattice-based schemes are the strongest technical options on the table. These methods would increase transaction sizes, which would directly impact mainnet fees. Developers must decide if the cost of protecting the network justifies a fee increase for all participants. For now, the debate continues on technical mailing lists while waiting for a formal Bitcoin Improvement Proposal (BIP) to define the migration parameters.
The next critical milestone will occur at the Bitcoin 2026 conference, where the first code draft for the signature upgrade will be presented. Miners and nodes will have to evaluate whether they agree to include these restrictions in their validation rules.
This article is for informational purposes and does not constitute financial advice.
