Ethereum proposals would separate state-creation costs from state-access costs

Two complementary proposals remain under review

The official EIP-8037 and 8038 documents list November 1, 2026, as their Last Call deadline. Created on October 1 and 3, 2025, respectively, both still show Last Call when checked. They address the same problem from two angles: the cost of keeping new information in Ethereum’s state and the cost of accessing or modifying it. This review milestone is neither final adoption nor a change already applied to users.

State contains the information nodes need to track accounts and contracts. Its growth increases storage demands, while its size can slow database access. The authors seek to align gas pricing more closely with those resources. This is not simply a uniform transaction-price increase: the affected operations, cost components, and consequences for block capacity differ.

Durable creation would have its own meter

EIP-8037 proposes a cost unit per new state byte and separate accounting for execution gas and state-creation gas. A user would pay the sum of both dimensions. At block level, the most heavily used resource would determine fullness and base-fee updates. This separation seeks to support more work without letting storage growth become an uncontrolled constraint.

The document targets average growth of 120 gibibytes annually in a reference scenario with 150 million gas. That is a calibration objective rather than a guaranteed measurement of the future network. It also describes a reservoir mechanism for tracking available gas and handling reversed state creation. Wallet and RPC estimates would need to reflect these rules. Tools measuring work through changes in remaining gas could also require adjustments.

Access and writing would differ from new storage

EIP-8038 separates operations into account or storage-slot access, writing, and possible creation of a new element. It raises cold account-access costs and introduces explicit write components. Durable creation remains priced by EIP-8037. The text also accounts for instructions requiring a second read to obtain contract-code size or contents.

The proposals are incompatible with earlier rules and would require a scheduled upgrade. Their authors acknowledge risks for some uses and greater complexity in block building and cost tracking. Refund mechanisms and interactions with bundled operations require careful checking. For developers, the immediate task is to follow review of these models and estimation tools, without presenting today’s deadline as an activated increase or promising general savings.