Technology•

Ethereum's Glamsterdam Fork Will Not Arrive in December: A Sixfold Jump in Contract Deployment Costs Has Pushed It to Late January at Best

Ethereum developers have moved the Glamsterdam upgrade out of December, giving more than 50 companies until mid-January to repair contracts that a steep rise in deployment costs would break.

Written By :MINRK
Ethereum's Glamsterdam Fork Will Not Arrive in December: A Sixfold Jump in Contract Deployment Costs Has Pushed It to Late January at Best

Photo by Nenad Novaković on Unsplash

Mentioned in This Article

ETH
ETH
Ethereum
$1,664.81
2.38%

1. Glamsterdam leaves the 2026 calendar

Glamsterdam, the next major Ethereum upgrade, will not reach the main network in December as first planned. At their weekly coordination call on November 19, the teams that build Ethereum (ETH) software said mid-January 2027 is the earliest possible activation and late January or early February the realistic window, because application developers need time to repair smart contracts the new rules would break.

The slip is modest in calendar terms, a matter of weeks, yet it carries the upgrade across the year boundary and confirms that a problem flagged only recently has become the main factor governing the schedule. The delay does not stem from a flaw in the upgrade's own code. It stems from software that other people have already deployed on Ethereum and that was written with assumptions the upgrade is about to overturn.

Ethereum has no central operator that can set a release date and impose it. Changes to the protocol are agreed by independent engineering teams that each maintain their own version of the network software, and those teams meet on a regular call to settle what ships and when. It was on that call that the new timing emerged, alongside a count of how many outside companies are affected and how quickly they believe they can respond.

2. What the Ethereum upgrade is designed to do

Capacity is the purpose of Glamsterdam. The package is intended to let the network handle more activity at the same time, so that applications already running on it, including on-chain trading venues and lending services, have room to grow without pushing against the limits of the base layer.

Raising capacity on a blockchain is never only a question of allowing more transactions. Every node that verifies the chain has to store and process the data that transactions create, and some kinds of data are far more burdensome than others. Information that must be kept permanently, such as the code of a newly deployed program, stays with the network indefinitely, long after the transaction that created it has been forgotten.

For that reason, a plan to increase throughput is usually paired with a review of what different operations cost. If the network is going to do more work per block, developers want the price of each operation to reflect the load it really places on the system. Glamsterdam includes such a repricing, and one element of it is the source of the present difficulty: a sharp increase in the fee for creating new permanent data.

3. Why is the Glamsterdam upgrade delayed?

Glamsterdam is delayed because one of its changes makes deploying a smart contract far more expensive, and existing programs built around the old price could stop working. Under the new rules, the base charge for launching a contract climbs from 32,000 gas to 183,600 gas, nearly six times the current level. Storing the program's code is billed separately, on top of that base amount.

Gas is the unit Ethereum uses to measure computing work. Each operation a transaction performs consumes a set amount of it, and the sender must supply enough to cover the whole sequence. When the supply runs out before the sequence is complete, the transaction does not finish partially. It fails, and whatever it was meant to accomplish does not happen.

That mechanism is what turns a price change into a compatibility problem. Many contracts do more than hold funds or record balances. Some create other contracts as part of their normal operation, and their authors often set aside a specific amount of gas for that step, calculated from the costs that applied when the code was written. A program that budgets for a 32,000 gas deployment charge and suddenly faces 183,600 can exhaust its allowance in the middle of a transaction and fail.

The difficulty is compounded by the way smart contracts work. Once published, a contract's code generally cannot be edited in place the way ordinary software is patched. Fixing a hard-coded assumption can mean deploying replacement contracts, moving users or funds across, or changing surrounding systems so that the fragile path is no longer used. None of that can be done overnight, which is why the affected teams asked for weeks and not days.

4. How many applications are exposed

Estimates of the damage vary with how broadly it is defined, but the figures discussed by developers are large. Marius van der Wijden, a developer at the Ethereum Foundation, estimated last week that as many as 15,000 programs could be disrupted by the change. Security researchers examining deployed code have separately identified about 200 potential problems.

To get ahead of the issue, the Ethereum Foundation and outside security researchers have been approaching the operators of vulnerable software directly. They told the November 19 call that they had contacted more than 50 affected companies. Most of those companies answered that they could have fixes in place by mid-January, on the condition that the rules stay as currently written.

That condition matters. A team repairing its contracts needs a fixed target. If the fee schedule were revised again, work already under way could have to be redone against different numbers. The companies' replies therefore gave core developers both a date to plan around and a reason to avoid reopening the design.

5. Client teams split on whether to change the rules

Opinion among the groups that write Ethereum's node software leans clearly toward leaving the specification alone. Geth, Nethermind, Reth and ethrex all supported going ahead without modifications. Besu accepted the current approach reluctantly, having first argued for a narrower fix. Erigon remains the holdout and still wants the rules altered.

These names refer to separate implementations of the same protocol. Ethereum deliberately runs on several independently written programs so that a bug in one does not take down the whole network. The arrangement improves resilience, but it also means every rule change has to be implemented identically by each team, and that a decision to proceed needs broad agreement among them.

The alternative to waiting for applications would be to soften or reshape the fee change so that fewer programs break. That route has its own hazards. Van der Wijden warned that one of the workarounds under discussion would break a different set of applications, trading one group of failures for another. With that risk on the table, most teams concluded that holding the rules steady and giving developers time was the safer course.

6. Deadlines for application developers

Two cut-off dates now apply to the companies doing repairs. Application makers have until mid-December to resolve their most serious problems, and until January 10 to deal with less urgent ones. The staggered timetable reflects the difference between failures that would halt a product outright and those that would affect only secondary functions.

The dates also line up with the testing schedule. Developers want the most severe issues cleared before the upgrade is rehearsed in public, so that the rehearsal reveals unknown problems instead of confirming known ones. The later deadline leaves a buffer between the end of application fixes and any activation on the main network, which is consistent with a launch in the final days of January or the start of February.

7. What happens next for Glamsterdam

The next decision point is November 26, when developers meet again and are due to make the final go or no-go call on the plan. If they confirm it, a rehearsal is tentatively scheduled for the week of December 14 on Hoodi, a public test network that mirrors Ethereum.

A test network run is the standard dress rehearsal before any change to the main chain. It lets client teams confirm that their separate implementations agree with one another under the new rules, and it gives application developers a live environment in which to check that their repaired contracts behave as intended. Problems found there can still move the date.

Only once that testing is complete would a main network activation follow. On the timeline described at the call, that points to late January or early February 2027, with mid-January as the earliest date developers consider possible.

8. What the delay means for users and builders

For people who simply hold or transfer ether, the postponement changes little in the short term. The network keeps operating under its existing rules until the upgrade activates, and the capacity gains Glamsterdam promises arrive some weeks later than first hoped.

For teams that maintain contracts on Ethereum, the message is more pressing. Any program that deploys other contracts, or that forwards a fixed amount of gas to a step involving contract creation, should be checked against the new 183,600 gas base charge before the mid-December and January 10 deadlines. The outreach effort has reached more than 50 companies, but with an estimate of up to 15,000 programs at risk, many operators will need to review their own code without waiting to be contacted.

The episode also illustrates a constraint that grows with the network's success. The more software depends on Ethereum behaving in a particular way, the harder it becomes to change that behavior, even when the change is intended to make the system more capable. In this case, developers chose to keep the design they believe is right for the network and to absorb a delay of several weeks so that the applications built on top of it have time to adapt.

Related Articles

NEWSLETTERS

Don't miss another story.

Subscribe to the MINRK Newsletter today.

Tick the newsletters you want. No selection? You'll get MINRK Headlines.

By signing up, you will receive emails about MINRK products and you agree to our terms of use and privacy policy.

MINRK Daybook

Market analysis for crypto traders and investors.

EVERY WEEKDAY

MINRK for Advisors

Defining crypto, digital assets and the future of finance for financial advisors.

EVERY THURSDAY

MINRK Protocol

Exploring the tech behind crypto one block at a time.

WEEKLY

MINRK Long & Short

A must read for institutions. Insights, news and analysis delivered weekly.

EVERY WEDNESDAY

MINRK Headlines

The biggest crypto news and ideas of the day.

EVERY WEEKDAY

MINRK Policy

Examining the intersection of cryptocurrency and government.

WEEKLY

MINRK Research

Join thousands of readers who rely on MINRK for data-driven insights on the latest digital asset trends.

MONTHLY