Ethereum developers have proposed a change to how gas is calculated for validator deposits, aiming to include the request bytes generated by these events in block gas accounting. The move targets more accurate resource management for the Ethereum network.
Background and motivation
Currently, the gas charged for validator deposit transactions covers only the execution step. After executing a deposit, the network passes on a request of 192 bytes with the block, but this data is excluded from the minimum gas charge. As a result, more data may be included in a block than the original gas limit calculation anticipates.
On Ethereum, gas determines how much computational and data resource can be consumed in each block. Validator deposits are on-chain actions that add new validators to the network, which is essential for maintaining its proof-of-stake security model.
Unaccounted data and EIP limitations
The developers noted that neither EIP-8131 nor EIP-8279, two ongoing proposals in the Ethereum ecosystem, account for these extra request bytes. This gap means that after EIP-8279 eliminates the bypass method through cold storage reads, deposits could offer another route to avoid the intended gas minimums.
The proposal explains that in the context of Gloas—an advancement in Ethereum’s consensus—there is no strict limit to the number of deposits per block, outside of gas itself. Additionally, the execution layer of Ethereum has not imposed a cap, so gas usage remains the only real restriction.
A relay contract can make repeated calls to the deposit contract, with each deposit costing roughly 26,000 gas. This charge falls below the threshold where the gas floor, applied for zero-byte calldata, would kick in. As a result, a block could include a payload roughly 1.44 times the gas limit divided by 64, compared to 1.15 times this amount in previous scenarios.
Mini dictionary: Gloas is a proposed advancement in Ethereum’s consensus protocol, intended to streamline validator onboarding and improve network efficiency. It builds on prior efficiency proposals, including EIP-6110, by optimizing the management of large-scale deposits.
Proposed solution and user impact
To address these shortcomings, the developers propose measuring and charging gas for the 192-byte data payload associated with deposit events. The condition matches EIP-6110, which already classifies logs with the deposit event topic as 192-byte request entries.
Implementing this change would require client developers—teams maintaining Ethereum’s software clients—to add and test new checks in their codebases.
By accounting for the actual data size passed with each deposit, Ethereum could ensure that its minimum gas charges more accurately reflect total resource consumption.
For ordinary users, the proposal is not expected to increase the cost of making validator deposits. The execution cost for a single deposit already exceeds the suggested gas minimum, so the additional 12,288 gas would simply set a slightly higher minimum threshold.
| Scenario | Payload Size (Relative to Limit) | Minimum Gas Added |
|---|---|---|
| Current (No fix) | 1.44 × gas limit ÷ 64 | None |
| Proposal (With fix) | 1.15 × gas limit ÷ 64 | 12,288 gas |
The proposal has not yet been scheduled for inclusion in a future Ethereum network upgrade. Its adoption would depend on further review and community consensus.






