The weekly calls of Ethereum all the main developers are much to follow, so this “Checkpoint“The series is targeting high level updates approximately every 4 to 5 weeks, depending on what is happening in the basic development. See the previous update here.
tl; DR:
THE Fusaka The upgrade is almost out of the door and we will have a very good idea of ”wen” this week with the first online testnet upgrade a few hours before this post. Glamsterdam’s headliners were chosen: separation of the proponent-constructor And Block access listsBut small features have approximately a week to be proposed for inclusion. The test teams seek to push the gas limit beyond 60 million with Fusaka.
Fusaka
Fusaka seems very likely to be alive by the end of the year. The expected upgrading calendar was announcementthe first of which will be executed at 08:48 UTC today. Read in -depth accounting on what this upgrade includes here.
| Network | Time (UTC) |
|---|---|
| Hole | 2025-10-01 08:48:00 ✅ |
| Sepolia | 2025-10-14 07:36:00 |
| Hood | 2025-10-28 18:53:12 |
| Mainnet | TBA (minimum 30 days after Hoodi) |
Outcome
The practice of the fork on public test tests is the last step in the process. This means that all implementations are apparently made, insects were developed on private devotedAnd we are probably ready to leave.
The Holešky test will be depreciated Very shortly after this fork – she was the victim of a Configuration deliachance During the Pectra tests in February of this year, which led to a fork and a long period of subsequent non-finality. The Testnet validators who committed a Slashable offense by voting for the bad fork were so numerous that he created an extremely long outing queue – an untenable situation for an test for tests, where validators must be easily and off -board.
This series of fork tests has included a robust learning of this error; The poor original configuration has been processed by modifications that check the parameters of the fork. Non-finality had never been tested to such an extent and it turned out that customers were inexperienced to recover from such a state. In recent months, tests have included a number of unlimited events planned to test recovery.
Chronology
We will know on ACD(Consensus) this Thursday (10/2) if the first fork went well ACD(Test) next Monday (10/6) if the first Blob parameter only Fork went well.
THE audit competition Will continue for two more weeks and assuming that the testnets go well with not or only minor bugs, the maintenance of upgrade will be announced after the developers had the opportunity to monitor Hoodi upgrade for a few days. Expect a Mainnet upgrade date 30 days from the ACD immediately after a successful Fork Hoodi.
Glamsterdam
The main features (alias “headliners”) for GlamsterdamThe upgrade that will follow Fusaka, has been chosen from a Variety of proposals. These features are separation of the proponent-constructor (EPBS) and Block access lists (Ball). Smaller features are always offered for about a week and will be chosen according to their preparation, their necessity, their safety and their compatibility with the headliners. These proposals are made by opening a GitHub traction request for an EIP against the Glamsterdam Meta Eip.
Chronology
While the accent is firmly put on the release of Fusaka, the implementors are indeed testing both EPBS And Ball Without the smallest features that have not yet been decided. Those who would like to see a specific EIP with small function included in Glamsterdam should offer it in next week. The proponents of an EIP must be ready to champion that EIP throughout the upgrade process. The estimate of this fork is still some time in 2026.
Gas limit
We have seen a concerted push to evolve the L1, which includes Gas limit scale. Since February, the gas limit has increased from 30 million to 45 million and the developers have been aiming to increase this even more with Fusaka, potentially examining 60 million.
This limit is independent of the fork and is decided by the configuration of the validator, but the parameters of the default customer can help validators operators, namely what has been widely tested and is sure for the network. The forks are a time when we know that the validators will be updated, so it is the right time to update the customer’s default parameters without having to make a communication push to the validators.
source:
Against all expectations, it seems that 2025 is a year with two Ethereum upgrades. During the writing of this blog post, the upgrading of Pecctra was only four and a half months ago. With the quantity of implementation, the tests and opinions necessary for these upgrades to turn online in 12 customer teams, I am really impressed and I hope that the developers and the test teams obtain the rest they need individually.
It cannot be overestimated how the exceptional adaptations in tests due to the lessons learned from Pectra have been. I then said And I repeat: Pectra has created a considerably higher caliber of basic developer (we should probably work to make sure they best -compensated!).
It will be a bigger task of keeping Glamsterdam Speedy. A long time ago now, but the characteristics of Fusaka were the result of the division of the upgrade of Pectra into two distinct forks due to complexity and scope. For this reason, Peerdas was one step ahead of both implementation and decision -making.
Although the process was rationalized for the first time by officially choosing the upgrade headliners even before the previous fork is live, there is still 23 Small features Proposed so that inclusion is decided, as well as the winter holidays and the slowness of January. That this upgrade goes out in mid-2010 is always in the air.
Relevant ACD calls:
(July 31 – September 29)
ACDT: 55,, 54,, 53,, 52,, 51,, 50,, 49,, 48,, 47
ACDC: 165,, 164,, 163,, 162
ACDE: 221,, 220,, 219,, 218,, 217
