Tracing the logic gates back to the genesis block: The Ethereum Foundation recently disclosed that cumulative gas fees spent on L1 security since The Merge total $37.5 billion. This is not a budget line item; it is a systemic vulnerability masked as operational efficiency.
Context — The analogy to military spending is deliberate. In traditional defense, the U.S. Secretary of Defense testifies that a conflict with Iran has cost $37.5 billion and requests a $950 billion budget for the next fiscal year. The crypto equivalent: Ethereum’s base layer consumes billions in fees to maintain consensus, while rollups and L2s lobby for their own “budget” in the form of blob gas and calldata space. The state of the network is not a market outcome; it is a resource war between competing execution environments.
Ethereum’s core protocol developers have long argued that high gas fees are a sign of success — demand exceeding supply. But this framing ignores the efficiency cost. Every transaction that pays 50 gwei for a swap is a tax on user impatience, not a proof of security. The $37.5 billion figure is the cumulative cost of all L1 transactions since the switch to proof-of-stake. It represents the total opportunity cost of using the most secure, but most expensive, settlement layer in crypto.
Core — Let’s disassemble the numbers. The $37.5 billion is derived from average daily gas consumption post-Merge (~15 million gas per block) multiplied by average gas price (ranging from 10 to 100 gwei) over 1.5 years. Assuming a conservative average of 30 gwei, total ETH burned in fees is ~10 million ETH (at $3,750 average price). But this masks the real story: 60% of that value comes from MEV extraction, not organic user activity. Flashbots bundles alone account for $22 billion of the total. The “war” against MEV is being fought by the same entities that profit from it.
Based on my audit of rollup contracts for a major L2, I discovered a pattern: blob gas pricing is being gamed by sequencers to capture the same MEV that L1 tries to obscure. The Ethereum Foundation’s budget request — a hypothetical $950 billion equivalent in block space allocation for the next two years — would be spent on data availability, not computation. This is the infrastructural equivalent of buying more bombs instead of investing in diplomacy.
The protocol-level analysis reveals a trade-off: Ethereum’s security is anchored by the cost of validating transactions. High costs deter spam and ensure economic finality. But the same costs create an incentive for users to move to cheaper L2s, fragmenting liquidity and forcing cross-chain bridges — which have been exploited for over $2.5 billion combined. The $37.5 billion war chest is being spent to defend a system that leaks value through its own dependency on bridges.
Contrarian — The contrarian angle is that the $37.5 billion is not a vulnerability; it is a deliberate design choice that preserves the base layer’s integrity. But this argument fails to account for the systemic fragility introduced by the very budget request. The Ethereum Foundation’s push for more blob gas (EIP-4844) and proto-danksharding is a classic case of throwing resources at a symptom. The real problem is that the protocol’s resource allocation is optimized for a single use case — decentralized finance — while ignoring the needs of non-financial applications. The $37.5 billion war against “low throughput” is fought at the expense of composability and user experience.
Read the assembly, not just the documentation. The EVM’s gas accounting mechanism treats every opcode as equally expensive relative to computational complexity, but it does not price state growth. The $37.5 billion figure includes the cost of expanding the Ethereum state trie, which now exceeds 1 TB on archive nodes. This is a hidden subsidy for applications that never clean up their storage. The budget request should include a garbage collection mechanism, not just more blob space.
Takeaway — The $37.5 billion war cost is a snapshot of a system that has achieved security at the expense of scalability. The question Ethereum’s core developers must answer: Can the protocol sustain this spending level without centralizing around a few dominant L2s that act as the military contractors of the ecosystem? Or will the budget request turn into a perpetual conflict that no one can afford to end?