This article discusses the advantages of native rollups executing on L1, pointing out that if rollups are forced to use Ethereum's native STF, they will lose certain capabilities. The article mentions that most functions (except for the second example) can be achieved by adding an extension—L1ContextPrecompile—on top of Ethereum's native STF. This extension allows arbitrary data to be passed from the L1 rollup contract to the L2 EVM. For related content, please refer to "Native Rollup Deposits via Passing L1 Context."


<div>
<div></div>
<img src="https://static.sosovalue.com/sosovalue/2025/04/23/69653f0e-15f3-4eed-b0aa-bc241a447e5e.jpg"> LampAdmin:</div>
<blockquote>
<p>If rollups were forced to use Ethereum’s native STF, they would lose these capabilities</p>
</blockquote>

<p>Most of these (except your 2nd example) could be implemented with a single extension on top of Ethereum’s native STF, the <code>L1ContextPrecompile</code>, which can be used to pass arbitrary data from the L1 rollup contract to the L2 EVM. See <a href="https://hackmd.io/@peter-scroll/rJSKJAFnyx">Native Rollup Deposits by Passing L1 Context</a>.</p>

Advantages of Native Rollups in L1 Execution and Expanded Applications of Ethereum STF