EIP-1559 Gas Fees: Ethereum Fee Mechanism for Developers

Frequently Asked Questions

01.Why did EIP-1559 introduce ETH burning instead of paying the base fee to validators?

EIP-1559 burns the base fee so the protocol ensures fees are paid in the network's native currency and cannot be manipulated through side-channel collusion between users and validators. Burning also creates a deflationary pressure on ETH supply proportional to network activity, aligning long-term incentives between validators and the broader ecosystem.

02.How is Blob Gas different from Execution Gas on Ethereum?

Execution gas on Ethereum L1 covers compute and state changes: opcodes, storage writes, and contract calls. Blob gas introduced by EIP-4844 is a separate market for data availability: blobs are pruned from full nodes after approximately 18 days and are never accessible to the EVM during execution. The two markets have independent base fees so congestion on one does not directly drive up cost on the other.

03.Can setting a high maxFeePerGas cause a transaction to overpay?

No. A high maxFeePerGas is safe: you only ever pay baseFee plus the priorityFee you set. The protocol refunds the difference between your maxFeePerGas and the actual cost. The only financial risk is that a very low maxFeePerGas causes the transaction to sit in the mempool indefinitely if the base fee rises above your ceiling.

04.Does storage slot packing always reduce gas costs in Solidity?

Slot packing saves gas only when the packed variables are written or read together in the same transaction. If you pack an address and a uint96 into one slot but only ever update the address, the required bit-shifting to isolate the variable can increase gas cost compared to using separate full slots.

05.What is the EIP-3529 change and why does it matter for gas optimization today?

EIP-3529 removed the generous storage-deletion gas refund that previously allowed gas tokens like CHI and GST2 to give users up to 50 percent back on high-fee transactions. After EIP-3529, optimization must focus on execution efficiency: fewer opcodes, smaller calldata, and tighter storage layouts rather than refund mechanics. The selfdestruct opcode no longer provides meaningful fee benefits.