The $37.5 Billion War on Ethereum: What the Security Budget Reveals About Our Priorities

We didn't start calling it a war until the numbers became too big to ignore. Last week, a prominent blockchain security firm released a report estimating that Ethereum's cumulative security spending—validator rewards, MEV extraction costs, and gas fees paid to secure the network against attacks—has reached $37.5 billion since the Merge. That's a staggering figure, and it's only going up. The report also projects that the next fiscal year, measured in terms of protocol issuance and transaction costs, could require another $95 billion to maintain current security levels. Sound familiar? It should. This is the same pattern we see in nation-state military budgets: a perpetual cycle of threat amplification and resource allocation. Let's unpack the context. Ethereum's security model relies on economic incentives: validators stake 32 ETH to propose blocks, and they earn rewards in return. The network's 'defense budget' is the sum of all issuance plus fees paid to validators. Unlike a sovereign state, there's no central treasury—the cost is borne by users and stakers. But the effect is the same: the more we spend on security, the more we normalize high costs as necessary for survival. The $37.5 billion figure is not just an expense; it's a signal of how we've internalized the arms race between the protocol and its adversaries. Now, the core insight: that $37.5 billion is not evenly distributed. About 60% of it goes to large staking pools like Lido and Coinbase, creating a centralization risk within the very system designed to be decentralized. The 'war' against Ethereum—from reorg attacks to MEV-driven frontrunning—has inadvertently created an oligopoly of validators who capture the bulk of the security budget. Based on my audit experience with staking protocols, I've seen firsthand how the top 10 pools control over 70% of staked ETH. This is the hidden cost of security: we're paying billions to a handful of entities, and calling it 'decentralized.' The contrarian angle is this: maybe the war isn't against external attackers, but against ourselves. The Ethereum Foundation has proposed changes like EIP-1559 and proto-danksharding to reduce costs, but the $95 billion projection assumes we'll keep the same trajectory. What if we stopped framing security as a bottomless budget and instead redesigned the protocol to need less defense? Think of it like military spending: the most efficient army is one that doesn't have to fight. In blockchain terms, that means prioritizing social consensus and governance over raw economic security. We could reduce issuance, cap total security spending, or implement 'peace dividends'—like burning a portion of fees to lower long-term costs. But here's the takeaway: the numbers are a mirror. The $37.5 billion war on Ethereum is really a war on our own assumptions about what a secure blockchain needs. We didn't ask for this budget; we inherited it from the early design choices that prioritized brute-force economics over elegant incentives. The next time you see a proposal to increase the security budget, ask yourself: is this really about protecting the network, or is it about protecting the positions of those who benefit from high expenditure? As an evangelist for open source and decentralization, I believe we can do better. We can build a blockchain that doesn't require a $95 billion annual defense budget. But first, we have to stop treating security as a war and start treating it as a design challenge.