This article discusses the advantages of native rollups in L1 execution, particularly concerning gas billing issues. It points out that with the introduction of new features such as blob sharing, data availability (DA) costs can be better managed, and all native rollup calls use the same execution function, standardizing execution costs. Additionally, proof costs are included in execution costs, making the gas billing of native rollups expected to be equivalent to L1 gas billing. For non-native rollups based on decentralized sequencers, the article proposes several coping strategies, including maximizing the use of FOCIL and pre-confirmation mechanisms, filtering out underpaid transactions, and avoiding becoming native rollups.

Regarding the gas accounting issue, this is a problem that rollups incur because of their desire/need to spread batches across L1 blocks and manage costs in self-determined ways. Native rollup gas accounting could be straightforward in this native rollup future:
<ol>
<li>For DA costs, with upcoming features such as blob sharing, and higher blob and rollups counts, we can start to assume blobs will be full and the per-byte DA cost of transactions within blobs are the same. A per transaction DA fee can conceivably be incorporated into blobs.</li>
<li>All native rollups are calling the same execution function, which should make the execution costs standardized across all rollups and rollup transactions. The respective rollup extension/derivation functions might create slightly different overheads here, but these should be small constants per batch, or calculable multipliers per-transaction.</li>
<li>Proving costs are baked into execution costs in this native rollup future.</li>
</ol>
All of this is to say, native rollup transaction gas accounting has a viable path to being equivalent to L1 gas accounting.
Dedicated non-based sequencer rollups offering preconfirmationsare the main losers in this scenario. A few non-exclusive options if gas accounting inline with what is done for current centralized sequencer rollups can’t be added:
<ol>
<li>Leverage FOCIL and inclusion preconfirmations to the max.</li>
<li>Have a mechanism for filtering out transactions not paying enough if gas costs change because an L1 slot was missed, i.e full or partial reorgs of the preconfirmed chain.</li>
<li>Don’t be native.</li>
</ol>

Summary of Gas Billing Advantages and Challenges in Native Execution on L1