Block Gas Accounting without Refunds

The five-minute read

One action, walked through

1. Open EIP 7778 and read the status line before the examples.
2. Write down the rule in one sentence. A fair version of that sentence is: This EIP modifies the block gas accounting mechanism to prevent the circumvention of block gas limits.
3. Name the object that changes: SSTORE, gas_spent, tx_gas_used.
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 7778 at the status the text itself states: Review.
• The object that has to change is SSTORE, gas_spent, tx_gas_used. 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 Block Gas Accounting without Refunds 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: SSTORE, gas_spent, tx_gas_used?

Terms

EIP 7778

The public text titled Block Gas Accounting without Refunds.

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 EIP modifies the block gas accounting mechanism to prevent the circumvention of block gas limits.
• It proposes that gas refunds, particularly those from SSTORE operations setting storage slots to zero, should not reduce the gas counted toward the block gas limit, while still being applied to transaction gas costs for users.
• Currently, gas refunds from operations like clearing storage slots (setting to zero) reduce both the transaction gas cost for users and the gas counted toward the block gas limit.

How the mechanism is specified

• Taken from the specification, the next constraint is: It proposes that gas refunds, particularly those from SSTORE operations setting storage slots to zero, should not reduce the gas counted toward the block gas limit, while still being applied to transaction gas costs for users.
• Locate SSTORE, gas_spent, tx_gas_used in EIP 7778 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 7778 when a pitch says 'Block Gas Accounting without Refunds' without saying whether the rule is consensus, policy, or an interface. The number is the citation. The pitch is not.