In June, we presented ProtocolReorganize the research teams and development of the Ethereum Foundation to better align with our current strategic objectives, L1 scale,, Drop -downAnd Improve UX Without compromising our commitment to the security and hardness of Ethereum.
In the coming weeks, we will publish updates on each workflow, covering their progress in progress, their new initiatives, its open questions and its collaboration opportunities. We start today with the L1 scale — Expect follow-up on blobs on a scale and to improve UX soon!
Tl; DR
- Marius van der Wijden joined Ansgar Dietrichs and Tim Beiko to co-direct the L1 scale
- The Mainnet gas limit increased to 45m afterBerlinteropa first step on the road around 100 m and beyond
- All the main customers of the execution layer have sent Expiration of pre-fusion historyconsiderably reducing the use of the node disc
- Access lists at blocks (BAL) are considered a headliner for Glamsterdam
- Initiatives to calculate calculation and state calculations are underway to better manage the prices of EVM resources and the bottlenecks of performance
- The path of Zkevm in real time proving becomes more concretewith the prototyping of a customer attest based in ZK in progress
- We always hire a Praging in performance engineering: Applications close on August 10
Serious geth-id about L1 scaling
Ethereum scaling requires reconciling ambitious conceptions with engineering pragmatism. To help us get there, we have appointed Marius van der Wijden As a co-directing for the L1 scale alongside Ansgar Dietrichs and Tim Beiko.
Marius’ vast engineering experience on Geth, combined with his commitment to the safety of protocols, makes him a perfect adjustment to align our strategy of scaling with the constraints of Ethereum.
Together, Ansgar, Marius and Tim have defined a set of key initiatives that will allow us to put on the L1 scale as quickly as possible.
Towards a main gas limit of 100 meters
Our immediate objective is to securely extend the main gas limit of Ethereum to 100 m per block. Parithosh Jayanthiclosely supported by Nethermind’s perfnet team, conducts our work to cross Each incremental increase.
In the recent Berlinterop eventCustomer teams have considerably improved their worst performance references, allowing the recent increase to 45 m of gas – a first step on the path to 100m of gas and beyond!
In addition, clients hardening has become an integral part of the 100 m gas initiative. The deployment of Pectra upgrade has highlighted several problems caused by the instability of the network. It is essential to ensure that customers remain robust as the flow increases, even if the network temporarily loses the purpose.
History expiration
The history expiration project, led by Matt GarnettReduces the imprint of historical data from Ethereum nodes. The recent deployment of Partial expiration of partial history Deleted historical data before merger, saving complete nodes from around 300 to 500 GB of disk space. This guarantees that they can work comfortably with a 2 TB disk.
By relying on this, we are now developing the expiration of the history of the bearings, which will continually emit historical data beyond a fixed retention period. This will keep the storage needs of manageable nodes, even as an Ethereum.
Block access lists
Access lists at blocks (BAL), defended by Toni Wahrstaetteremerge as a leading candidate for inclusion in the upgrade of Glamsterdam. The balls offer several critical advantages:
- Activate the execution of the parallel transaction in the blocks.
- Facilitate the parallel calculation of the state roots, considerably accelerating the treatment of the blocks.
- Authorize the preload of the required state at the start of the execution of the block, by optimizing the disk access models.
- Improve the overall effectiveness of nodes synchronization, benefiting new and archival nodes.
These improvements collectively improve Ethereum’s capacity to reliably manage higher gas limits and faster block treatment.
Reward and pricing
A continuous challenge in the Ethereum scaling is to align the gas costs of EVM operations with their general calculation costs. The Performance of the Word of Cases currently limit the flow rate of the network.
By improving comparative analysis infrastructure and repensation operations that cannot be optimized by customers, we can make the execution times of the blocks more coherent. If we conclude the difference between the worst cases of cases, we can then increase the gas limit proportionally.
Ansgar Dietrichs is carrying out efforts focused on targeted comparative and engineering analysis interventions, directly informed by the complete comparative analysis of Perfnet, to identify and resolve the strangulation bottlenecks in calculation. Significant progress has already been made after Berliterop, in particular in the management of calculation scenarios The worst cases.
In parallel, Carlos Pérez spearhead Bloatnet: An initiative to analyze and optimize state performance. This implies testing the performance of the nodes under conditions with state sizes double the current reduction limits and gas reaching 100 to 150 m, to clarify directly the reviews and optimizations of customers.
These two efforts will shed light on the proposals of Glamsterdam EIP to homogenize the costs of resources between operations, allowing additional L1 scaling.
ZKEVM Customer attested
Today, Ethereum nodes perform all transactions in a block during reception. This is expensive in calculation. To reduce this calculation cost, Ethereum customers could rather verify ZK proof of the execution of the block. To activate this, the evidence of the block must be produced in real time, that we obtain closer and closer to.
Kevaundray Wedderburn is at the top of the work on a zkevm ATterter client who assumes that we have proofs in real time and uses them to fulfill his validator tasks.
Once the prototype is ready for Mainnet, it will take place as an optional verification mechanism. We expect a small group of nodes to adopt this over the next year, allowing us to strengthen its robustness and safety.
After that, the Ethereum nodes can gradually switch to validation based on ZK, finally with the default value. At this stage, the L1 gas limit could increase considerably – stupid mode!
RPC Performance and hiring
As the flow increases, different types of nodes (execution, consensus, RPC) are faced with distinct challenges. The RPC nodes specifically meet increased pressure because they serve as large historical and real -time state demands.
Internally, EF Geth and Pandaops teams are actively looking for optimal configurations for different types of nodes. We expect the importance of this to increase in the years to come and want to develop our expertise in this area.
To this end, we actively hire for a Praging in performance engineering. The requests are closed August 10. If you are as excited as we are about the L1 scaling, we would be delighted to hear you!
