Gas Schedule
Pronunciation: GAS SKEH-jool
Definition
A gas schedule assigns resource costs to virtual-machine operations, storage changes, data use, and other transaction behaviors under active protocol rules. Protocol upgrades can reprice opcodes, add refunds, or change warm and cold access costs as hardware and attack understanding evolves. Contracts whose logic assumes a fixed cost or a particular stipend can fail after repricing even when their source code is unchanged.
Overview
Meaning and scope
A gas schedule assigns resource costs to virtual-machine operations, storage changes, data use, and other transaction behaviors under active protocol rules. Protocol upgrades can reprice opcodes, add refunds, or change warm and cold access costs as hardware and attack understanding evolves. Contracts whose logic assumes a fixed cost or a particular stipend can fail after repricing even when their source code is unchanged.
Mechanism and operation
A gas schedule maps each execution operation to a gas cost. It is designed to approximate computational, storage, bandwidth, and denial-of-service burden so expensive actions consume more of a block’s limited capacity. Developers should avoid depending on exact gas amounts for authorization or critical control flow and should benchmark under current fork rules. Payment systems should test contract interactions around upgrades and revise fee reserves when the schedule changes. An estimate should identify the fee unit, network, block context, and transaction parameters used to calculate it. Operational handling of Gas Schedule should account for congestion, replacement rules, rejected fee settings, and software-version differences.
Practical payment example
A payout contract is tested against a network upgrade that changes opcode pricing. Engineers recalculate transaction bounds and confirm that required calls still complete under realistic gas limits.
Operational checks
Calculations should use integer base units and preserve the original fields submitted by the signer, because rounded display values are insufficient for reconciliation or incident review. A pending quote can change before inclusion, and a transaction that fails at execution may still consume a network fee.
Distinctions and limits
Wallet defaults, quoted caps, and minimum protocol charges are different values, so interfaces should label each field and avoid presenting a maximum authorization as the amount ultimately paid.
Related reading
Related definitions: gas.
Example
A payout contract is tested against a network upgrade that changes opcode pricing. Engineers recalculate transaction bounds and confirm that required calls still complete under realistic gas limits.
Comparison
Wallet defaults, quoted caps, and minimum protocol charges are different values, so interfaces should label each field and avoid presenting a maximum authorization as the amount ultimately paid. Operational handling of Gas Schedule should account for congestion, replacement rules, rejected fee settings, and software-version differences.
Key Takeaway
Gas schedules translate operations into resource charges and can change at forks, affecting contract behavior, estimates, and reserves.
Sources
- Ethereum Foundation Documentation: Gas — Ethereum Foundation (2026-07-30)
- Ethereum Documentation: Transactions — Ethereum Foundation (2026-07-30)