> For the complete documentation index, see [llms.txt](https://docs.antimatter.finance/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.antimatter.finance/b2/chain-architecture/reward-distribution.md).

# Reward Distribution

A validator can get rewards by executing transactions. Each transaction has an execution cost and $$15/16$$ of this cost goes to the validator, but $$1/16$$ of the reward goes to the system treasury that can use these funds for the system needs, such as bridging cost coverage and relaying. Not all block rewards go to the validator's owner. A share of them is also distributed between delegators.

Whenever the validator's owner creates a new validator, the commission rate must be specified. The commission rate defines what percentage of the block reward goes to the validator owner. It is limited to 0% up to 30% to limit validators from setting very high commission rates.

On the other hand, delegators' rewards are also calculated based on their total staked amount at the validator. The reward is calculated per one validator. The total rewards for a delegator, if staked at different validators, is the sum or per-validator rewards.


---

# 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.antimatter.finance/b2/chain-architecture/reward-distribution.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.