Saturday, July 11, 2026 Today's news About Live prices →
£ PoundToken
Crypto, covered properly · Est. 2026
Bitcoin

StarkWare Chief’s Inflation Proposal Reignites Debate Over Bitcoin’s Fixed Supply

Eli Ben-Sasson's call for perpetual 4% issuance highlights unresolved questions over miner incentives as Bitcoin's subsidy nears zero.

By Freya Macdonald · ·3 min read
StarkWare Chief’s Inflation Proposal Reignites Debate Over Bitcoin’s Fixed Supply

Eli Ben-Sasson, chief executive of StarkWare, has called for Bitcoin to abandon its 21 million coin supply cap in favour of a perpetual annual issuance rate capped at 4%, reopening a long-dormant debate over how the network will fund its own security once block subsidies disappear. The proposal, posted on X on 7 July, has drawn near-universal rejection from Bitcoin’s core community, according to Crypto Briefing.

Ben-Sasson’s argument rests on the scale of Bitcoin lost to misplaced private keys, forgotten hardware and unrecoverable estates. Estimates cited in the report put permanently inaccessible Bitcoin at between 3 million and 4 million coins, or roughly 15% to 20% of total supply, a figure that only grows with time.

Miner economics at the centre of the proposal

The StarkWare chief frames the shrinking usable supply as a structural threat to network security rather than a curiosity. Bitcoin miners are currently compensated through a combination of block subsidies and transaction fees, but the subsidy halves roughly every four years and is scheduled to fall below one BTC per block around 2036, eventually reaching zero.

Ben-Sasson’s proposed fix is to prevent the subsidy from ever fully vanishing, replacing the current schedule with a rule-based ceiling of 4% annual issuance. He has characterised this not as inflationary policy but as an alternative monetary rule to the one Satoshi Nakamoto encoded in 2009, designed to offset lost coins while keeping miners incentivised over the long run.

A hostile reception from Bitcoin’s base

Reaction from Bitcoin maximalists was swift and largely dismissive, Crypto Briefing reports, reflecting the community’s longstanding treatment of any change to the supply schedule as a threat to the protocol’s credibility. Critics counter that lost coins effectively increase the value of remaining supply, since an effective float closer to 17 million Bitcoin, rather than diluting holders, reinforces scarcity.

There is also a governance obstacle. Bitcoin has no central authority capable of enacting such a change; any alteration to issuance would require overwhelming consensus among node operators, miners and developers. The last comparable rupture, the 2017 block size dispute, ended in a chain split that produced Bitcoin Cash — a precedent regularly invoked by opponents of the proposal.

Why a Layer 2 firm has a stake in the outcome

Ben-Sasson’s intervention is notable given StarkWare’s position in the industry. The firm is a prominent developer of ZK-STARK cryptographic proof technology and has been extending its stack into Bitcoin-adjacent infrastructure, including privacy-oriented initiatives such as strkBTC, according to the report.

That positioning gives StarkWare a direct commercial interest in Bitcoin’s continued security. If mining economics deteriorate as subsidies shrink, the guarantees underpinning Layer 2 systems built atop Bitcoin, including StarkWare’s own products, could weaken. Ethereum addressed a comparable dilemma by shifting entirely to proof-of-stake alongside its EIP-1559 fee-burn mechanism, but Bitcoin’s community has historically rejected such flexibility as a philosophical red line.

For institutional observers, the more consequential metric is not the fate of Ben-Sasson’s proposal but the trajectory of transaction fee revenue relative to the declining block subsidy, a ratio that will determine whether the 21 million cap remains economically viable without protocol intervention.

Read more: StarkWare Chief’s 4% Issuance Proposal Reopens Bitcoin Monetary Policy Debate

More Bitcoin

Leave a Reply

Your email address will not be published. Required fields are marked *