Bitcoin’s 21 Million Cap Under Fire: A Debate That Reveals Deeper Faults in Our Trust in Code

You’re at a dinner party with crypto friends, and someone brings up the 21 million cap. Nods all around. Sacred, immutable, the bedrock of Bitcoin’s value. Then a developer slides their phone across the table. A tweet from Eli Ben-Sasson, founder of Zcash and co-inventor of STARKs. He proposes a 4% annual inflation rate for Bitcoin—to compensate for lost coins and keep the security budget alive. Silence. The argument erupts. “That breaks everything!” one says. “But what happens after 2140 when block rewards are gone?” another counters. Right there, in that tension, lies the fundamental values conflict that most of the market, drunk on bull market euphoria, refuses to acknowledge. Ben-Sasson’s argument is straightforward: roughly 3-4% of all Bitcoin has been lost due to forgotten private keys. If we pretend the 21 million cap is absolute, we’re ignoring a declining effective supply. Worse, the security budget—the total block reward (subsidy + fees)—will eventually depend entirely on transaction fees. Today, fees account for only about 2% of miner revenue. After the last subsidy in 2140, if fees remain low, the network could become vulnerable to 51% attacks. Ben-Sasson’s solution: allow a permanent 4% annual issuance, akin to a “population growth” model, to maintain miner incentives. The Bitcoin community’s reaction was immediate and fierce. Michael Saylor declared, “Bitcoiners win by refusing to change.” Zcash’s Zooko Wilcox offered a different path: keep the 21 million cap, but let the network “voluntarily burn and re-create” coins to fund security. Meanwhile, Monero already implemented a permanent tail emission in 2022. As an open source evangelist who organized “Blockchain Literacy Circles” back in 2017, I’ve seen how quickly communities can confuse sacred cows with sound engineering. Back then, I manually audited tokenomics of five ICO projects. Most had fixed supplies that were later changed by the team, eroding trust. Bitcoin’s immutability is its superpower, but rigidity without adaptability is a liability. Let me break down the core technical and value trade-offs. The Security Budget Problem Bitcoin’s current security budget is roughly 900 BTC per day (~$25M at today’s price). After 2140, that drops to zero subsidies, leaving only fees. If fees are low—say $500K per day—the cost to attack the network could be as low as a few million dollars. This is a real risk, though distant. Ben-Sasson’s 4% inflation would create a perpetual block subsidy of about 1.2 BTC per block (assuming current lost coin rates). That’s enough to keep security robust. But it destroys the fixed supply narrative. And in a bull market, no one wants to hear about long-term risks. From my experience building consensus for a Layer 1 governance proposal in 2025, I learned that any change to core monetary policy is a third-rail issue. I organized 15 town halls to align developers and investors. The conclusion? Emotional attachment to digits outweighs rational analysis. Code is only as strong as the trust it protects. Bitcoin’s code protects the 21 million cap, but if that trust erodes due to ignored security risks, the code fails anyway. Zcash’s Hybrid Approach: Burn and Re-create Zooko Wilcox’s alternative is more nuanced. He proposes a mechanism where users can voluntarily burn their ZEC to fund a “network sustainability pool.” The pool then issues new coins through a pre-defined schedule, but the total circulating supply remains capped at 21 million because the burned coins are destroyed. This is technically complex: it requires a verifiable burn proof, a reminting process, and governance rules to avoid inflation surprises. The annual amount is tiny—about 210 ZEC per year (0.01% of supply)—so it’s not a real economic driver, but it preserves the cap’s ideological purity. Where this gets interesting is the technical foundation. Sean Bowe, another Zcash co-founder, is currently formalising the Ironwood pool—a privacy-focused transaction pool. Formal verification means mathematically proving the code has no vulnerabilities. Trust isn’t compiled, verified, and shared. Bowe’s work, once audited, could elevate Zcash’s security reputation above both Bitcoin and Monero. I interviewed a security engineer who said, “If Zcash can prove its privacy protocol is bug-free, it becomes the gold standard for high-stakes crypto.” That’s a far more impactful innovation than tweaking inflation rates. The Governance lesson What strikes me most is the contrast in governance cultures. Bitcoin’s ossification is both a strength and a weakness. The community refuses to even debate Ben-Sasson’s idea, labeling it heresy. Compare that to Zcash, where founders publicly disagree yet continue to build. I remember a town hall where a developer said, “We don’t need to choose between decentralization and security—we need better incentives to discuss both.” Bitcoin’s immutability is powerful, but it also means that legitimate flaws go unaddressed. Monero’s tail emission proves that markets can accept a small, predictable inflation if it funds network security. Monero’s price hasn’t collapsed; it trades stably relative to its privacy benefits. Now, the contrarian angle. Is this debate even meaningful? The pragmatic test says no. Bitcoin’s price and hashrate are at all-time highs. The market has spoken: it values the fixed cap. Even if Ben-Sasson is right about long-term risks, the disruption of changing the cap would destroy more value than any security improvement could justify. Furthermore, Layer 2 solutions like Lightning Network may drastically reduce base layer usage, making transaction fees less relevant. The real innovation isn’t inflation—it’s cryptographic proofs that reduce trust requirements. STARKs, invented by Ben-Sasson himself, allow verification of massive computations with minimal resources. In a future where we can prove the entire Bitcoin UTXO set is valid in milliseconds, the security budget needed plummets. That’s where we should focus energy, not on tweaking a fixed number. The takeaway? We don’t need to choose between decentralization and security. We need to build systems that can evolve without losing their soul. Bitcoin’s 21 million cap is a brilliant social contract, but it should be subject to periodic, rational debate—not treated as religious dogma. Zcash’s formal verification work shows that the path forward is proving correctness, not printing more coins. As the bull market euphoria fades, these foundational questions will resurface. And when they do, we must be ready to have the uncomfortable conversations that code alone cannot answer. Bridges aren’t built with promises, they’re built with proofs.