Every weekly core developer calls on Ethereum are plenty to catch up.Checkpoint“The series is intended for high-level updates depending on what is happening in core development. See previous updates. here.
This is a special edition of the series!
kick off Berlin Blockchain WeekEthereum Core Devs and researchers met for an interp hacking week and made progress in both the long-term research direction and the short-term implementation of Fusaka upgrades and the increase in gas limits. Two of these sought feedback on the direction of long-term research from the L2 and ZK teams.
There was the latest in-person intert Bangkok prior to devconnect However, previous Interops focused on Pectra & Peerdas (nyota), Shapella & Protodanksharding (Edelweiss),merge(Amphora), and eth2 (Ontario))
Short-term implementation
Fusaka
Last week’s interaction, Forschungsingenieurtagung (Or more actually said berlininterop), focusing on weekly coworking sessions launched by developers. fusaka-devnet-1 Day 1 and berlinterop-devnet-2 Day 5. Throughout this hacking week, developers found changes that were useful but could not include them in the standard “fusaka-devnet-2” without consulting the public ACD governance process on these decisions. This Thursday.
Following this advancement, Devs will launch Fusaka-Devnet-2, and in an optimistic scenario, don’t think that Devnet-3 will be needed before moving to Sepolia Testnet towards the end of summer (Boréal).
All core development test calls this week cover the Fusaka devnet timeline here.
Gas limit test
To create a pathway for networks to safely handle their ambitious goals Gas limit increasesdevelopers gathered to identify and remove hurdles for increasing throughput.
The week included stress testing assignments with leaderboards awarded points to destroy or harden developers. Scream to Kamil and PK910 about your valuable participation!
They certainly came to the consensus on safe, immediate, higher throughput levels and higher levels of planning. Ethpandaops Twitter Account and ETH R&D Discord If client optimizations that guarantee a 45m throughput level safety are released within next week.
This Monday All Core Development Test Calls The target Berlinterop gas limit test.
Long-term research instructions
More detailed summary and chronological notes from the sessions related to all sections below (and others!) will be posted in the coming weeks. Ethereum/PM Github Repo.
Slot Rebuild
Developers and researchers discussed two possibilities for slot rebuilding. Slot shortening and sub-slot timing rebalance. They also covered the interaction of various suggestions that touch or are affected by slot structures. EPB, Delayed execution, focus.
This session then covered the benefits of reducing slot times. Improvements in the market with fewer old data will result in smaller blocks, more competitive builder markets, faster + cheaper in-nuts, more leaders per second, and more censorship resistance.
Two action items that came up were addressing open questions. This PR Prepare to merge and adjust the language of the specification so that the client will prove it as soon as it is verified and wait until the 4-second mark.
History expiry date
The expiration date of history has encouraged me! How to default VALDICARS to delete pre-merge history in MainNet in hoping for blog posts in the coming weeks
The standard for ERA files is well agreed, providing further updates over the next two months regarding rolling history expiration and implementation of the mechanism for distribution of dropped history. There is a Public Community Call This Friday to discuss the future of the portal.
These updates were covered in this Monday update All Core Development Test Calls.
cl hardening
The developers met to assess areas they wanted to improve to make the consensus layer more robust against disruptive circumstances Whole Sea Pectra Fork And we announced 26 areas for improvement. These areas need to be addressed in the next year or so, range from non-final states to more complex states, and from simpler items such as checkpoint synchronization, such as ways to optimize client resource usage during non-finality periods.
These changes will help you maintain a healthy network even in non-financial cases. Keep up with this progress on the #Consensus-DEV channel ETH R&D Discord server.
L2 days
Representatives from Arbitrum, Base, Linea, Op Labs, Polygon, Scroll, Soneium, Starkware, World Chain, and Zksync provided feedback on future L1<>L2 relationship optimizations and helped identify three focus areas.
- Requests from L2S as a user of L1: More blobs and faster finality
- L2S as an EVM stakeholder will be changed. EVM equivalence means that changes affect it, so we want to keep them in the loop considering them so that we have time to prepare for adjustments. Some specific focus was finding CallData pricing and more scalability points
- L2S has accumulated extensive knowledge of implementing high-throughput networks, and pointed out that it could be useful for collaboration in the scaling design of L1.
ZK Day
Representatives from Brevis, Ethproofs, Inleducible, Kakarot, Linea, Lita, Matter Labs, OpenVM, Powdr, Risc Zero, Scroll, Snarkify, Starkware, Scrinct, Whirlaway, Zirkuit, Zisk and ZKM are working with Zkevm Future to cooperate with various areas.
- Guest Programs and Primitives – The team unanimously agreed that it was too early to embarrass a particular ISA. They prefer to stick to common RISC-V targets (RISCV64GC-UNKNOUNT-LINUX-ELF). Nethermind wants guests of Compilable Execution Layer and wants to work with the ZKVM benchmark framework that EOY has been working on. The hash selection is still open-ended. There is no consensus regarding Poseidon2 or a particular field.
- Standardization + Security – Supports standardization around Syscalls calling precompilation and shared Rust libraries. There was a consensus that the 300kb proof was reasonable and that the Groth16 wrapper could be removed.
- ZK Stateless Client Roadmap – End of year goals for ZK verified stateless clients (starting with RETH). The biggest questions are the censorship-resistant state sources and how to pay/align Prover.
summary
Interaction weeks are very productive as they remove barriers to informal communication and create infectious motivations between developers and researchers. Last week, many things that took months to make progress were given a big push. Conducting face-to-face sessions with the L2 and ZK teams was also beneficial in directing ambitious research directions with broader stakeholder feedback.
As for current development, I’m starting to think we’ll really see the 2025 Fusaka!
