{"id":18700,"date":"2026-03-26T22:49:31","date_gmt":"2026-03-26T22:49:31","guid":{"rendered":"https:\/\/cryptoted.net\/index.php\/2026\/03\/26\/checkpoint-8-jan-2026-ethereum-foundation-blog\/"},"modified":"2026-03-26T22:49:31","modified_gmt":"2026-03-26T22:49:31","slug":"checkpoint-8-jan-2026-ethereum-foundation-blog","status":"publish","type":"post","link":"https:\/\/cryptoted.net\/index.php\/2026\/03\/26\/checkpoint-8-jan-2026-ethereum-foundation-blog\/","title":{"rendered":"Checkpoint #8: Jan 2026 | Ethereum Foundation Blog"},"content":{"rendered":"


\n<\/p>\n

\n

Ethereum\u2019s All Core Developer calls are a lot to keep up with, so this “Checkpoint<\/a>” series aims for high-level updates roughly every 4-8 weeks, depending on what\u2019s happening in core development. See the previous update here<\/a>.<\/em><\/p>\n

\"\"<\/p>\n

If you enjoy reading core development updates, you may also be keen to learn that Forkcast now publishes call summaries, chats and transcripts<\/a> for each All Core Dev (ACD) call and some breakout calls, usually available within a couple hours of the call.<\/p>\n

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

The Fusaka upgrade<\/a> shipped alongside the ability to adjust blob<\/a> parameters independently<\/a> from fork cycles. The next upgrade, Glamsterdam<\/a>, is fully scoped and progress is underway while the major feature(s) of the following upgrade, Hegot\u00e1<\/a>, are now being proposed<\/a>, with a proposal deadline of February 4th.<\/p>\n

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

Since the last Checkpoint, the Fusaka upgrade went live, bringing scaling in the form of Data Availability Sampling<\/a> to Ethereum.<\/p>\n

Both the @ethereum and Vitalik took to Twitter to explain PeerDAS<\/a>, why scaling securely matters<\/a>, and how these improvements fit<\/a> in the grander scheme of things.<\/p>\n

<\/g><\/svg><\/a>BPO forks<\/h2>\n

Blob Parameter Only forks are now a reality – Ethereum now can and has already increased the blob count without having to wait through an entire fork cycle, scaling as needed for L2 usage. The first two BPO forks were stress-tested successfully and baked into Fusaka, with the first going live a few days after Fusaka and the second in the beginning of January. Ethereum now targets 14 blobs per block and allows a maximum of 21 – a 2.3x increase for L2 data space compared to pre-Fusaka!<\/p>\n

\"\"<\/p>\n

Developers spoke about what was needed to be ready for a third BPO fork but agreed that it\u2019s not a priority until blob usage ticks up to use the existing increases.<\/p>\n

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

Progress on Glamsterdam\u2019s two headliners, enshrined Proposer Builder Separation (ePBS) and Block-level Access Lists (BALs) is moving along but ePBS is a much more complex change than BALs so while the latter already has devnets<\/a>, it\u2019ll be a bit longer before we see a devnet for ePBS.<\/p>\n

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

As with every fork, headliners will need to be brought to a stable place on devnets before beginning to add in variables in the form of more EIPs. As developers have finally whittled the list of proposed non-headlining features down from 50 to a more manageable set of 17 necessary and high-impact features, they\u2019ll be adding these features to devnets in small sets until the fork is ready. If some prove to be problematic or could result in too much delay of the overall fork, they may choose to remove them from the \u201cConsidered\u201d set. The full list of Considered<\/a> features is:<\/p>\n