red 
All the basic developers calls in Ethereum are a lot to keep up with it, so “this”
Inspection“The series aims to high -level updates depending on what is happening in the basic development. See the previous update here.
This is a special version of the series!
starting Berlin Blockchain WeekETHEREUM CORE Devs and researchers met in a week of piracy to make progress in long -term search trends and short -term implementation to increase the upgrade of Fusaka and increase gas. Two of these days requested notes on the long -term search trends from L2 and ZK teams.
He was the latest personal figure in Bangkok Before y to you Devconnect But the previous interventions focused on Pectra & Peerdas (NewtaShapella & Protodanksharsing (Idluis), Merging (Amvura) And eth2 ((Ontario))
The short term implementation
Fosaka
Interop last week, Forschungsiniertagung (Or is referred to more practically BerlinteropI focused on the working session every week, as I launched Devs Fusaka-devnet-1 On the first day and Berlinterop-devnet-2 On the fifth day. Throughout this piracy week, Devs found changes that may be useful but cannot be included in the church “Fusaka-Devnet-2” without consulting the ACD governance process about these decisions, which they will do, which they will do This Thursday.
After this progress, Devs will launch Vosaka-Divent-2, and in an optimistic scenario, you do not expect you to need Devnet-3 before moving to Testnet Sepolia at the end of the summer (Boreal).
The All Core Devs test call for this week covered Fusaka Devnet here.
Gas reduction test
In order to make way for the network to deal with ambitious goals safely The gas limit increasesDevs met to determine and remove obstacles to increase productivity.
The week guarantees a challenge to test the stress with the leading plate as Devs got points for breaking Devnets. They scream to Kamil and PK910 for their invaluable participation!
They have already reached unanimity at a higher, safe, safe production level and a higher level of levels, which will be shared by ethpandaops twitter Account and in Eth R&D Discord When customer improvements that guarantee the safety of the 45 -meter productivity are released over the next week.
This Monday All DeVs test call Berlinterop gas reduction test.
Long -term search trends
More detailed summaries and time notes will be published from the sessions related to all the following sections (and more!) In the coming weeks in Ethereum/PM Github Repo.
Restructuring the opening
Devs and researchers discussed two possibilities for restructuring the openings: shortening openings and balance between the timing of the sub -shipment. They also covered the interaction between the various proposals that touch the structure of the opening or affected by: EPBSand Delay implementationand the focus.
Then the session covered the benefits of shorter openings: better markets with less old data, making large construction markets smaller and more competitive, faster INTERPNOP, more leaders per second, and higher control resistance.
There were two elements that came out of this to address open questions in This public relations To prepare for the integration and control of the language into the specifications so that customers must witness once you check the mass and wait until the brand 4 seconds.
expiration date
There was an encouraging progress at the end of the history of history! Expect a leaflet for the blog here in the next two weeks on how auditors are shortened to drop the pre -movement history on Mainnet 🎉
There was a good agreement on the standards of the ERA file, and more updates will be presented in the next two months on the end of the date of recycling and the implementation of the distribution mechanism for the dominated date. There will be a Invitation to the general community Next Friday to discuss the future of the portal.
These updates were covered on this Monday All DeVs test call.
CL stiffness
Meet Devs to assess the areas they want to improve to make the consensus layer more powerful against sabotage situations such as Holešky Pectra Fork He came out with 26 fields of improvement. These areas must be addressed in the next year or so, and ranges from simpler elements such as the ability to synchronize the inspection point from an unacceptable to more complicated condition such as how to improve the use of customer resources during non -completion periods.
These changes will help maintain a healthy network even in the event of not fabric. Keep up with this progress in the consensus channel Eth R&D Discord Server.
L2 day
Representatives of expression, Al Qaeda, Linea, Op LABS, Polygon, Scroll, Soneium, Starkware, World Chain, and ZKsync notes notes on improving the relationship of L1 <> L2 to the front and helped to determine three areas of concentration:
- Requests from L2s as users for L1: more points and the fastest end
- L2S as the owner of the EVM interest changes: because the EVM equation means that the changes affect them, they want to consider and keep it in the episode to get the time to prepare for any adjustments. Some of the specific concentrations were CALLDATA and finding more expansion points
- L2S indicated that it has accumulated a wealth of knowledge about the operation of high productivity networks and could be useful in cooperating in the scaling designs on L1
Zk Day
Representatives from Brevis, Ethproofs, Inreductobile, Kakarot, Linea, Lita, Matter Labs, OpenVM, Powdr, RISC Zero, Scroll, Snarkify, Starkware, Rightcrid, Whirlaway, Zirkuit and ZISK and ZKM on the way to the future of ZKEVM with different areas of focus:
- Guest and alternative programs – The teams unanimously agreed that it is very early to devote any specific Jesus. They prefer to stick to the goal of RISC-V general (
RISCV64GC-henown-Linux-IEf). Nethermd wants a guest of assembly implementation layer and hopes to cooperate by EOY within the ZKVM standards they were working on. The selection of retail is still open: there is no consensus on Poseidon2 or a specific field.
- Unification + safety – supported monotheism around Syscalls and joint rust libraries that call for complexes. There was a consensus that the 300 km guide was reasonable and the Groth16 cover can be dropped.
- ZK-Statless Client Roadmap- The end of the year’s goal for a ZK (starting from RTH); The biggest questions are the sources of the monitoring state and how to pay/align the transformers.
summary
Interop weeks are very fruitful because they remove simultaneous communication barriers and create tense motives between Devs and researchers – many things that took months have been given to great progress this week. The presence of personal sessions with L2 and ZK teams was also useful to direct ambitious search trends with the broader interests.
As for the current development … I started thinking that we will really see Fosaka 2025!
