State Creation Gas Cost Increase

The five-minute read

One action, walked through

1. Open EIP 8037 and read the status line before the examples.
2. Write down the rule in one sentence. A fair version of that sentence is: This proposal increases the cost of state creation operations, thus avoiding excessive state growth under increased block gas limits.
3. Name the object that changes: CPSB, new_state_added.
4. Ask what an old client, an old contract, or an offline counterparty does. If the document is silent, the silence is part of the design.

The argument, unpacked

What has to be true

• You are implementing EIP 8037 at the status the text itself states: Review.
• The object that has to change is CPSB, new_state_added. A neighbouring document with a similar name is not this one.
• Constants in the text can be superseded by a later fork. Cite the EIP number and the fork you mean.

What happened after the paper

The source marks this review. It is not a live consensus rule just because it has a number. Later documents can narrow, replace, or ignore this one. Cite the number you mean.

What to check before you use the idea

• What does State Creation Gas Cost Increase charge, reject, or redefine on the first touch versus a later one?
• Does a reverted subcall roll the change back?
• Can you point at the object in a client: CPSB, new_state_added?

Terms

EIP 8037

The public text titled State Creation Gas Cost Increase.

Review

The document's own label for how finished the text is. It is not a market fact.

The problem the paper names

An underpriced or ambiguous EVM rule is not a feature. It is a block that takes longer than the gas limit claimed, or a client that disagrees about the result.

What the design proposes

• This proposal increases the cost of state creation operations, thus avoiding excessive state growth under increased block gas limits.
• It introduces a new variable, CPSB (cost per state byte), and sets this unit of gas costs per new state byte by targeting an average state growth of 120 GiB per year at a reference block gas limit of 150M gas units.
• It also introduces an independent metering for state creation costs, thus allowing for increased throughput and for larger contract deployments without being limited by the single transaction gas limit.

How the mechanism is specified

• Taken from the specification, the next constraint is: It introduces a new variable, CPSB (cost per state byte), and sets this unit of gas costs per new state byte by targeting an average state growth of 120 GiB per year at a reference block gas limit of 150M gas units.
• Locate CPSB, new_state_added in EIP 8037 and apply it to one transaction or call.
• Then check the failure the class of rule always has: a node that did not upgrade, a reverted call, a replayed signature, or a peer that does not speak the message.

What this page does not treat as proven

• A gas or opcode change is not a throughput benchmark. It is a relative price and a validity rule.
• Constants in the text can be superseded by a later fork. Cite the EIP number and the fork you mean.
• The source marks this review. It is not a live consensus rule just because it has a number.

Why a venture studio still reads it

Use EIP 8037 when a pitch says 'State Creation Gas Cost Increase' without saying whether the rule is consensus, policy, or an interface. The number is the citation. The pitch is not.