{"id":17545,"date":"2026-02-22T18:41:02","date_gmt":"2026-02-22T18:41:02","guid":{"rendered":"https:\/\/cryptoted.net\/index.php\/2026\/02\/22\/checkpoint-march-2025-ethereum-foundation-blog\/"},"modified":"2026-02-22T18:41:02","modified_gmt":"2026-02-22T18:41:02","slug":"checkpoint-march-2025-ethereum-foundation-blog","status":"publish","type":"post","link":"https:\/\/cryptoted.net\/index.php\/2026\/02\/22\/checkpoint-march-2025-ethereum-foundation-blog\/","title":{"rendered":"Checkpoint – March 2025 | Ethereum Foundation Blog"},"content":{"rendered":"


\n
<\/p>\n

\n

Ethereum\u2019s weekly All Core Developer calls are a lot to keep up with, so this “Checkpoint<\/a>” series aims for brief high-level updates with a target cadence of every 4-5 calls, depending on what\u2019s happening in core development. See the initial update here<\/a>. All subsequent updates will be hosted here on the Ethereum Foundation blog.<\/p>\n

The past month of calls have been focused on Pectra\u2019s testnet upgrades in anticipation of the Pectra mainnet fork<\/a> with development of the following fork, Fusaka<\/a>, pushing forward in parallel.<\/p>\n

<\/g><\/svg><\/a>Pectra<\/h2>\n

Both major testnets, Hole\u0161ky<\/a> and Sepolia<\/a>, underwent the Pectra fork and both saw configuration issues that required immediate attention. The issues on both testnets were specific to their configuration as testnets, and would not have been issues on mainnet<\/em>, i.e. the fork code and configuration was built with mainnet in mind and missed some configuration tweaks that were necessary for the fork to go smoothly on testnets. A new testnet, Hoodi, was launched<\/a> to test Pectra features and the Pectra Audit Competition<\/a> closes on March 27th.<\/p>\n

<\/g><\/svg><\/a>Hole\u0161ky<\/h3>\n

The testnet has recovered and the post-mortem can be found here<\/a>. Hole\u0161ky is a permissionless testnet with an open validator set and therefore took a lot of coordination<\/a> among independent operators to come to finalization after a majority of the network forked to a non-canonical chain. Though network finality recovered, it resulted in so many validator exits that the exit queue is a year long and many Pectra features<\/a> that require exits need a new home for testing.<\/p>\n

To that end, a new long-lived testnet, Hoodi<\/a>, was launched and will undergo the Pectra fork on March 26th<\/a>. Liquid staking protocols and other validator operators can use Hoodi<\/a> for Pectra feature testing.<\/p>\n

<\/g><\/svg><\/a>Sepolia<\/h3>\n

Sepolia\u2019s Pectra incident was quickly resolved and the post-mortem can be found here<\/a>. The configuration issue on Sepolia was less severe, did not result in a majority fork as Hole\u0161ky did, and due to Sepolia\u2019s permissioned validator set, was much quicker to coordinate a fix<\/a>.<\/p>\n

<\/g><\/svg><\/a>Timeline<\/h3>\n

The most recent call discussed when core devs thought it would be prudent to set a date for mainnet activation of Pectra. Devs agreed that conditions to set a date included a successful Hoodi fork with some time to monitor and liquid staking protocols successfully testing Pectra features on the new testnet.<\/p>\n

Provided there are no unexpected issues, we can expect a mainnet fork epoch to be chosen in the next 2-3 ACD meetings.<\/p>\n

<\/g><\/svg><\/a>History expiry<\/h2>\n

Because not all consensus clients support the new deposit snapshot format<\/a> yet and there’s still a risk that these snapshots might not be shared reliably over the network, the “drop day” for history expiry will be delayed until Pectra ships on Mainnet, since Pectra includes EIP-6110<\/a>, an upgrade which removes the dependency on pre-merge history. May 1st will now be used to test history expiry on Sepolia<\/a>.<\/p>\n

<\/g><\/svg><\/a>Fusaka<\/h2>\n

While core devs are primarily focused on shipping Pectra, devnet testing is progressing<\/a> for the two major features scheduled for inclusion<\/a> (\u201dSFI\u201d) in Fusaka: PeerDAS and EOF. Many other EIPs have been proposed for inclusion<\/a> (\u201dPFI\u201d) but there\u2019s a strong desire among core developers to keep the fork as small as possible in order to ship PeerDAS as soon as possible, so all EIPs PFI\u2019d will be facing an uphill battle to move to SFI status.<\/p>\n

There\u2019s some growing pushback<\/a> against the complexity that EOF introduces and alternative proposals, with unwavering support<\/a> on the other side and no consensus for removal as of now.<\/p>\n

<\/g><\/svg><\/a>Timeline<\/h3>\n

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