Ethereum developers have proposed a change to gas accounting mechanisms that would include data created by validator deposits in gas calculations [1]. Currently, while gas accounting measures the execution of deposits, the 192-byte request data passed along with each block after deposit completion is excluded from the minimum gas charge, creating a potential loophole [1]. This exclusion means that under Gloas, where there is no fixed cap on deposit requests per block and the execution layer has not implemented one either, gas becomes the only limiting factor, potentially allowing more data than initial calculations account for [1].
The technical issue stems from the fact that neither EIP-8131 nor EIP-8279 accounts for these request bytes, meaning deposits could become another way to bypass the gas floor once EIP-8279 closes existing loopholes involving cold storage reads [1]. A relay contract can call the deposit contract repeatedly at around 26,000 gas per deposit, resulting in a payload of approximately 1.44 times the block gas limit divided by 64, compared with about 1.15 times the baseline [1]. The proposal directly addresses this data size issue by counting a log from the deposit contract with the deposit event topic as 192 bytes before the log entry is added, using the same condition EIP-6110 uses to turn logs into requests [1].
According to the proposal, regular users are not expected to pay more for standard deposits, as the cost of executing a regular deposit is already above the proposed minimum, meaning the extra 12,288 gas would only raise the minimum charge [1]. However, implementing this change would require an additional check that client developers would need to implement and test [1]. The proposal has yet to be scheduled for a network upgrade [1].
CONCLUSION
Ethereum developers are addressing a potential gas accounting vulnerability in validator deposits that could allow circumvention of gas limits through repeated deposit requests. While the proposed fix aims to close this loophole without increasing costs for regular users, the change requires client-level implementation and remains pending network upgrade scheduling.