The Ethereum L1 Pectra upgrade has introduced changes to calldata gas costs via EIP-7623 that may affect OP Stack chain profitability in specific configurations and market conditions. This notice outlines the potential impact on your chain and recommends specific actions. EIP-7623 increases the amount of gas payable for calldata-heavy transactions. These include such transactions as those used by OPStack chains before the Ecotone upgrade when blob data availability (blob DA) was introduced. Blob DA has now been the default and recommended option for the OPStack for some time, so almost all chains make use of it. In order to continue to optimize for chains operating with blob DA, the Optimism protocol’s current DA fee pricing formula has remained unchanged despite Pectra activating on Ethereum. This has allowed chains using blob DA to continue without updating their fee config. Chains configured for blob data availability remain entirely unaffected by the Pectra upgrade. However, chains configured for calldata (i.e. operating in a legacy DA mode) may experience a reduction in profitability. It is possible for such chains to be making a loss on data availability costs under certain market conditions. Therefore all chains should check their fee scalar config.Documentation Index
Fetch the complete documentation index at: https://docs.optimism.io/llms.txt
Use this file to discover all available pages before exploring further.
Actions required
Since the Ecotone upgrade, the Optimism protocol prices L2 transactions using a function that incorporates the L1 base fee as well as the L1 blob base fee. The other inputs are the so-called “Ecotone scalars”: operator-controlled parameters stored in the SystemConfig contract which can be used to tune the chain’s (approximate) target profit margin for DA. Please review your Ecotone scalar chain configuration.If your chain uses a zero blob base fee scalar, meaning it is configured to price for calldata only, you may need to update the base fee scalar and/or the blob base fee scalar. Otherwise, no action is necessary.
baseFeeScalar | blobBaseFeeScalar | batcher DA | Impact | Action |
|---|---|---|---|---|
| any | >~10^4 | calldata, blob, or auto | No action required | |
x | 0 | calldata | Undercharging L2 Users | Check scalar config and consider setting baseFeeScalar to x * 10/4 to preserve profit margin |
| any | 0 | blob or auto | Overcharging L2 Users most of the time | Check scalar config and consider setting a positive blobBaseFeeScalar |