> For the complete documentation index, see [llms.txt](https://docs.rddl.io/rddl-network/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.rddl.io/rddl-network/basics/proof-of-productivity/rewards.md).

# Rewards

The following paragraphs give an overview of how rewards are created and managed. The following stages are processed until someone can access their RDDL rewards:

1. [Reward Calculation](/rddl-network/basics/proof-of-productivity/rewards.md)
2. [Clearance Process](/rddl-network/basics/proof-of-productivity/rewards/clearance-process.md): re-issuance & distribution
3. [Claiming Rewards](/rddl-network/basics/proof-of-productivity/rewards/claiming-rewards.md)

## Staging the Rewards

RDDL tokens are issued as the final rewards of a PoP to a PoP-related multi-sig wallet (**PoP wallet**) on the Liquid network.

Rewarded PoP participants can claim their rewards from this wallet. Tokens to claim RDDL from the PoP-Wallet are minted once a day by a clearance process on Planetmint. The minted tokens representing claims are named **cRDDL** (claimable RDDL).

The block proposing validator verifying the ReportPoPResult message from the challenger mints **stagedCRDDL** following the [reward calculation](/rddl-network/basics/proof-of-productivity/rewards/reward-calculation.md). The resulting stagedCRDDL tokens are converted to cRDDL by the [clearance process](#daily-clearance-process).

## Claiming RDDLS

Details are to be defined. The claiming of RDDL will be issued by a Planetmint message. That message will burn cRDDL and transfer RDDL tokens from the PoP wallet to the specified Liquid address.

{% hint style="info" %}
More details will follow soon.
{% endhint %}

##


---

# 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.rddl.io/rddl-network/basics/proof-of-productivity/rewards.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.