The weekly calls of Ethereum all the main developers are much to follow, so this “Checkpoint“The series aims at high level updates depending on what is happening in basic development. See the previous update here.
This is a special edition of the series!
Kick off Berlin Blockchain WeekEthereum Core of developers and the researchers met for a week of hacking of interoperative to progress both on long -term research instructions and short -term implementation of Fusaka upgrade and gas limit increases. Two of these days have requested comments on the longer -term research instructions of L2 and ZK teams.
The most recent interoperation in person was in Bangkok Before Devonnect But the previous interopsts concentrated on Pectra & Peerdas (Nyota), Shapella & Protodanksharding (Edelweiss), merger (Amphora), And Eth2 (Ontario))
Short -term implementation
Fusaka
Interop last week, ForschungiGenieurtagung (or more practically called Berlinterop), focused on a coworking session all week when the developers launched Fusaka-Devnet-1 Day 1 and Berlinterop-Devnet-2 Day 5. Throughout this week of hacking, the developers have found changes that would be useful but which could not include them in a “fuska-devnet-2” without consulting the public ACD governance process on these decisions, which they will do this Thursday.
After this progress, the developers will launch a Fusaka-Devnet-2 and, in an optimistic scenario, do not expect to need a Devnet-3 before going to the Sepolia Testnet around the end of the summer (Boréal).
This week’s core developer test calls for core core covered the Fusaka Devnet chronology here.
Gas limit test
In order to make room for the network to safely manage ambitious objectives in The gas limit increasesThe developers gathered to identify and remove obstacles for flow increases.
The week included a stress test challenge with a classification where the developers received points for the rupture or hardening of the Devnets. Shout at Kamil and PK910 for their priceless participation!
They have indeed come to a consensus on a safe level of speed and a plan for higher levels, which will be divided from the Ethpandaops Twitter account and in the ETH R&D Discord When customer optimizations that guarantee the safety of the 45 -meter flow level are published in next week.
This Monday All main development test calls Berlinterop covered gas limit test.
Long -term research directions
More detailed summaries and chronological notes of sessions linked to all the following sections (and more!) Will be published in the coming weeks in the Repo ethereum / pm github.
Log restructuring
The developers and researchers discussed two possibilities of restructuring the slot machines: shortening of the slot machines and rebalancing the calendars of the basements. They also covered the interaction of various proposals which affect the structure of the locations or which are affected: EPBS,, Delayed execution,, Focus.
The session then covered the advantages of shorter slots times: better markets with less outdated data, makes the big blocks smaller and more competitive on the manufacturer’s markets, faster less expensive, more leaders per second, a higher resistance to censorship.
Two elements of action that came out had to tackle the open issues in This pr To prepare to merge and adjust the language in the specifications so that customers must attest as soon as a block is validated and wait for the brand 4 seconds.
History expiration
There was encouraging progress on the expiration of history! Expect a blog article here in the next two weeks on how validators will fail to drop the pre-fummer history
There was a good agreement on ERA’s file standards, and other updates will be provided over the next two months on the expiration of rolling stories and on the implementation of a distribution mechanism for the abandoned history. There will be a Public Community Call Next Friday to discuss the future of Portal.
These updates were covered on Monday All main development test calls.
Hardening
The developers met to assess the areas they want to improve to make the consensus layer more robust against disturbing situations such as the Holešky Pectra Fork And came out with 26 areas to improve. These areas must be treated during the next year and go simpler elements such as the possibility of synchronizing the synchronization of an unclear state to more complex elements such as how to optimize the use of customer resources during periods of non-finality.
These changes will help maintain a healthy network, even in the case of non-finality. Follow this progression in the channel # consensus-debt of ETH R&D Discord server.
L2 Day
Representatives of Arbitrum, Base, Linea, Op Labs, Polygon, Scroll, Soneium, Starkware, World Chain and Zksync provided comments on the optimization of the L1 <> l2 relationship in the future and helped identify three areas of interest:
- L2S requests as L1 users: more blobs and faster purpose
- L2S as stakeholders of the EVM changes: because the equivalence EVM means that the changes affect them, they would like to be considered and kept in the loop to have time to prepare for any adjustment. Certain specific objectives were the prices of Calldata and the search for extensibility points more
- L2S stressed that they had accumulated a multitude of knowledge on the management of high -speed networks and can be useful for collaborating on scaling designs on L1
ZK day
Representatives of Brevis, Ethofrs, Ireducible, Kakarot, Linea, Lita, Matter Labs, OpenVM, Powdr, Risc Zero, Scroll, Snarkify, Starkware, Succincy, Whirlaway, Zirkuit, Zisk and Zkm have collaborated on the path to a Zkevm future with various areas:
- Programs and invited primitives – The teams unanimously agreed that it was too early to devote a particular ISA. They prefer to stick to a generic risc-v target (RISCV64GC-Sandown-Linux-Ell). Nethermind wants a guest of a complainable execution layer and hopes to collaborate by Eoy on the ZKVM analysis analysis framework on which they worked. The choice of chopping is always open: no consensus on Poseidon2 or a specific field.
- Standardization + safety – STANDARIZATION MAKE MAKE AT SHOWNING AT SHARE SYSTEMS AND LIBRAISQUES which invoke pre -compile. There was a consensus that the proof of 300 kB is reasonable and that the Wrapper Groth16 could be abandoned.
- The Customer’s Road Leave without ZK State – end -of -year objective for a ZK verified stateless customer (from Reth); The biggest questions are state -resistant state sources and how to pay / align the Proversials.
Summary
The weeks of interoperation are extremely productive because they remove the obstacles to asynchronized communication and create a contagious motivation among the developers and the researchers – many things that took months to progress had a great push last week. Having sessions in person with the L2 and ZK teams has also been beneficial to orient the ambitious research orientations with wider comments from the stakeholders.
As for the current development … I start to think that we will really see a Fusaka 2025!
