You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Overview
Currently, Monomer applications will contain all execution gas fees in the FeeCollector module account.
However, we need to add gas consumption for L1 data fees as well to fulfill the OP Stack Spec and compensate the sequencer for posting data on L1. To do this, we can add a new decorator to the default AnteHandler to calculate the L1 data fee. For posting batches via blobs, we can use the following formula:
Update monogen to use a custom AnteHandler for regular transactions.
We’re currently using a custom AnteHandler to bypass signatures and fees for Deposit txs, however we’ll want to use a custom one for regular txs as well to add an additional decorator to the default x/authAnteHandler
Add a new decorator (ConsumeGasForL1DataFeeDecorator) to the AnteHandler to include cosuming gas for L1 data fees.
Overview
Currently, Monomer applications will contain all execution gas fees in the
FeeCollector
module account.However, we need to add gas consumption for L1 data fees as well to fulfill the OP Stack Spec and compensate the sequencer for posting data on L1. To do this, we can add a new decorator to the default
AnteHandler
to calculate the L1 data fee. For posting batches via blobs, we can use the following formula:(compressedTxSize) * (16*l1BaseFee*lBaseFeeScalar + l1BlobBaseFee*l1BlobBaseFeeScalar) / 1e6
Tasks
AnteHandler
for regular transactions.AnteHandler
to bypass signatures and fees forDeposit
txs, however we’ll want to use a custom one for regular txs as well to add an additional decorator to the defaultx/auth
AnteHandler
ConsumeGasForL1DataFeeDecorator
) to theAnteHandler
to include cosuming gas for L1 data fees.ConsumeGasForTxSizeDecorator
The text was updated successfully, but these errors were encountered: