Gas Fees
Transaction Costs and Gas Estimation on Meta Yield ($MY)
In the Meta Yield ($MY) network, there are two key parties responsible for transaction fees when submitting a transaction:
The Poster – If reimbursable, this party pays for L1 resources, such as the L1 calldata required to post the transaction.
The Network Fee – This accounts for L2 resources, which include computation, storage, and other operational costs that L2 nodes incur to process and service the transaction.
L1 and L2 Components of Transaction Fees
The L1 component is determined by the transaction's estimated contribution to the batch's size. This is calculated by applying the Brotli compression algorithm to the transaction by itself. The L2 component then adjusts based on the L2 network's view of the L1 data price, which dynamically fluctuates over time to ensure fair compensation for the batch poster. This is all governed by L1 Pricing principles.
The L2 component consists of the traditional fees paid by Geth (Ethereum) to stakers in a vanilla L1 chain. These fees cover the computation and storage costs associated with applying the state transition function. Additionally, Meta Yield (via ArbOS) charges extra fees for executing L2-specific precompiles. These additional fees are dynamically priced depending on the specific resources utilized during the execution of the call.
Gas Price Floor on Meta Yield ($MY)
Each Meta Yield chain has a minimum L2 gas price, which can be queried via the Meta Yield GasInfo's getMinimumGasPrice method. For now, this is set at 0.01 Gwei on Meta Yield. This gas price floor ensures that transaction fees remain fair and predictable, while still providing enough compensation to the network participants.
Estimating Gas on Meta Yield ($MY)
To estimate the gas required for a transaction on Meta Yield ($MY), you can use the eth_estimateGas RPC call. This will return a value sufficient to cover the full transaction fee at the current L2 gas price. Essentially, the value returned from eth_estimateGas multiplied by the L2 gas price gives the total Ether required for the transaction to succeed.
It's important to note that the value returned by eth_estimateGas can change over time due to fluctuations in the L1 calldata price. As a result, you should expect that estimates will shift as network conditions evolve.
Tips in L2 Transactions
On Meta Yield ($MY), the Sequencer prioritizes transactions on a first-come, first-served basis. Since the concept of tips does not align with this model, tips are ignored in the Meta Yield ecosystem. Users on Meta Yield always pay the base fee, regardless of the tip they choose to set.
Gas Estimation for Retryable Transactions
When submitting a transaction that schedules another (for example, when redeeming), the subsequent transaction's execution will be included when estimating gas via the node's RPC. For this reason, a transaction's gas estimate can only be fully accurate if all the scheduled transactions succeed within a given gas limit.
This is particularly important when working with retryable transactions and scheduling redemption attempts. Since a call to redeem donates all of its gas to the process, multiple tasks should be limited to specific amounts of gas for each subcall. If this is not done properly, the first subcall might consume all of the gas, leading to the failure of the second one, regardless of the estimated gas limit.
Gas estimation for Retryable submissions can be done via the NodeInterface, and it similarly requires that the auto-redeem attempt be successful for the gas estimation to be accurate.
This setup ensures efficient transaction handling on Meta Yield ($MY), including flexible gas estimations, dynamic fee adjustments, and a robust system for handling retryable transactions. By integrating these mechanics, Meta Yield ($MY) aims to enhance user experience while maintaining a secure and scalable Layer 2 solution.
Last updated