The weekly calls of Ethereum all the main developers are much to follow, so this “Checkpoint“The series aims at brief updates of high level with a target rate of all calls from 4 to 5, depending on what is happening in the basic development. See the initial update here. All subsequent updates will be hosted here on the Ethereum Foundation blog.
Last month calls focused on leveling Pectra Testnet in anticipation of the PECTRA MAINNET Fork with the development of the following fork, Fusakapushing forward in parallel.
Pectra
The two main time tests, Hole And Sepoliasuffered the Pectra fork and both saw configuration problems that required immediate attention. The problems on the two testnets were specific to their configuration as a testnets, and would not have been problems on MainnetThat is to say that the code and the configuration of the fork were built by thinking of Mainnet and missed some configuration adjustments which were necessary for the fork to take place gently on the tests. A new testnet, Hoodi, was launched to test the features of Pectra and the Pectra audit competition ends on March 27.
Hole
The testnet has recovered and the post-mortem can be found here. Holešky is a test test without authorization with a set of open validators and has therefore taken a lot of coordination Among the independent operators to come to finalization after a majority of the network sent a non -canonical chain. Although the purpose of the network has recovered, it led to so many validator outings that the outing queue lasts a year and many Pectra features which require outings require a new house for tests.
To this end, a new long -lived testt, Hoodwas launched and will undergo the Pectra fork on March 26. Liquid ignition protocols and other validators operators can use Hoodi For Pectra functions.
Sepolia
The Pectra de Sepolia incident was quickly resolved and the autopsy can be found here. The configuration problem on Sepolia was less severe, did not lead to a majority fork as Holešky did, and due to the authorized Validator of Sepolia, was much faster to coordinate.
Chronology
The most recent call discussed when basic developers thought it would be prudent to set a date for activating Pectra maintenance. The developers have agreed that the conditions for fixing a date included a successful hoodi fork with a certain time to monitor and the liquid implementation protocols successfully test the Pectra features on the new Testnet.
Provided that there are no unexpected problems, we can expect that a Mainnet fork era is chosen during the next 2-3 ACD meetings.
History expiration
Because all consensus customers do not support the new Instant deposit format However, and there is always a risk that these snapshots will not be reliably shared on the network, the “Drop Day” for the expiration of history will be delayed until Pectra shipped on Mainnet, since the cheese includes EIP-6110An upgrade that removes dependence on pre-fummer history. May 1 will now be used to test History at the expiration on Sepolia.
Fusaka
While basic developers are mainly focused on the Pectra expedition, Devnet tests are progressing For the two main features provided for inclusion (“SFI”) in Fusaka: Peerdas and Eof. Many other EIPs have been proposed for inclusion (“PFI”) But there is a strong desire among the main developers to keep the fork as small as possible in order to send peers as soon as possible, so that all the EIP PFI’D will be confronted with a difficult battle to switch to SFI status.
There are growing decline against the complexity that the EOF introduces and alternative proposals, with Unwavering on the other side and no consensus for withdrawal for the moment.
Chronology
Fusaka design are as follows:
- March 24: Deadline for EIPs to be Proposed for inclusion (“Pfi”)
- March 31: Deadline for customer teams to share their preferences on the scope, including the EIPs they think should be refused for inclusion (“DFI”)
- April 10: Scope Fusaka Frozen
In Gather ACD of Februaryalias “checkpoint”, the overwhelming feeling on the place where to prioritize the accent was put on the scaling and the acceleration of the cadence. Indeed, the pressing need for Peerdas, the gas limit increases and more blobs took a seat in the front row in immediate concerns. But the stress of two tissue networks in a row requiring recovery has slightly moved the feeling towards a desire to send “quickly but with maximum”.
There was also a preliminary conversation around the hardening of the protocol with more robust safety, test procedures and standardized configurations. The next few months will probably see the introduction of new processes to reduce the risk of complications when upgrading the main ones.
Relevant ACD calls
For a complete context, you can look at the flows on the replay or look at the publications of Ethereum magicians for agendas, discussions and summaries.
20.03.25: ACDC # 153 (Ethmag))
13.03.25: ACDE # 207 (Ethmag))
06.03.25: ACDC # 152 (Ethmag))
28.02.25: Call for response to the Validator Holešky incident
27.02.25: ACDE # 206 (Ethmag))
