This website uses cookies
We use cookies to personalise content and ads, to provide social media features and to analyse our traffic. We also share information about your use of our site with our social media, advertising and analytics partners who may combine it with other information that you’ve provided to them or that they’ve collected from your use of their services.
Consent Selection
Details
  • Necessary cookies help make a website usable by enabling basic functions like page navigation and access to secure areas of the website. The website cannot function properly without these cookies.

    • Learn more about this provideropens in a new window
      CookieConsentStores the user's cookie consent state for the current domain
      Maximum Storage Duration: 1 yearType: HTTP Cookie
    • Learn more about this provideropens in a new window
      bcookieUsed in order to detect spam and improve the website's security.
      Maximum Storage Duration: 1 yearType: HTTP Cookie
      li_gcStores the user's cookie consent state for the current domain
      Maximum Storage Duration: 180 daysType: HTTP Cookie
    • Learn more about this provideropens in a new window
      datadomeUsed in context with the website's BotManager. The BotManager detects, categorizes and compiles reports on potential bots trying to access the website.
      Maximum Storage Duration: 1 yearType: HTTP Cookie
    • _pk_testcookie_domainThis cookie determines whether the browser accepts cookies.
      Maximum Storage Duration: 1 dayType: HTTP Cookie
    • __cf_bm [x3]This cookie is used to distinguish between humans and bots. This is beneficial for the website, in order to make valid reports on the use of their website.
      Maximum Storage Duration: 1 dayType: HTTP Cookie
  • Preference cookies enable a website to remember information that changes the way the website behaves or looks, like your preferred language or the region that you are in.
    • Learn more about this provideropens in a new window
      lidcRegisters which server-cluster is serving the visitor. This is used in context with load balancing, in order to optimize user experience.
      Maximum Storage Duration: 1 dayType: HTTP Cookie
  • Statistic cookies help website owners to understand how visitors interact with websites by collecting and reporting information anonymously.
    • Learn more about this provideropens in a new window
      guestRegisters data on visitors' website-behaviour. This is used for internal analysis and website optimization.
      Maximum Storage Duration: 1 monthType: HTTP Cookie
    • Learn more about this provideropens in a new window
      personalization_idThis cookie is set by Twitter - The cookie allows the visitor to share content from the website onto their Twitter profile.
      Maximum Storage Duration: 400 daysType: HTTP Cookie
    • _pk_uidUsed by Piwik Analytics Platform to identify the visitor on repeat visits to the website.
      Maximum Storage Duration: 1 yearType: HTTP Cookie
      _pk_id#Collects statistics on the user's visits to the website, such as the number of visits, average time spent on the website and what pages have been read.
      Maximum Storage Duration: 1 yearType: HTTP Cookie
      _pk_ses#Used by Piwik Analytics Platform to track page requests from the visitor during the session.
      Maximum Storage Duration: 1 dayType: HTTP Cookie
    • FPGSIDRegisters statistical data on users' behaviour on the website. Used for internal analytics by the website operator.
      Maximum Storage Duration: 1 dayType: HTTP Cookie
      FPIDRegisters statistical data on users' behaviour on the website. Used for internal analytics by the website operator.
      Maximum Storage Duration: 400 daysType: HTTP Cookie
      FPLCRegisters a unique ID that is used to generate statistical data on how the visitor uses the website.
      Maximum Storage Duration: 1 dayType: HTTP Cookie
    • _gaRegisters a unique ID that is used to generate statistical data on how the visitor uses the website.
      Maximum Storage Duration: 2 yearsType: HTTP Cookie
      _ga_#Used by Google Analytics to collect data on the number of times a user has visited the website as well as dates for the first and most recent visit.
      Maximum Storage Duration: 2 yearsType: HTTP Cookie
  • Marketing cookies are used to track visitors across websites. The intention is to display ads that are relevant and engaging for the individual user and thereby more valuable for publishers and third party advertisers.
    • Learn more about this provideropens in a new window

      Some of the data collected by this provider is for the purposes of personalization and measuring advertising effectiveness. The provider may use the IP Addresses for ads measurement and ads personalization.

      ads/ga-audiencesUsed by Google AdWords to re-engage visitors that are likely to convert to customers based on the visitor's online behaviour across websites.
      Maximum Storage Duration: SessionType: Pixel Tracker
    • Learn more about this provideropens in a new window
      userRefererDetermines how the user accessed the website. This information is used by the website operator in order to measure the efficiency of their marketing.
      Maximum Storage Duration: 1 monthType: HTTP Cookie
    • Learn more about this provideropens in a new window
      #:session-dataTracks the individual sessions on the website, allowing the website to compile statistical data from multiple visits. This data can also be used to create leads for marketing purposes.
      Maximum Storage Duration: PersistentType: HTML Local Storage
      eng_mtTracks the conversion rate between the user and the advertisement banners on the website - This serves to optimise the relevance of the advertisements on the website.
      Maximum Storage Duration: PersistentType: HTML Local Storage
      t_gidThis cookie assigns a specific visitor ID, when the visitor interacts with ads or content from the website - this allows the website to target the visitor with similar ads or content.
      Maximum Storage Duration: 1 yearType: HTTP Cookie
      t_pt_gidCollects information on user preferences and/or interaction with web-campaign content - This is used on CRM-campaign-platform used by website owners for promoting events or products.
      Maximum Storage Duration: 1 yearType: HTTP Cookie
      taboola global:user-idSets a unique ID for the visitor, that allows third party advertisers to target the visitor with relevant advertisement. This pairing service is provided by third party advertisement hubs, which facilitates real-time bidding for advertisers.
      Maximum Storage Duration: PersistentType: HTML Local Storage
      taboola_session_idThis cookie is used to collect information on a visitor. This information will become an ID string with information on a specific visitor – ID information strings can be used to target groups with similar preferences, or can be used by third-party domains or ad-exchanges.
      Maximum Storage Duration: SessionType: HTTP Cookie
    • Learn more about this provideropens in a new window
      1/i/adsct [x2]Collects data on user behaviour and interaction in order to optimize the website and make advertisement on the website more relevant.
      Maximum Storage Duration: SessionType: Pixel Tracker
      muc_adsCollects data on user behaviour and interaction in order to optimize the website and make advertisement on the website more relevant.
      Maximum Storage Duration: 400 daysType: HTTP Cookie
      guest_idCollects data related to the user's visits to the website, such as the number of visits, average time spent on the website and which pages have been loaded, with the purpose of personalising and improving the Twitter service.
      Maximum Storage Duration: 400 daysType: HTTP Cookie
      guest_id_adsCollects information on user behaviour on multiple websites. This information is used in order to optimize the relevance of advertisement on the website.
      Maximum Storage Duration: 400 daysType: HTTP Cookie
      guest_id_marketingCollects information on user behaviour on multiple websites. This information is used in order to optimize the relevance of advertisement on the website.
      Maximum Storage Duration: 400 daysType: HTTP Cookie
    • _gcl_auUsed by Google AdSense for experimenting with advertisement efficiency across websites using their services.
      Maximum Storage Duration: 3 monthsType: HTTP Cookie
      _gcl_lsTracks the conversion rate between the user and the advertisement banners on the website - This serves to optimise the relevance of the advertisements on the website.
      Maximum Storage Duration: PersistentType: HTML Local Storage
    • pardot [x2]Used in context with Account-Based-Marketing (ABM). The cookie registers data such as IP-addresses, time spent on the website and page requests for the visit. This is used for retargeting of multiple users rooting from the same IP-addresses. ABM usually facilitates B2B marketing purposes.
      Maximum Storage Duration: SessionType: HTTP Cookie
  • Unclassified cookies are cookies that we are in the process of classifying, together with the providers of individual cookies.
    • cs_analytics_ip_blockedPending
      Maximum Storage Duration: SessionType: HTTP Cookie
      user_tokenPending
      Maximum Storage Duration: 1 yearType: HTTP Cookie
    • _twpidPending
      Maximum Storage Duration: SessionType: HTTP Cookie
Cookie declaration last updated on 8/20/26 by Cookiebot
[#IABV2_TITLE#]
[#IABV2_BODY_INTRO#]
[#IABV2_BODY_LEGITIMATE_INTEREST_INTRO#]
[#IABV2_BODY_PREFERENCE_INTRO#]
[#IABV2_BODY_PURPOSES_INTRO#]
[#IABV2_BODY_PURPOSES#]
[#IABV2_BODY_FEATURES_INTRO#]
[#IABV2_BODY_FEATURES#]
[#IABV2_BODY_PARTNERS_INTRO#]
[#IABV2_BODY_PARTNERS#]
About
Cookies are small text files that can be used by websites to make a user's experience more efficient.

The law states that we can store cookies on your device if they are strictly necessary for the operation of this site. For all other types of cookies we need your permission.

This site uses different types of cookies. Some cookies are placed by third party services that appear on our pages.

You can at any time change or withdraw your consent from the Cookie Declaration on our website.

Learn more about who we are, how you can contact us and how we process personal data in our Privacy Policy.

Please state your consent ID and date when you contact us regarding your consent.
Image Burning quantum-vulnerable coins is a bad idea

Burning quantum-vulnerable coins is a bad idea

Timer5 min read

  • Bitcoin
  • Technology

The debate over burning quantum-vulnerable Bitcoin has simmered for years, but it’s now gaining traction among influential Bitcoin community members (Peter Wuille, Jameson Lopp, @calle/@niftynei). Their push or acceptance for a hardfork to destroy these coins, often cloaked in good intentions, threatens the core of Bitcoin’s promise: property rights for anyone, independent of institutional control.

Bitcoin exists to secure property rights without reliance on governments. Its fixed supply prevents value theft through inflation, and its design ensures coins can’t be seized or reassigned by fiat. The whole point is that no one can steal from you. All other benefits—easier economic calculation, lower time preference—stem from this foundation.

Many may consider this quite ironic given that the threat of quantum computers is exactly that: theft. But this is the point everyone gets wrong. There is in fact no appreciable threat of theft from quantum computers. The threat of theft stems only from well-meaning interventionalists.

A hardfork is state-like intervention in the Bitcoin network, imposing the majority’s will on a minority. It’s only justified in existential crises, 

like a direct threat to the network’s survival. Quantum computing isn’t that threat. Practical quantum computers capable of breaking ECDSA are at least a decade away, giving us ample time to soft-fork quantum-resistant address formats and voluntarily move coins to safer addresses. In fact, owners of vulnerable P2PK addresses can already transfer funds to secure formats like P2PKH—unless of course, they don’t actually own the coins.

There is not a single person who will not have ample time and opportunity to move their coins to non-vulnerable addresses. Any and all coins remaining in quantum vulnerable addresses at the advent of quantum computers should be considered either as donations to those developing such machines, or ownerless. If something is ownerless it is fair game to anyone who can claim ownership over it.

The argument for burning coins hinges on fear: roughly 1.7 million P2PK coins, often labeled “lost,” could be vulnerable. But “lost” doesn’t necessarily mean unowned. We simply don’t know if anyone owns them. In fact, it hasn’t even been more than a few weeks since 80,000 btc that has featured on several lists of “lost” coins were moved for the first time in 14 years. 

Some claim 25% of Bitcoin’s supply is at risk, but this adds coins being currently used in unsafe ways, such as exchanges reusing addresses—a practice unlikely to persist in a quantum era. If owners of vulnerable coins choose not to move them, that’s their right. I find the very idea of burning coins that are not your own squarely contradictory to Bitcoin’s ethos.

I also cannot find any evidence to support the argument that these coins represent some threat to market stability. Below, I have listed all coins in P2PK addresses and grouped them by size band. There are only about 10,200 BTC in addresses that could cause any market disruption. Given how small these balances are, this disruption would be both minor and temporary. A single middle-sized bitcoin treasury being liquidated would have a bigger impact. Moreover, the effect of the coins in any of these addresses coming to market at any given time is not distinguishable from current whale behavior. 

Distribution and amount of quantum vulnerable coinsAlmost all vulnerable coins are coinbase transactions that have never moved. Out of the 34,287 addresses in the 10 - 100 BTC band, 34,068 have balances between 49 and 51 BTC. Under no technological scenario I have ever heard suggested do all these addresses suddenly become reversible in an instance. Reversing an address will take time and it will cost money. Reversing an address with 3,233 BTC in it will take as long as reversing one with 50 BTC.

In effect this means that the proper treasure hunt only really involves 24 addresses. The rest will be worth relatively little, and may not be worth the time and effort at varying stages of technological development. This also presents us with an opportunity I consider beneficial enough that it warrants consideration on its own:

If no coins are left in P2PK addresses, we will have no hard evidence of the progression of quantum computing power towards the actually scary scenario for Bitcoin as it’s currently structured; the point where private keys can be calculated from signatures in less than 10 minutes. If we leave the P2PK coins as they are, the Patoshi stack alone will literally act as a countdown clock informing us of the progression of practical quantum computers. This will give us a dependable way of calculating the time-risk of using Taproot addresses. Increasing tick speed will also act as a strong incentive for UTXO owners to move their coins to secure address formats.

Consider these points:

  • Quantum computers can’t create new bitcoin; the 21-million cap holds

  • A quantum miner selling recovered coins is no different from a whale dumping theirs—market impacts are manageable

  • It will take the same time and effort to reverse any two addresses and we have no idea what the costs will be—that might make many P2PK addresses unprofitable to recover, perhaps forever

  • Vulnerable coins won’t flood the market at once; some large addresses might come in early since they are the most attractive to reverse, but overall they’d trickle in slowly as most are 50-coin coinbase UTXOs

  • Burning coins is like banning treasure hunting to prevent “wealth redistribution.” It’s absurd and undermines bitcoin’s credibility as neutral and non-sovereign

One of the most important tenants of Bitcoin is that it has a fixed supply. Altering the supply critically undermines the assurances users have in bitcoin as sound money. Burning coins alters the supply. Another one is that Bitcoin offers the right to self custody. Burning coins violates the right to self custody. The whole thing is absurd: some people are so concerned with avoiding theft that they want to commit theft.

Forcing a hardfork to burn coins not only destroys the idea that bitcoin supply is fixed, it violates Bitcoin’s promise of neutral property rights. If we override owners’ rights once, we open the door to future interventions. Bitcoin’s claim to sovereignty would crumble, replaced by rule-by-fiat. That is the way Ethereum operates, not Bitcoin. It’s one of the lamest possible ways to ruin one of the greatest technologies ever.

Published onAug 5th, 2025

Writer
Led Bitcoin Research since 2017.

related articles

Welcome to CoinShares

Personal Data

0102

When you visit CoinShares website, cookies enhance your experience. They help us to show you more relevant content. Some cookies are necessary for the site to work and will always be active. Blocking some types of cookies may impact your experience of the website and the services which we offer on our website.

We use cookies on our site to optimize our services. Learn more about our EU cookie policy or US cookie policy.

  • Necessary
    Question circle icon
  • Preferences
    Question circle icon
  • Statistical
    Question circle icon
  • Marketing
    Question circle icon
Necessary cookies help make a website usable by enabling basic functions like page navigation and access to secure areas of the website. The website cannot function properly without these cookies.
Preference cookies enable a website to remember information that changes the way the website behaves or looks, like your preferred language or the region that you are in.
Statistic cookies help website owners to understand how visitors interact with websites by collecting and reporting information anonymously.
Marketing cookies are used to track visitors across websites. The intention is to display ads that are relevant and engaging for the individual user and thereby more valuable for publishers and third party advertisers.