> For the complete documentation index, see [llms.txt](https://docs.constellationnetwork.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.constellationnetwork.io/network-intro/dag-delegation/managing-delegated-positions/delegation-rewards.md).

# Delegation rewards

By participating in the network through delegation, you support validator operations and contribute to metagraph projects. In return, the protocol provides DAG-based incentives to encourage active participation.

### **How rewards are distributed**

* Incentives are automatically added to your delegated balance, increasing your stake over time.
* These incentives accumulate in your delegation position and are not directly claimable.
* To access your delegated tokens and the associated incentives, you must undelegate and wait for the 21-day unbonding period to complete.

{% hint style="warning" %}
**On integrationnet, for testing purposes, the unbonding period is 1 day only**
{% endhint %}

### **Incentive sources**

Delegators receive incentives through the following components:

1. **Fixed incentive rate (3% annualized)**
   * All delegated DAG receives a consistent 3% annual incentive, providing a stable baseline for participation.
2. **Variable emissions (45% of protocol-level emissions)**
   * 45% of all newly minted tokens are allocated to delegators.
   * This share adjusts based on the overall network delegation rate, offering greater incentives when less than 60% of the total DAG supply is delegated
3. **Validator commission**
   * Validators  apply a commission fee to the total incentives earned by their delegators.
   * This commission supports validator operations and is deducted before rewards are distributed to delegators.
   * The commission rate varies by validator and is displayed when choosing where to delegate.


---

# 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.constellationnetwork.io/network-intro/dag-delegation/managing-delegated-positions/delegation-rewards.md?ask=<question>&goal=<user_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.