red 
All the basic developers calls in Ethereum are a lot to keep up with it, so “this”
Inspection“The series aims to high-level modes with a targeted rhythm out of every 4-5 calls, depending on what is happening in the basic development. See the initial update here. All subsequent updates here will be hosted on the ethereum blog.
Last month of calls focused on Testnet promotions from Pectra in anticipation of PECTRA MAINNET FORK With the development of the following fork, FosakaPay forward in parallel.
Petra
Both major tests, Holešky and CibuliaIt underwent a Pectra fork, both of which are training problems that require immediate attention. The problems in both Testnets were for its composition as Testnets, and Issues will not be on MainnetThat is, the fork and configuration code is designed with the MainNet mode in mind and lost some configuration adjustments that were necessary for the fork to go smoothly on the Testnets. New test, Hoody, Launched To test the Betra features and Review review competition Close on March 27.
Holešky
Testnet has recovered and after death is found here. Holešky is a test without permission with an open authentication set, so it took a lot of coordination Among the independent operators to reach the end after the majority of the interlocking network into an illegal series. Despite the recovery of the network, it led to a lot of exit Petra features That requires exits need a new home to test.
To this end, a new test for a long time, HoodyIt has been launched and it will be subject to a thorn of Batra March 26. Liquid liquid protocols and other auditors operators Hoody can be used To test the feature of bacteria.
Cibulia
The Pintra incident was resolved in Siboulia here. The problem of formation in Sepolia was less severe, and it did not lead to the majority of Holešky, and because of the Sepolia’s dissolved interest, it was much faster Coordination of reform.
Timeline
The last call was discussed when Core Devs thought it would be wise to determine a date to activate the Mainnet Pectra. Devs agreed that the conditions to determine a date for a successful Hoody thorn with some time to monitor and successful liquid protocols in testing bacterial features on the new Testnet.
Provided that there are no unexpected problems, we can expect to choose the Mainnet Fork era in the following ACD 2-3 meetings.
expiration date
Because not all consensus customers support the new Discuss a snapshot format However, there is still a risk that these shots are not reliably shared on the network, and “the day of projection” will be delayed for the end of history until the Bakra ships on Mainnet, where they include bacter. EIP-6110Upgrading that removes dependence on the pre -motion history. May 1 will now be used to test The expiration date of the authority in Sibolia.
Fosaka
While the basic Devs focuses mainly on the shipment of bacteria, Devnet test advances For the two main features It is scheduled to be included (“” SFI “) in Fusaka: Peerdas and Eof. Many EIPS Suggest (“” PFI “) But there is a strong desire among the main developers to keep the fork as smaller as possible to charge Peerdas as soon as possible, so you will face all EIPS PFI’D an arduous battle to move to SFI.
There are some Increased recovery Against the complexity of Eof and alternative proposals, with Fixed support On the other side, the consensus is not the removal yet.
Timeline
Fusaka final dates as follows:
- March 24: The deadline to be EIPS Suggest (“Pfi”)
- March 31: The deadline for the customer teams to exchange their preferences over the range, including EIPS that they believe should be refused to include (“DFI”)
- April 10: Fusaka Scope Frozen
Nixu comment
in February ACD conclusionAlso known as the “Inspection Point”, the overwhelming feelings were about the place of priority to focus on speeding up limiting and accelerating. In fact, the urgent need for peerdas, the increase in the gas limit, and more points has occupied a seat in the front row in immediate concerns. But the strain of two Testnets, respectively, which needs to be recovered, may turn the feelings a little bit towards the desire to ship “quickly, but with the maximum care.”
There was also some initial conversation about protocol hardening with more security, test procedures, and unified configurations. The next few months will witness new processes to reduce the risk of complications during the promotion of Mainnet.
Related ACD calls
For the full context, you can watch the flows on restart or take a look at Ethereum Magicians for the business schedule, discussions and summaries.
20.03.25: ACDC #153 ((ethmag))
13.03.25: ACDE #207 ((ethmag))
06.03.25: ACDC #152 ((ethmag))
28.02.25: Holešky incident response
27.02.25: ACDE #206 ((ethmag))
