# Token supply operations

#### Overview

`ExternalRequestsManager` smart contracts govern supply operations with USR and RLP. Their specification is the same for both USR and RLP tokens. This includes methods for requesting minting and burning, as well as canceling these requests. The source code and all contract addresses can be found in the [resolv-contracts-public GitHub repository](https://github.com/resolv-im/resolv-contracts-public).

#### Prerequisites

Before performing any operations, the address interacting with the smart contract must be whitelisted. Ensure you are whitelisted to interact with the `ExternalRequestsManager` contracts.

#### Request States

All mint and redemption requests go through three states:

1. **CREATED**: The request has been created and is not yet handled.
2. **CANCELLED**: The request has been canceled by the user. No tokens will be minted or burned for requests in this state.
3. **COMPLETED**: The request has been completed, and the tokens have been minted or burned.

Subpages of this sections further outline minting and redemption processes for USR and RLP.


---

# 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://docs.resolv.xyz/litepaper/for-developers/token-supply-operations.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.