Mint and burn
Issue and destroy token supply with signer approval
Available on enquiry. General availability is planned for Q1 2027. To activate Tokenisation now, speak with [email protected].
Minting issues new tokens and increases total supply. Burning destroys tokens and reduces it. Each is a transaction from the vault that holds the relevant role, so that vault's signers approve it with io.sign Multi-Party Computation (MPC) approvals.
What each token type supports
| Token type | Mint | Burn |
|---|---|---|
| ERC-20 Standard and Standard with signed approvals | — (fixed supply) | — |
| ERC-20 Managed issuer | To the vault or any address, up to the cap | From any holder. Holders can also burn their own tokens. |
| ERC-3643 | To an address with a verified ONCHAINID identity | From any holder |
| Liquid AMP2 Transfer-restricted and Issuer | To the issuing vault | From the issuing vault's own holding |
| Liquid AMP2 Standard | — (fixed supply) | — |
On a Managed issuer ERC-20, minting needs the minter role, and burning from a holder needs the compliance role. See Token controls.
Mint or burn
- Choose the token, the address (where the token type allows one), and the amount.
- Optionally, build the transaction first to review exactly what your signers sign.
- Your signers review and approve the request.
- io.vault broadcasts the transaction, and balances and total supply update.
For ERC-3643, minting to an address without a verified identity fails. See ERC-3643 and ONCHAINID.
Amounts and decimals
Amounts are in base units: one token is 10 to the power of its decimals. For a token with 6 decimals, minting 1000000 base units issues 1 token. Check the scale before your signers approve, because a mint or burn can't be reversed except by an opposite transaction.
Reconcile supply
After each mint or burn, check the token's total supply on chain against your issuance records. For a stablecoin, this is the figure you reconcile against reserves.
Updated 17 days ago