> 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/reissuance-and-distribution.md).

# Reissuance & Distribution

RDDL Network initially anticipated notarizing all important aspects of two chains: Liquid and Planetmint. It, of course, turned out not to be economically sustainable. Therefore, all PoP rewards and distribution activities are notarized on Liquid once a day. This process contains two steps: the reissuance of the RDDL tokens and their distribution.

The tokens are distributed to the following wallets: DAO, PoP, early investor, investor and strategic investment.

### Reissuance

Reissuance is triggered periodically (once daily, configurable by the network) by the network. The block proposing validator iterates over all challenges since the last reissuance and computes the number of tokens to be reissued.

The block proposer creates and broadcasts a `ReissueRDDLProposal` message. The network validates the message. The block proposer reissues the calculated tokens once the network confirms the message. After that, the proposer also creates a `ReissueRDDLResult` message with the details about the reissuance.

### Distribution

The distribution of the reissued tokens is set to 30 minutes (15 epochs) after the reissuance. The block proposer initializes the distribution by issuing the `DistributionRequest` message. The network validates the message. The block proposer distributes the tokens following the proposal after the network confirms the message. After that, the proposer creates a DistributionResult message with the corresponding transaction IDs and broadcasts the message to the network.

```mermaid
sequenceDiagram
    participant Proposing-Validator 
    participant Planetmint
    participant All-Validators
    participant 2of3-ReissuanceWallet

    loop Reissuance - once a day 
        Proposing-Validator->>Planetmint: Create & Broadcast Reissuance Request
        All-Validators->>All-Validators: Validate Reissuance Request
        All-Validators->>Planetmint: Approve or reject reissuance Request
        Planetmint->>All-Validators: Distribute request (if approved)
        Proposing-Validator->>2of3-ReissuanceWallet: Reissuance tokens if request got approved
        2of3-ReissuanceWallet->>Proposing-Validator: return transaction ID or error
        Proposing-Validator->>Planetmint: Notarize results of the reissuance (txid)
    end
    
    loop Distribution - 30 minutes after reissuance
        Proposing-Validator->>Planetmint: Create & Broadcast Distribution Request
        All-Validators->>All-Validators: Validate Distribution Request
        All-Validators->>Planetmint: Approve or reject distribution Request
        Planetmint->>All-Validators: Distribute request (if approved)
        Proposing-Validator->>2of3-ReissuanceWallet: distribute tokens if request got approved
        2of3-ReissuanceWallet->>Proposing-Validator: return transaction ID or error
        Proposing-Validator->>Planetmint: Notarize results of the distribution (txid)
    end
```


---

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

```
GET https://docs.rddl.io/rddl-network/basics/reissuance-and-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.