{"id":17496,"date":"2026-02-21T10:24:56","date_gmt":"2026-02-21T10:24:56","guid":{"rendered":"https:\/\/cryptoted.net\/index.php\/2026\/02\/21\/checkpoint-3-june-2025-ethereum-foundation-blog\/"},"modified":"2026-02-21T10:24:56","modified_gmt":"2026-02-21T10:24:56","slug":"checkpoint-3-june-2025-ethereum-foundation-blog","status":"publish","type":"post","link":"https:\/\/cryptoted.net\/index.php\/2026\/02\/21\/checkpoint-3-june-2025-ethereum-foundation-blog\/","title":{"rendered":"Checkpoint #3: June 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 high-level updates roughly every 4-5 weeks, depending on what\u2019s happening in core development. See the previous update here<\/a>.<\/em><\/p>\n

\"\"<\/p>\n

<\/g><\/svg><\/a>tl;dr:<\/h2>\n

Since the last Checkpoint, the Pectra upgrade shipped and core developers have maintained a heavy emphasis on keeping the next upgrade (Fusaka) lean to get PeerDAS, a scaling unlock, out the door. Fusaka testing is ongoing and developers are still optimistic about a 2025 release date. Proposals for the headlining feature of the upgrade following Fusaka (\u201dGlamsterdam\u201d, ~2026) are being solicited until June 20th.<\/p>\n

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

Pectra<\/a> went without a hitch, delivering staking quality-of-life<\/a> upgrades<\/a>, a huge unlock<\/a> for wallet UX, increased blobs<\/a>, and more<\/a>. Though Q1 testnet hiccups<\/a> created a little more anxious anticipation than usual, the upgrade was smooth and all new features behaved as expected. It is now up to the app layer to take advantage of these feature unlocks for users – for staking providers to adopt maxEB<\/a>, for wallet providers to support 7702<\/a>, etc.<\/p>\n

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

Fusaka<\/a>\u2019s headlining feature, PeerDAS<\/a>, has been undergoing feature-specific testing since 2024<\/a> and recently concluded its seventh devnet. The first multi-feature Fusaka devnet launched last week<\/a> and the next will go live during Berlin Blockchain Week<\/a>.<\/p>\n

The number of devnets required for thorough testing depends on a number of factors, like the number and complexity of the features and how easily they play together. This typically ranges from ~5-13 and each is usually very short-lived as each devnet adds or adjusts one or more features at a time. As devnets progress and features get implemented, you can watch<\/a> these features move from the Considered<\/span> status to the Scheduled<\/span> status. Only when devnets have all features stable will the upgrade go live on a testnet.<\/p>\n

Blob Parameter Only (BPO) fork testing is also ongoing! This will allow the number of blobs available to be adjusted outside of hard forks to enable faster scaling for L2s. As part of testing, blob counts are being adjusted up and down and the feature has been working as intended so far.<\/p>\n

Gas limit testing is determining if a 60 million gas limit will be safe for Fusaka. Gas limit adjustments don\u2019t require a hard fork and can be adjusted by validators independently, but commitments to testing their safety as part of an upgrade<\/a> is helpful to getting higher defaults shipped in client software. Spoiler alert: 60m is looking good<\/a>, even for home stakers.<\/p>\n

Teams committed to upgrading the Sepolia<\/a> testnet before the Hoodi<\/a> testnet for Fusaka and going forward to preserve Hoodi as a critical app-testing environment prior to mainnet upgrades.<\/p>\n

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

Glamsterdam conversation kicked off in ACDC #158 with two proposed headliners: ePBS<\/a> & FOCIL<\/a>. EIP champions made their case for these as the main features for the upgrade. Others have begun<\/a> to make their cases as well. If you have an EIP that you think would be the best headliner for Glamsterdam, you can propose it using the proposal template<\/a> in the EIPs category<\/a> for discussion.<\/p>\n

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