> For the complete documentation index, see [llms.txt](https://docs.lumio.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.lumio.io/fees.md). # Fees The network fees are not yet finalized and will be subject to change after successful testing. For the EVM, the fees might align with those used in OP. The transaction fee on L2 comprises two components: an execution fee and a storage fee. This is because virtually every transaction must be posted to the settlement layer, enabling the recovery of transaction history and verification of L2 transactions. The fees also depend on the load of the settlement layer, meaning they can fluctuate, sometimes being lower or higher. For more details, refer to the OP [documentation](https://community.optimism.io/docs/developers/build/transaction-fees/). Furthermore, as Pontem L2 is settlement-agnostic, in V0 transactions will initially be settled on Ethereum. However, future plans involve using Aptos and other protocols to store transaction data, potentially reducing transaction costs significantly. This approach also allows for a fallback to Ethereum if the primary settlement layer encounters issues. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.lumio.io/fees.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.