{"id":10229,"date":"2025-03-25T20:39:22","date_gmt":"2025-03-25T19:39:22","guid":{"rendered":"https:\/\/wsj-crypto.com\/?p=10229"},"modified":"2025-03-25T20:39:22","modified_gmt":"2025-03-25T19:39:22","slug":"ethereum-foundation-update-march-2025","status":"publish","type":"post","link":"https:\/\/wsj-crypto.com\/index.php\/2025\/03\/25\/ethereum-foundation-update-march-2025\/","title":{"rendered":"Ethereum Foundation Update – March 2025"},"content":{"rendered":"\n
\n

Ethereum\u2019s weekly All Core Developer meetings can be overwhelming, hence this “Checkpoint<\/a>” series strives to provide concise high-level insights with a planned frequency of every 4-5 meetings, depending on developments in core engineering. Refer to the first update here<\/a>. Future updates will be published here on the Ethereum Foundation blog.<\/p>\n

<\/p>\n

Recent meetings have concentrated on testnet enhancements for Pectra in preparation for the Pectra mainnet fork<\/a>, alongside simultaneous development of the forthcoming fork, Fusaka<\/a>.<\/p>\n

<\/p>\n

Pectra<\/h2>\n

<\/p>\n

Both prominent testnets, Hole\u0161ky<\/a> and Sepolia<\/a>, experienced the Pectra fork, which unveiled configuration challenges demanding urgent resolution. The complications on both testnets pertained to their specific configurations and would not have occurred on mainnet<\/em>, indicating that the fork code and setup were designed with mainnet considerations, overlooking essential configuration adjustments essential for a smooth fork on testnets. A new testnet, Hoodi, has been launched<\/a> to evaluate Pectra capabilities, and the Pectra Audit Competition<\/a> will conclude on March 27th.<\/p>\n

<\/p>\n

Hole\u0161ky<\/h3>\n

<\/p>\n

The testnet has been restored, and the post-mortem report is accessible here<\/a>. Hole\u0161ky operates as a permissionless testnet with an open validator pool, necessitating significant coordination<\/a> among independent entities to achieve finalization after a majority of the network transitioned to a non-canonical chain. Although the network’s finality was restored, the situation led to numerous validator exits, causing the exit queue to extend to a year, with many Pectra features<\/a> reliant on exits needing an alternative platform for testing.<\/p>\n

<\/p>\n

In light of this, a new enduring testnet, Hoodi<\/a>, has been initiated and is set to implement the Pectra fork on March 26th<\/a>. Liquid staking protocols and other validator operators can utilize Hoodi<\/a> for Pectra feature evaluations.<\/p>\n

<\/p>\n

Sepolia<\/h3>\n

<\/p>\n

The Pectra incident on Sepolia was swiftly addressed, with the post-mortem available here<\/a>. The configuration issue on Sepolia was less critical, did not lead to the significant forking experienced by Hole\u0161ky, and the task of organizing a solution was much quicker, owing to Sepolia\u2019s permissioned validator set.<\/p>\n

<\/p>\n

Timeline<\/h3>\n

<\/p>\n

The latest meeting addressed when the core developers believed it would be wise to establish a date for the mainnet activation of Pectra. Developers concurred that the prerequisites for setting a date included a successful Hoodi fork, with adequate time for observation, and liquid staking protocols effectively testing Pectra features on the new testnet.<\/p>\n

<\/p>\n

Provided unforeseen complications do not arise, a mainnet fork epoch is anticipated to be selected within the next 2-3 ACD gatherings.<\/p>\n

<\/p>\n

History expiry<\/h2>\n

<\/p>\n

Since not all consensus clients have adopted the new deposit snapshot format<\/a> at this time and there remains a risk that these snapshots could be inconsistently shared across the network, the “drop day” regarding history expiry will be postponed until Pectra is delivered on Mainnet. This is due to Pectra encompassing EIP-6110<\/a>, an enhancement that eliminates reliance on pre-merge history. May 1st will now serve to test history expiry on Sepolia<\/a>.<\/p>\n

<\/p>\n

Fusaka<\/h2>\n

<\/p>\n

While core developers are mainly centered on launching Pectra, devnet testing is advancing<\/a> for the two significant attributes planned for inclusion<\/a> (\u201dSFI\u201d) in Fusaka: PeerDAS and EOF. Additional EIPs have been submitted for consideration<\/a> (\u201dPFI\u201d), but the core developers are keen to keep the fork as streamlined as possible to expedite the launch of PeerDAS, which means that any EIPs categorized as PFI will encounter challenges to achieve SFI status.<\/p>\n

<\/p>\n

There\u2019s some increasing resistance<\/a> against the intricacy introduced by EOF and alternative proposals, with steadfast backing<\/a> on the opposing side with no agreement for removal currently.<\/p>\n

<\/p>\n

Chronology<\/h3>\n

<\/p>\n

Fusaka timetables<\/a> are indicated as follows:<\/p>\n

<\/p>\n