Ethereum developers are evaluating a potential shift in the method of calculating gas used for validator investments. The proposed adjustment aims to factor in the additional data load transmitted with a block upon completing an investment transaction. This change seeks to prevent the underestimation of data size by the current computation, which could result in exceeding the predicted total data transferable per block.
Addressing the Overlooked Data Burden
In the current system, the execution cost for a validator investment is included in the gas calculation. However, a 192-byte request data segment transmitted post-transaction does not reflect in the minimum gas fee, potentially allowing more data to enter a block than initially calculated under the same gas limit. Developers identify this data size as the primary issue, suggesting that the additional data load, rather than the execution cost, is the core concern.
The proposal targets the extra data load transmitted with the block, rather than the execution cost of validator investments, aiming to align the gas base more closely with data size.
Current EIP Drafts Lack Coverage on This Aspect
Under the current Gloas structure, there is no fixed upper limit for investment requests per block. Additionally, the execution layer does not impose a cap on these requests, making gas the only practical constraint. Neither EIP-8131 nor EIP-8279 accounts for the request bytes in question. This oversight raises concerns that validator investments might find a new way to exceed the gas base indirectly once the backdoor associated with cold storage reads is closed with EIP-8279.
In a demonstrated scenario, a relay contract can consecutively call an investment contract, each costing approximately 26,000 gas. This execution cost remains below the threshold that begins raising the total fee for zero-byte calldata. Consequently, the resulting data load can rise to about 1.44 times the base value, divided by 64 for block gas limits, up from the previous level of approximately 1.15 times.
A log produced by an investment contract, titled as an investment event, is counted as 192 bytes before any log entry is added. EIP-6110 addresses the transformation of these logs into request structures under similar conditions, prompting developers to view measuring the current data path as a more straightforward technical solution.
Regular users are not expected to face increased fees for ordinary validator investments, as the additional 12,288 gas proposed will only raise the minimum fee slightly.
Network Update Timeline Remains Uncertain
The proposal may impose additional implementation and testing requirements on client developers. Extra verification processes will be essential to ensure the new control mechanism functions correctly across different clients. Despite this, the adjustment is not anticipated to directly render typical validator investments more costly, as the execution cost of a standard investment already exceeds the proposed minimum level. This change has not yet been scheduled for any network update.



