Loading prices…
STKR NewsSTKR News0 of 3 free this month
Markets

Ethereum Devs Weigh a Scaling Upgrade That Could Break 15,000 Apps

Ethereum developers are debating the Glamsterdam upgrade, which offers a 3.3x scaling boost but risks breaking over 15,000 existing smart contracts in the process.

Originally on Decrypt →
AB

Adrian Boysel

Contributor

Nov 17, 2026

5 min read

Photo illustration / STKR News

The Price of Progress

In the world of blockchain development, we often talk about scalability as if it is a free lunch. We assume that with enough clever engineering and a few hard forks, we can magically increase throughput without anyone feeling the pinch. But as the recent discussions around Ethereum's upcoming Glamsterdam upgrade show, that is rarely the case. We are currently staring down a trade-off that pits raw network capacity against the stability of thousands of existing applications.

The core issue revolves around two specific changes being proposed for the Ethereum Virtual Machine (EVM). These changes are designed to optimize how the network handles data and transactions, effectively aiming for a 3.3x increase in capacity. On paper, that sounds like a founder's dream. More room for users means lower fees and a smoother experience. But the technical reality is that these optimizations break long-standing assumptions that developers have relied on for years.

The Breaking Point

During a recent core developer call, the community was forced to reckon with the scale of this disruption. Analysis suggests that these changes could break as many as 15,000 smart contracts currently live on the mainnet. For those of us building in this space, that number is staggering. These aren't just abandoned experiments; many of these contracts represent active liquidity, user assets, and foundational infrastructure for decentralized finance.

The problem is that the EVM was built with certain constants in mind. When you change how gas is calculated or how data is accessed, you change the environment in which these contracts live. If a contract was coded to expect a specific gas cost for a specific operation, and that cost suddenly changes or the operation is restricted, the contract can fail. Unlike a traditional web app where you can just push a hotfix to the server, a smart contract is immutable. Once it’s broken, it’s often broken forever.

Founder Perspective: The Scalability Trap

As a founder, I look at this and see a classic dilemma. We want Ethereum to be the global settlement layer, but to get there, it needs to be faster. However, if the path to speed involves nuking 15,000 apps every few years, we are going to lose the trust of the very people building the ecosystem. It creates a culture of fear where developers are hesitant to deploy complex logic because they don't know if the underlying ground will shift beneath them in twelve months.

Ethereum is currently in a state of constant evolution, which is healthy, but we have to ask where the line is. If we prioritize the new users of tomorrow over the builders of today, we risk turning the network into a graveyard of broken code. The 3.3x capacity boost is tempting, especially as competitors like Solana or L2s continue to eat into Ethereum's market share, but a network is only as valuable as the things built on top of it.

The Developer Trade-off

What makes this situation particularly difficult is that the developers advocating for these changes aren't doing it out of malice. They are trying to solve the very real problem of state bloat and inefficient resource usage. The Glamsterdam upgrade is a genuine attempt to modernize the architecture. But for the developer who has a contract managing millions of dollars in locked value, "modernization" is just a fancy word for a potential disaster.

We have to look at the specifics of what is being proposed. By altering how the network handles specific operations, the devs are essentially trying to squeeze more juice out of the existing hardware. It is an efficiency play. But in the EVM, efficiency often comes at the cost of backwards compatibility. We are seeing a shift in philosophy from "move slow and preserve everything" to "move faster and fix what breaks."

What Builders Should Watch

If you are currently building on Ethereum or planning to launch a project, this is the time to audit your assumptions. You cannot assume that gas costs will remain static or that specific opcodes will behave the same way indefinitely. The Glamsterdam debate is a signal that the core team is willing to break things in the name of progress. This means your code needs to be as resilient and flexible as possible.

For those with existing contracts, the next few months will be critical. You need to verify if your logic relies on the specific parameters being targeted in this upgrade. If it does, you might be looking at a forced migration or, worse, a complete loss of functionality. This is the hidden tax of building on a platform that is still under active construction.

The Long View

Ultimately, Ethereum will likely move forward with some version of these changes. The pressure to scale is too high to ignore. But the fallout from this decision will set the tone for the next several years of development. If 15,000 apps go dark, it will be a PR nightmare and a massive blow to the concept of "code is law." If the transition is handled smoothly, it will prove that Ethereum can evolve without self-destructing.

We are watching a live experiment in governance and engineering. The stakes aren't just transaction speeds; they are the reliability of the entire decentralized web. As someone who has spent years watching this space, I am skeptical of any upgrade that claims to be a win-win. There is always a cost. In this case, the cost might be the very decentralization and stability that made Ethereum attractive in the first place.

The Takeaway

The Glamsterdam upgrade represents a fundamental tension in crypto: the need for speed versus the necessity of stability. For builders, this is a reminder that the underlying protocol is not a static utility. It is a living, breathing, and sometimes destructive force. Keep your eyes on the core dev updates, and never assume your code is safe from the march of progress.


Read the original at Decrypt →

The Brief

Stay Updated on Cutting-Edge Tech

A six-minute morning dispatch on the markets and the technology shaping them.

Free. No spam. Unsubscribe anytime.

Write for STKR

Become a Contributor

Earn $STKR for published stories on markets, protocols, and culture.

  • Earn $STKR for every published piece
  • Editorial support from the STKR desk
  • Byline visibility across the network
  • First look at the upcoming creator program
Apply to Write

Keep reading

All stories

Comments

24 reader responses