# Deploy Rewards Token (ORC-20）

<mark style="color:green;">**In the next step**</mark>, we will deploy an ORC-20 token to serve as the rewards token.

## Example:

```json
{
  "p": "orc-20",
  "tick": "any tick",
  "name": "any orc-20 token"
  "op": "deploy",
  "max": "11000000",
  "lim": "1000",
  "dt": "brc20-staking",
  "res":"100000",
}
```

<table><thead><tr><th width="147.33333333333331">Key</th><th width="114">Required</th><th>Description</th></tr></thead><tbody><tr><td>orc-20 field</td><td>yes</td><td><del>Rewards Token must comply with the orc-20 protocol, and add two custom keys to the orc-20 protocol: <mark style="color:green;"><code>dt</code></mark>, <mark style="color:green;"><code>da</code></mark></del><br>The rewards token needs to adhere to the ORC-20 protocol and includes two additional custom fields, "dt" and "res," as specified by the ORC-20 standards. It is important to note that the "lim" field must be set to 0, indicating that the token cannot be minted and can only be forged through staking.</td></tr><tr><td>dt</td><td>yes</td><td>Distribution Type: token distribution type other than mint</td></tr><tr><td><del>da</del></td><td><del>yes</del></td><td><del>Distribution Amount: the total amount of tokens issued through the distribution type, this field and max field together are the actual total amount of tokens</del></td></tr><tr><td>res</td><td>yes</td><td>Reserve: The amount reserved by the team, which will be minted directly to the address holding the deploy inscription after deployment.</td></tr></tbody></table>

{% hint style="info" %}
💡 The rewards token belongs to the <mark style="color:green;">`orc-20`</mark> protocol and incorporates custom fields <mark style="color:green;">`dt`</mark> and <mark style="color:green;">`res`</mark>. Please ensure to securely store the deployment inscription of the rewards token, as only the address holding this deployment inscription can deploy a staking pool.
{% endhint %}