> For the complete documentation index, see [llms.txt](https://docs.talus.network/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.talus.network/concepts/13-priority-fee-tokenomics.md).
# Priority-Fee Tokenomics
{% hint style="info" %}
**Audience:** Leaders, liquidity providers, and integrators.
**Goal:** Understand how the priority-fee vault exchanges $US for SUI and records the payment evidence used by eligible work.
{% endhint %}
Priority fees are a protocol payment path for work that needs SUI liquidity for eligible Leader submission. The priority-fee vault holds SUI and $US, publishes a rate and liquidity state, and records shares or payment evidence for the parties that provide or consume liquidity.
### Protocol actors and state
* A **$US buyer** supplies `Coin` and receives the caller-accepted SUI output subject to the minimum SUI output. The ordinary quote-command gap and supported readback boundary are documented in the task guide.
* A **Leader or priority-fee provider** supplies SUI as a `PriorityFeeDeposit` tagged to the Leader capability. Collection credits that Leader’s shares; the shares determine the proportional US entitlement, while a matching registered Leader capability authorizes withdrawal after the vault’s SUI side drains.
* The **vault** exposes SUI, $US, rate, liquidity, deposit, share, collection, and withdrawal state plus the events that prove each transition.
* An **eligible execution** consumes the SUI-side priority charge according to protocol rules. It is a separate accounting charge from Tool price and submitter transaction gas, but it is not a separate funding source: the Task/Execution payment budget is split into `gas_budget_mist` and `priority_fee_reserve_mist`, and the priority amount is computed from that signed budget. Inspect the signed occurrence budget and on-chain `ExecutionPayment` split rather than adding an independent reserve.
The priority-fee vault is a public protocol object. Exact fields, events, and transaction signatures belong to the generated [priority-fee vault reference](/reference/move/nexus_registry/priority_fee_vault.md).
#### Buyer and provider outcomes
The buyer should compute an expected $US-for-SUI output from the supported vault readback, apply `min_sui_out`, submit the wallet-authorized transaction, and compare the before/after vault state and events. A Leader or provider should record the SUI `PriorityFeeDeposit`, its Leader tag, the collection event and share delta, and the later proportional US withdrawal after the SUI side drains. Never treat a displayed rate or share balance as proof that the transaction settled; use effects and events.
#### Guide path
Follow [Use the Priority-Fee Vault as a $US Buyer](/guides/tokenomics/use-priority-fee-vault.md) for the task procedure. That guide names CLI or SDK inspection gaps instead of inventing a command when the selected public client does not expose a reader.
**Next**
Continue to [Protocol Upgrades and Compatibility](/concepts/14-protocol-upgrades-and-compatibility.md) when a release changes the package or identity assumptions behind this state.
---
# 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 following URL with the `ask` and `goal` query parameters:
```
GET https://docs.talus.network/concepts/13-priority-fee-tokenomics.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 `build a script that syncs our docs to a CMS` 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.
