# Transaction Fee Distribution

The use of all the functions in the Jur runtime requires a fee in $JUR tokens; Every user, dApp, or parachain pays an associated fee in $JUR for transactions carried out on the network. Transaction fees are divided into four categories:

<figure><img src="https://lh6.googleusercontent.com/v0ChWx1wFaB7GlNf1k2oL_wu7RTli1oOkc6wrxfhBJuhPk9TGnJXLTZ0dyQTKMgRKVfOWFNgRt_zaz2m5znHwPNIe6UgzzcoGdAgFOnpc1MPlCDm9alnhCEnZb3Ha-KW4zqXIdaNiBvImOvumi6QvdWDKZzTS9A9WUox7GPtLGyjV4nlOhPgMyAdglCwCw" alt=""><figcaption></figcaption></figure>

* 20% Collator Fee as a payment to the collators for their work sustaining the infrastructure costs of running nodes and producing blocks.&#x20;
* 20% Burn Fee as a deflationary force. The circulating supply of $JUR decreases over time, proportional to usage, thus accruing value for $JUR token holders given the fixed total supply of $JUR.
* 40% Society Rewards Pool to the most active communities to incentivize usage. It introduces a progressive force that shifts direct ownership of the network into the hands of the most active users. Creating agency fosters cooperation among network actors, and awards benefits for adoption of the Jur Chain. Rewards are initially accrued in a wallet; after iterations within the Jur community, criteria on how rewards will be distributed will be determined. $JUR holders who become meta-citizens through staking will vote which communities' treasuries receive the reward.
* 20% Jur Ecosystem Pool dedicated to supporting Jur's protocol and ecosystem needs, including technical expenses, parachain bids, and growth-related initiatives.


---

# Agent Instructions: 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:

```
GET https://gitbook.jur.io/jur-documentation/jur-economy/transaction-fee-distribution.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.