This Ethereum scaling upgrade can’t be simply understood as a blanket reduction in fees
Glamsterdam’s proposal increases Ethereum’s processing capacity while also adjusting gas charges for certain newly added on-chain data operations. Whether this scaling will make a particular application cheaper depends on which operations it uses and the gas price at that time—not on a vague assumption that fees are uniformly discounted.
As of October 1, the official plan is to activate on October 6 on the Sepolia testnet. The dates for Hoodi and the mainnet have not been determined yet. This announcement has not changed the existing mainnet fee rules for $ETH .
Besides executing transactions, nodes must also store account information, contract code, and storage data. With more things allowed per block, the new data may also occupy disk space faster and slow down nodes. Simply improving execution speed doesn’t solve the ongoing problem of accumulating data.
The upgraded block access lists will list the accounts and storage locations involved in executing transactions, enabling clients to read and verify in parallel. If clients can process more work at once, that creates the conditions to increase throughput. But reading faster doesn’t mean storing less—the long-term burden of additional data still needs to be handled.
The included EIP-8037 increases gas charges for operations such as creating new accounts, writing to new storage locations, and deploying code, and measures the newly added state separately. This fee structure is intended to control the data growth rate after scaling. If an application frequently creates new data, it needs to重点算 (pay particular attention to) and estimate the extra cost of these operations. There is also another fee adjustment for accessing existing data, so you can’t simply categorize applications into “fees increase” and “fees don’t increase.”
An increase in the gas consumed by the same kind of operation doesn’t necessarily mean the ETH-denominated bill will rise. If congestion eases after scaling, the decrease in unit price may offset the increase in usage; and even if demand grows along with it, you still can’t guarantee that transaction fees will go down.
Developers also have to deal with compatibility issues. After the Ethereum Foundation replayed historical transactions, they found that most transactions can still be executed unchanged, while a small number of contracts rely on hard-coded gas assumptions. Some failures can be resolved by raising the transaction gas limit, while others require modifying the contract or how it is called. Increasing the limit only allows a transaction to use more gas—it does not automatically make every transaction spend the full amount.
Testnet fees also can’t be used to predict mainnet bills, because test traffic and the prices users are willing to pay are different. For application teams, a more useful approach is to test the new rules with their own transactions and compare the old and new usage under the same gas unit price. First determine how much more or less the business itself will consume, then observe congestion and gas prices after the upgrade goes live on mainnet. Only by combining these two parts can you tell whether this scaling upgrade will save money for your users—or cost them more.
Glamsterdam’s proposal increases Ethereum’s processing capacity while also adjusting gas charges for certain newly added on-chain data operations. Whether this scaling will make a particular application cheaper depends on which operations it uses and the gas price at that time—not on a vague assumption that fees are uniformly discounted.
As of October 1, the official plan is to activate on October 6 on the Sepolia testnet. The dates for Hoodi and the mainnet have not been determined yet. This announcement has not changed the existing mainnet fee rules for $ETH .
Besides executing transactions, nodes must also store account information, contract code, and storage data. With more things allowed per block, the new data may also occupy disk space faster and slow down nodes. Simply improving execution speed doesn’t solve the ongoing problem of accumulating data.
The upgraded block access lists will list the accounts and storage locations involved in executing transactions, enabling clients to read and verify in parallel. If clients can process more work at once, that creates the conditions to increase throughput. But reading faster doesn’t mean storing less—the long-term burden of additional data still needs to be handled.
The included EIP-8037 increases gas charges for operations such as creating new accounts, writing to new storage locations, and deploying code, and measures the newly added state separately. This fee structure is intended to control the data growth rate after scaling. If an application frequently creates new data, it needs to重点算 (pay particular attention to) and estimate the extra cost of these operations. There is also another fee adjustment for accessing existing data, so you can’t simply categorize applications into “fees increase” and “fees don’t increase.”
An increase in the gas consumed by the same kind of operation doesn’t necessarily mean the ETH-denominated bill will rise. If congestion eases after scaling, the decrease in unit price may offset the increase in usage; and even if demand grows along with it, you still can’t guarantee that transaction fees will go down.
Developers also have to deal with compatibility issues. After the Ethereum Foundation replayed historical transactions, they found that most transactions can still be executed unchanged, while a small number of contracts rely on hard-coded gas assumptions. Some failures can be resolved by raising the transaction gas limit, while others require modifying the contract or how it is called. Increasing the limit only allows a transaction to use more gas—it does not automatically make every transaction spend the full amount.
Testnet fees also can’t be used to predict mainnet bills, because test traffic and the prices users are willing to pay are different. For application teams, a more useful approach is to test the new rules with their own transactions and compare the old and new usage under the same gas unit price. First determine how much more or less the business itself will consume, then observe congestion and gas prices after the upgrade goes live on mainnet. Only by combining these two parts can you tell whether this scaling upgrade will save money for your users—or cost them more.