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 Perpetual inflation won’t save your blockchain

Perpetual inflation won’t save your blockchain

Timer14 min read

  • Altcoins

The materials on this website or any third-party websites accessed herein are not associated with and have not been reviewed or approved by: (i) Valkyrie Funds LLC dba CoinShares, its products, or the distributor of its products, or (ii) CoinShares Co., its products, or the marketing agent of its products.

Key takeaways

  • A lot of blockchains are using perpetual inflation, often called tail emission, to attempt to guarantee miner/validator income in the absence of a robust fee market

  • The problem is that all such inflation is denominated in the token native to the blockchain in question, and its future purchasing power cannot be known let alone guaranteed   

  • As a result, protocol security in censorship resistant blockchains is a market outcome not an engineering problem and therefore has no guaranteed solution—either there is future demand for security or there is not, and this cannot be known

  • Since the future token purchasing power cannot be known, no amount of tinkering with the monetary policy is ever guaranteed to sufficiently secure a blockchain—instead, tinkering erodes the monetary properties of the token, risking a downward security death spiral as tokens are unable to compete for monetary demand and the mining/validating rewards lack sufficient value to secure the chain 

  • In short, tail emission is not, and cannot be, a guarantee of sustainable settlement assurance

  • On the contrary, I argue that constantly revising protocol monetary policy presents a bigger risk to long term security than simply letting the market tell us whether it wants something or not

A couple weeks back on 12 August 2025, Monero, PoW blockchain underwent a 6-block re-org. Over several days after, it then suffered several 9-block re-orgs.

While this only represents a 12-18 minute history re-write given Monero’s 2 minute block time target (the time-equivalent of approximately 2 Bitcoin blocks), it is still way outside the range of standard non-malicious re-orgs that happen from time to time on PoW blockchains. Statistically, natural re-orgs past two are highly unlikely, and the probability of occurrence decays exponentially with each additional block. 

It is therefore quite likely that the 6-block re-org was an intentional act on the part of Qubic—a strange blockchain acting as a de facto Monero mining pool. And they have publicly claimed that it was. The attack has been widely represented in the media as a 51% attack, however, more sophisticated analyses have not found any convincing proof of this assertion. 

In all likelihood, the re-orgs were instances of a “selfish mining” strategy—a long-known method for maximising mining revenue by miners who control around 33% of hashrate within PoW blockchains. PoS blockchains are also vulnerable to such attacks, often at even lower levels of total stake, although PoS complexity often makes it a less straightforward matter to analyse.

This is not, however, a post about selfish mining. Nor is it a post about Qubic’s peculiar incentive structure which used token markets to, at least temporarily, improve profitability for Monero miners pointing hashrate towards them, rapidly growing their hashrate. Instead I’d like to discuss a less obvious, but in my opinion, much more important takeaway from the debacle: Namely, that tail inflation is not a viable solution to long term protocol security in blockchains.

Let’s first agree on some definitions

One of the reasons discussions on this topic (and most other debates too if we’re honest) are so tedious is that people don’t agree on the meaning of words and terms and therefore end up talking right past each other. In order to avoid that I want to be ultra clear about what I mean when I refer to certain words and terms.

  1. Protocol Security — Few terms get thrown around as loosely as this one. It is in turn often reduced to “cost to attack”, which is a loose unspecified reference to re-org cost. When we use the term, we will use it under the strict meaning of settlement assurance as laid out in detail by Nic Carter in 2019

  2. Censorship Resistance — The ability for a blockchain to unseat a malicious miner who has achieved 51% or more hashrate contribution and is using it to censor blocks

  3. Tail Emission — The use of infinite inflation as an incentive for block creation

  4. Security Budget — This is a term I prefer to mostly avoid because it cannot be quantified in a meaningful way within the confines of a blockchain protocol. Therefore it is purely conceptually illustrative, carrying no concrete meaning

There seems to be a problem with Bitcoin’s long term security

Let me try to briefly summarise the apparent problem underlying all of this, which all stems from Bitcoin. One of the major assumptions underlying Bitcoin is that once the supply of new coins runs out, transaction fees will take over as the main source of payment for miners.

Technically speaking, this is already the case. Over the last year on average, if you removed the current block emission of 3.125 btc, approximately 0.06 btc of fees would remain (less than half of that if the average was 30 days). The problem looks obvious: Current fees are less than 1/100th the size of the block subsidy, that’s not very much.

Bitcoin fee ratio multiple (FMR)In fact, if fees never improve from here in btc terms, they won’t match the size of the block reward until 6 halvings from now. That’s about 23 years from now. This means that for the mining reward to remain at least at its current level, the product of the bitcoin purchasing power and current total fees per block (btc_purchasing_power * total_btc_fees) needs to grow by a factor of 100 in 23 years.

A lot of people think this is unlikely, so there have been a lot of suggestions of how this can be “fixed”. There’s just one problem with that mindset.

Protocol security in censorship resistant blockchains is a market outcome not an engineering problem

I need to preface this segment with the clarification that when I talk about Censorship Resistant blockchains I am talking exclusively about PoW blockchains. PoS blockchains can per definition not resist censorship, a topic we have covered in depth in previous work. 

When I previously said that Bitcoin’s long term security/settlement assurance is based on an assumption I meant just that. It is not possible to prove that it will be “sufficient” over the long term. Either there is market demand for settlement assurance through transaction fees or there is not. It is almost exactly the same question as to whether there will be demand for bitcoin in the future or not. 

If the answer to either of those questions is “no”, Bitcoin will fail. I also can’t imagine it’s possible that the answer is “yes” to one, and “no” to the other, so the failure condition is almost exactly the same. If people don’t need bitcoin (the money) or Bitcoin (the protocol and network), it will fail. The argument is self-evident.

This reality does not tend to sit well with the engineering types of the world (I am one). As a result, many  “solutions” have been proposed. These “solutions” tend to fall into two categories. Either they aim to change the supply or demand side of the fee market, or they aim to use tail emission as a perpetual reward for block creation.

The problem is that neither of those approaches can provably work. No matter how much one tinkers with either the supply or demand side of the fee market, one cannot guarantee that there will be any demand at all, let alone “sufficient” demand, whatever "sufficient" means in this context. This is obvious enough to most people.

Still, just because it cannot be 'guaranteed' or 'provable', people still think there are theoretically better designs than at present, and that is why these things are proposed. That’s a fair enough position to have, I just cannot stress enough the fact that thinking they will work is as much of a leap of faith as thinking the fee model will work. The truth is that nobody knows if either will work.

A tail emission “security budget” can never be proven sufficient 

It seems to be less obvious to a lot of people that tail emission has the same exact problem of not provably being a solution to incentivise perpetual settlement assurance. At what level is the tail inflation “sufficient”? Setting tail emission at 1% targeting some arbitrary “security budget” can never guarantee settlement assurance at any given level—it’s all pure guesswork.

Since you cannot know the future purchasing power of the token, you are always at risk of the emission being “too low”, necessitating endless changes in monetary policy, and in the extreme, runaway inflation. This further erodes the monetary properties of the token risking a security death spiral as plummeting token prices requires ever-higher inflation rates to finance the “security budget”.

Monero’s vulnerability should be a shot across the bow for tail emission blockchains

As mentioned above, the main point I want to drive home here is that tail emission is no guarantor of long-term blockchain security. Monero implemented tail emission in 2022, and among the community it was expected that it would guarantee sustainability of the block reward. While I suppose that is technically true, as we’ve all just seen, it has also been meaningless in terms of providing workable settlement assurances.

Monero priceWhile there’s a guaranteed perpetual block reward available for Monero miners, Monero the token cannot compete with bitcoin on monetary properties so nobody stores any value in Monero. The outcome is clear as day, Monero purchasing power has been relatively stagnant over the last decade. Against its strongest competitor, bitcoin, the situation is much worse, with Monero plummeting in value over the years.

In other words, tail emission sounds fine and well, but if your token isn’t worth anything no amount of tail inflation will be enough.

This should be a wake up call for blockchain inflationists. It is widely accepted among bitcoiners at least that inflation is harmful to fiat money and society at large. I therefore find it remarkable that there are any bitcoiners at all that believe it wouldn’t be harmful to bitcoin.

The main driver of long-term value in any type of money comes from its low-velocity users looking for an instrument that holds the value of their savings over the long term. These users have a strong preference for a monetary unit they perceive as having the strongest possible monetary properties. If your blockchain doesn’t provide that, they might use it to transact with high velocity, but not to store their wealth while they’re economically inactive. That’s bad news for your token value.

We must resist the engineering temptation to tinker with Bitcoin’s monetary properties

In an earlier paragraph I mentioned that in order for Bitcoin to retain its current settlement assurance over the next 25 years or so it needs to grow the purchasing power of transaction fee rewards ( btc_purchasing_power * total_btc_fees) by about 100 times. I actually don’t think that’s unlikely at all.

Given that bitcoin price has grown by more than 100x over the last 10 years, and over the same time we’ve had several periods of sustained fee levels more than 20x higher than current ones in BTC terms. In other words, 10x growth in price coupled with a 10x growth in fees over the next two and a half decades doesn’t sound that improbable to me.

Total daily BTC transaction feesThat is, I don’t think it’s unlikely so long as bitcoin retains its exceptional monetary properties. If we mess those up by changing the block size, adding infinite inflation, or falling into the general Ethereum mindset of constant and endless revisions to monetary policy, I think that’s a much bigger risk than just letting the market tell us whether there’s demand for bitcoin over the long term.

In fact, the very reason bitcoin is not already at $10m per coin is that we (as one big society and market) fundamentally cannot know whether the assumption of a sufficient future demand for bitcoin turns out to be a good one, or not. Figuring out the answer to that question and pricing the probability accurately as time goes on is exactly what markets are for. Let it do its thing.


 1This is a theoretical level that does not account for a whole range of confounding factors that create a more blurry range around the actually necessary real-world conditions.

Published onOct 2nd, 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.