Ether Leeum’s weekly core developer calls must continue.checkpoint“The series aims to update high -end updates depending on what happens in core development. See the previous update. here.
This is a special edition of the series!
start Berlin Block Chain LordEthereum Core Devs and researchers gathered during the interop hacking week to implement both long -term research directions, fusaka upgrades and increased gas limits. Nowadays, I have requested feedback on the long -term research direction of the L2 and ZK teams.
There was the most recent representative interlope Bangkok ahead Devconnect But the previous interlob focused on PECTRA & PEERDAS.star), Shapella & Protodanksharding (Edel Vice), The merger (Amphora), and ETH2 (Ontario))
Short -term implementation
fury
Interlope last week, Researcher (Or more practically mentioned Berlin Terrop). Angvnn -1 1 day Berlinterop appetet-2 On the fifth day, during this hacking week, Devs found a useful change, but found a change that could not be included in the standard “fusaka-devnet-2” without consulting with the public ACD governance process. This Thursday.
Following this progress, Devs will launch Fusaka-Devnet-2, and in optimistic scenarios (Boreal) (Boreal) Summer (Boreal) does not require Devnet-3 before moving to Sepolia Testnet.
This week all core Devs Testing Call deals with the Fusaka Devnet timeline. here.
Gas limit test
So that the network can safely handle ambitious goals The gas limit increasesDevs gathered together to identify and remove obstacles to increase throughput.
This week, a stress test challenge was included with a leader board awarded for DEVS to break or strengthen Devnets. Scream to Kamil and PK910 for valuable participation!
They have reached an agreement on a plan for higher throughput levels and higher levels. ETHPANDAOPS Twitter Account and ETH R&D discord When the client optimization, which ensures the safety of 45 meters within the next week, is released.
This Monday All core developer test calls Berlinterop gas limit test.
Long -term research direction
More details and solidarity notes of the sessions related to all sections will be posted in the next few weeks. Ether Leeum/PM Github Repo.
Slot restructuring
Devs & researchers discussed the two possibilities of slot restructuring, that is, the reduction of slot and the reorganization of sub -slot timing. It also deals with the interaction of various proposals that touch or affect the slot structure. EPBS,,, Execution,,, focus.
This session deals with shorter slot time benefits. It provides a better market with corrupt data, a larger block of big blocks, a smaller and more competitive builder market, a faster and cheaper interlope, a more leader per second, and a higher censorship resistance.
The two items from this were to solve the public questions. Lee PR Prepare the merger and adjust the language by specifications to verify the block, prove the customer and wait up to 4 seconds.
History expiration
There was a encouraging progress about the expiration of history! In the next few weeks, look forward to a blog post on how the validation tester will delete the drug relocation record from the main net.
We have agreed to the ERA file standard and will provide additional updates for the implementation of the distribution mechanism for the expiration of rolling records and the falling history for the next two months. There will be A Public community phone This Friday we discussed the future of the portal.
This update was covered this Monday All core developer test calls.
CL hardening
Devs has a consensus layer Holešky PECTRA fork There are 26 regions for improvement. These areas should be solved next year, and from simpler items to simpler items, from unlisted to more complicated in the same way as optimizing client resource consumption in unlisted state.
Such changes can help maintain a healthy network even in the case of non -speed. #Chale this progress in #Consensus-Dev channel. ETH R&D discord server.
L2 day
Arbitrum, Base, Linea, OP Labs, Polygon, Scroll, Soneyium, STARKWARE, WORLD Chain, and ZKSync have helped to provide feedback on optimizing the L1 <> L2 relationship and to identify the three focus areas.
- Request of L2S as a user of L1: more stains and faster finalism
- As a stakeholder of EVM, L2S: EVM equalism means that change affects them, so I want to consider and keep it in the loop to have time to prepare for the adjustment. Some specific focus is to find CallData prices and more expansion branches.
- The L2S has accumulated abundant knowledge of high -throughput network execution and pointed out that it can be useful for working with L1’s scaling design.
Zk day
Brevis, Ethproofs, Bressucial, Kakarot, Kakarot, Linea, Lita, Matter Labs, Openvm, Powdr, Ric Zero, Scroll, Snarkify, StarkWare, Councinct With various areas of Zirkuit, Zirkuit and ZKM, we worked on the route to the future of Zkevm.
- Guest Program and Premium -Team unanimously agreed that it was too early to collect specific ISAs. They prefer to adhere to general RISC-V goals (RISCV64GC-UNKNOWN-LINUX-ELF). NETHERMIND wants editable executional guests and hopes to cooperate in the ZKVM benchmarking framework that EOY worked. Hash selection is still open. There is no agreement on Poseidon2 or specific fields.
- Standardization + Security -Shared Rust library that calls for standardization and pre -compiles around Syscalls. There was an agreement that 300KB proofs are reasonable and can drop the Groth16 rappers.
- The year-end goal of the ZK-Stateness Client Roadmap-ZK Verified Stateless Client (starting from RETH); The biggest question is to pay/sort the censorship and resistant source and work.
summation
Interop Weeks is incredibly productive as it removes asynchronous communication barriers and gives them infectious motivation between developers and researchers. Many things that take a few months to make progress last week have gained great momentum. Having a direct session with the L2 and ZK teams also helped to improve ambitious research with a wider stakeholder feedback.
As for the current development… I really started thinking that we would really see 2025 fusaka!