> For the complete documentation index, see [llms.txt](https://docs.bloxchain.app/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.bloxchain.app/platform-bloxchain.app/use-cases/token-ops.md).

# Token mint & burn

**Audience:** Admin · **Time:** \~60 min (testnet)

Guard **mint** and **burn** with compliance-style approval — supply changes only after review.

## What you build

| Piece          | Recommendation                                                |
| -------------- | ------------------------------------------------------------- |
| **Operations** | `Mint`, `Burn` (per your token ABI)                           |
| **Roles**      | `Minter Requester`, `Compliance Approver`                     |
| **Workflow**   | Meta request + approve (or **Time-delay** for cooling period) |
| **Allowlist**  | Token contract as target; optional mint `to` recipients       |

***

## Prerequisites

* Account workspace + deployed or linked token contract.
* Token ABI available (mint/burn function signatures).

***

## Step 1 — Security baseline

**Deployment → Security** ([Security settings](/platform-bloxchain.app/overview-1/security-settings.md))

| Setting      | Recommendation                                                                          |
| ------------ | --------------------------------------------------------------------------------------- |
| **Owner**    | Token admin — controls schema registration                                              |
| **Timelock** | Strongly recommended for mint/burn on mainnet                                           |
| **Recovery** | Document for supply-incident response — [Recovery](/platform-bloxchain.app/recovery.md) |

***

## Step 2 — Register mint and burn operations

**Deployment → Operations → Register** ([Operations](/platform-bloxchain.app/overview-1/operations.md))

### Mint

| Field                 | Value                                            |
| --------------------- | ------------------------------------------------ |
| Operation name        | `Mint`                                           |
| Function signature    | `mint(address,uint256)` *(adjust to your token)* |
| Workflow capabilities | **Meta request + approve** or **Time-delay**     |

### Burn

| Field                 | Value                                      |
| --------------------- | ------------------------------------------ |
| Operation name        | `Burn`                                     |
| Function signature    | `burn(uint256)` or `burn(address,uint256)` |
| Workflow capabilities | Same as mint                               |

**Sign** → **Execute** for each.

If your token uses non-standard selectors, copy the exact signature from your contract ABI — mismatch blocks registration.

***

## Step 3 — Create roles

**Deployment → Roles** ([Roles & members](/platform-bloxchain.app/overview-1/roles-and-members.md))

| Role name             | Purpose                                           |
| --------------------- | ------------------------------------------------- |
| `Minter Requester`    | Submits mint/burn requests (ops or bridge wallet) |
| `Compliance Approver` | Approves supply changes                           |
| Owner                 | Protected — admin only; not day-to-day minter     |

Never assign request + approve on the same wallet for production token ops.

***

## Step 4 — Grant permissions

For **each** of Mint and Burn ([Permissions](/platform-bloxchain.app/overview-1/permissions.md)):

| Role                | Pending Request | Sign and approve request | Finalize approved request |
| ------------------- | :-------------: | :----------------------: | :-----------------------: |
| Minter Requester    |        ✓        |             —            |             —             |
| Compliance Approver |        —        |             ✓            |             ✓             |

Optional: grant **Cancel** to Compliance if you enabled **Meta cancel** on the schema.

***

## Step 5 — Allowlists

**Allowlists** ([Allowlists](/platform-bloxchain.app/overview-1/allowlists.md))

| List                 | What to add                                                                        |
| -------------------- | ---------------------------------------------------------------------------------- |
| **Contract targets** | Your **token contract** address (required for external mint/burn calls)            |
| **Recipients**       | Optional — restrict `to` addresses for mint if policy requires capped destinations |

***

## Step 6 — Connect your application

* Whitelist token under the mint/burn **execution selector** ([Connect your application](/platform-bloxchain.app/overview-1/connect-your-application.md)).
* If a **factory or controller** triggers mints, add it as a **member** on `Minter Requester` or whitelist as call target.
* SDK reads/writes use the **Account workspace** address, not the token address, as `contractAddress`.

***

## Step 7 — Test

1. **Minter Requester** → [Submit request](/platform-bloxchain.app/overview/submit-request.md) — small test mint on testnet.
2. **Compliance Approver** → [Approve and sign](/platform-bloxchain.app/overview/approve-and-sign.md).
3. Verify token `totalSupply` and [History](/platform-bloxchain.app/overview/history.md).
4. Repeat for burn with a trivial amount.

***

## Checklist

* [ ] Mint and burn schemas registered
* [ ] Compliance approver ≠ minter requester
* [ ] Token contract on contract-target allowlist
* [ ] Supply change only after full approval path
* [ ] [Production readiness](/developers/production-readiness.md) before mainnet mint authority

## Protocol

[Guard controller](/protocol/guard-controller.md) · [Definition contract](/protocol/definition-contract.md)

## Related

* [Custom configure](/platform-bloxchain.app/overview-1.md) for non-standard token interfaces
* [Use cases](/platform-bloxchain.app/use-cases.md)


---

# 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.bloxchain.app/platform-bloxchain.app/use-cases/token-ops.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.