> For the complete documentation index, see [llms.txt](https://docs.mutuum.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.mutuum.com/extra/l2-cost-optimization.md). # L2 Cost Optimization Mutuum plans to optimize transaction costs on Layer 2 (L2) networks by focusing on the primary factor contributing to fees: calldata. Rather than passing multiple full-size parameters, the protocol intends to compress all necessary information into a single byte-encoded string, thereby reducing both on-chain storage and per-transaction expenses. Because Mutuum anticipates supporting a limited set of assets, it can assign each token a compact identifier (for instance, using 16 bits) instead of the full 160-bit address. This approach helps contain the size of calldata whenever users interact with the protocol. Additionally, Mutuum may implement specialized contract logic tailored to the unique structure of rollup environments such as Arbitrum or Optimism, ensuring that transactions remain affordable and efficient. By minimizing the overhead of data transmission and leveraging short-form asset identifiers, Mutuum seeks to offer a rapid, cost-effective user experience on L2 chains, aligning with its goal of delivering greater scalability and accessibility for borrowers and lenders alike. --- # 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.mutuum.com/extra/l2-cost-optimization.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.