> For the complete documentation index, see [llms.txt](https://docs.merlinchain.io/merlin-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.merlinchain.io/merlin-docs/developers/builder-guides/fees.md).

# Fees

Transaction fees on Merlin Chain comprise two components: **L2 transaction execution fees and L1 security fees**. The L2 transaction execution fee is incurred when executing transactions on the Layer 2 network, while the L1 fee primarily covers the cost of transmitting L2 data and ZK proofs to the Layer 1 network.

At this stage, Merlin Chain only charges L2 transaction execution fees. The fee model for transaction execution is similar to the gas fee model used in other EVM-compatible chains. Each transaction consumes a certain amount of Gas, and users can specify the Gas Price per unit of gas when initiating a transaction. **The total cost of a transaction is calculated as Gas Cost \* Gas Price**. 

This section are a few key points related to Fees on Merlin Chain, including:

* [Fee Model - No EIP-1559 Support](/merlin-docs/developers/builder-guides/fees/fee-model.md)
* [Gas](/merlin-docs/developers/builder-guides/fees/gas.md)

<br>


---

# 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.merlinchain.io/merlin-docs/developers/builder-guides/fees.md?ask=<question>&goal=<endgoal>
```

`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.