> For the complete documentation index, see [llms.txt](https://docs.xyo.network/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.xyo.network/xyo-layer-one/architecture/transaction-fees.md). # Transaction Fees Transaction Fees are any funds provided by the client when submitting a transaction to be included in a block. ### Base Fee The Base Fee is defined as the amount of XL1 that needs to be provided for a transaction to enter the pending transaction pool. If the transaction passes the initial signature check, the Base Fee is burned as part of the blockchain’s standard operation. In the case that the transaction fails protocol validation, the actor who is being asked to accept the transaction may claim the Base Fee by wrapping the invalid transaction in a Claim Transaction. ### Gas Fee The Gas Fee is defined as the amount of XL1 that is provided to cover the cost of processing and including the transaction by the block producer. This is variable based on the size of the transaction (including elevated payloads) and the scripts processed during block building. If the gas is insufficient to cover the calculated cost, then it is not included in the blockchain. **100% of this fee may be transferred to the producer's address of choice**, which in most cases is their own address. ### Priority Fee The Priority Fee is defined as the amount of XL1 that is granted to the block producer to raise the priority of the transaction. To determine the priority score, the priority amount is divided by the gas amount. When the transaction is included in a block, **100% of this fee may be transferred to the producer's address of choice**. --- # 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 by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.xyo.network/xyo-layer-one/architecture/transaction-fees.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. 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.