Bitcoin's Fixed Supply Under Siege: Zcash Co-Founder Proposes 4% Inflation to Fix a 'Broken' Security Model

Bitcoin transaction fees have collapsed to near 2019 lows. Over the past week, the average fee per transaction hovered at $0.12, contributing less than 2% of total miner revenue. The remaining 98% comes from the block subsidy—a fixed reward that halves every four years and will effectively hit zero by 2140. This data point is not new. What is new is that a co-founder of Zcash and co-inventor of STARK proofs, Eli Ben-Sasson, has publicly called this design a systemic failure. He argues that the 21 million cap is an arbitrary constraint that will eventually destabilize the network's security budget. His proposed fix: replace the fixed supply with a 4% annual inflation rate, permanently. Context: Ben-Sasson's tweet from early 2026 ignited a predictable firestorm. Bitcoin maximalists immediately invoked the sacred code of 21 million. Michael Saylor's echo—"the network wins when it refuses to change"—became a rallying cry. But this isn't a fringe opinion. Ben-Sasson is a heavyweight in zero-knowledge cryptography. He co-founded Zcash, which itself enforces a 21 million supply cap. His argument rests on a simple arithmetic: if the block subsidy declines to zero and transaction fees don't rise—and current trends suggest they won't—then the security budget shrinks. A network with a shrinking security budget is a network vulnerable to attack. Core: Let's tear this proposal down systematically. The technical implementation is trivial—change one parameter in the consensus code to issue 4% of the current total supply annually instead of a decreasing decay curve. But the systemic consequences are profound. The proposal assumes a constant loss rate of private keys—something Ben-Sasson equates to population death. He wants inflation to offset that loss, keeping the effective circulating supply stable. But here's where the analysis must be forensic. No code has been released. No testnet exists. It's a thought experiment dressed as a proposal. Based on my audit experience, this is a classic red flag: a solution offered without a single line of implementation detail. The community can't verify the assumptions, let alone the security of the change. Now consider the alternatives. Zcash's own founder, Zooko Wilcox, proposed a different mechanism: maintain the 21 million hard cap but allow voluntary token burning that miners can later remint. This is not simple. It requires a complex burn-and-remint smart contract that must be formally verified to prevent double-spend attacks. Sean Bowe, another Zcash core developer, is currently formalizing the Ironwood pool—a privacy pool that undergoes rigorous verification to eliminate hidden bugs. That work is real. It has a specification, a timeline, and a third-party audit scheduled. It is the kind of trust-minimized engineering that a cold dissection demands. Ben-Sasson's proposal has none of this. Yet there is a deeper systemic problem. Ben-Sasson's 4% inflation is actually a cap, not a guarantee. The real issuance could be lower if the loss rate is lower. But in Bitcoin's zero-trust environment, any inflation is perceived as a hack on the core value proposition. It shatters the narrative of digital scarcity that drives the entire market. The argument that 'the network must pay for security' is academically valid, but it ignores the political reality: Bitcoin holders are not rational security maximizers. They are ideological believers in fixed supply. The market has priced the 21 million cap as absolute. Contrarian: Now the angle that bulls might get right. Ben-Sasson's concern is not unfounded. If we model the Bitcoin security budget over the next 100 years, assuming zero fee growth, the hashrate could drop by 90%. That would make a 51% attack affordable for a state-level actor. The proposal—while flawed—forces the ecosystem to confront a real trade-off. The contrarian insight is that the Bitcoin community might eventually need a 'second best' solution: not inflation, but something like a demurrage fee or a transaction fee floor. Monero already runs a permanent block reward of 0.6 XMR per block. It hasn't collapsed. Its security budget is stable. That example provides weak evidence that a soft supply cap can work. But the fatal flaw in Ben-Sasson's narrative is his timing. The market is in a sideways chop. Capital is fleeing to perceived safety. Bitcoin is winning because it is the most rigid, least adaptable asset. Any proposal to change the monetary policy is automatically rejected, not because it's technically unsound, but because it undermines the very thing that makes Bitcoin valuable: predictability. The Zcash community itself is split on this. Wilcox's alternative, while preserving the cap, adds complexity that could introduce new failure modes. The burn-and-remint mechanism must be carefully audited. One integer overflow could drain the pool. Takeaway: The debate over Bitcoin's 21 million cap will not be resolved by calculation or code. It will be resolved by market logic. As long as the security budget remains funded by subsidies and fees stay low, the system is stable—for now. But the clock is ticking. The block reward will keep halving. Eventually, the subsidy becomes noise. Then the question becomes: will the fee market replace it, or will the network face a slow decline into insecurity? Ben-Sasson opened the door to this discussion. He did not offer a viable solution. The only real innovation here is the formal verification work on Zcash's Ironwood pool—a trust-minimized approach that could set a standard for auditing privacy pools. Everything else is noise in the echo chamber of ideology.