BALUSD
Balancer / United States dollar
crypto Composite

It is mostly due to the following 3 EIPs:
- EIP-7732, Enshrined Proposer-Builder Separation: This restructures how much time there is per slot (12s) for executing the transaction in the block. One can even attest to a block without having it validated fully. As far as I remember validators now have 9 seconds to validate a block instead of 4s. More time means more time to validate larger blocks.
- EIP-7928, Block-Level Access Lists (BAL): It adds a list to every transaction which indicates which resources it needs access to. This allows execution clients to preload all the needed state into RAM which makes the execution itself much faster. It also allows for much more efficient parallelization of the execution validation than we have now. That is a pretty massive gain. Blocks are getting larger in size though as the list adds quite a few kBs.
- A bunch of gas repricing EIPs: There are quite a few EIPs which reprice the gas cost for certain operations. This means one can push the gas limits quite a bit without risking extremely validation times in the worst case.
Execution client teams have not optimized their code fully and it will take some time to get there. That is why they compromised on 200M Gas. According to an execution client core dev theoretically 900M should be possible through ePBS and BALs alone. The same core dev said: "200M is the weaksauce level; likely goes higher". So we will see were it goes in the coming year.

It is mostly due to the following 3 EIPs:
- EIP-7732, Enshrined Proposer-Builder Separation: This restructures how much time there is per slot (12s) for executing the transaction in the block. One can even attest to a block without having it validated fully. As far as I remember validators now have 9 seconds to validate a block instead of 4s. More time means more time to validate larger blocks.
- EIP-7928, Block-Level Access Lists (BAL): It adds a list to every transaction which indicates which resources it needs access to. This allows execution clients to preload all the needed state into RAM which makes the execution itself much faster. It also allows for much more efficient parallelization of the execution validation than we have now. That is a pretty massive gain. Blocks are getting larger in size though as the list adds quite a few kBs.
- A bunch of gas repricing EIPs: There are quite a few EIPs which reprice the gas cost for certain operations. This means one can push the gas limits quite a bit without risking extremely validation times in the worst case.
Execution client teams have not optimized their code fully and it will take some time to get there. That is why they compromised on 200M Gas. According to an execution client core dev theoretically 900M should be possible through ePBS and BALs alone. The same core dev said: "200M is the weaksauce level; likely goes higher". So we will see were it goes in the coming year.