Tokenisation
Deploy and manage tokenised assets and stablecoins from your vaults
Available on enquiry. General availability is planned for Q1 2027. To activate Tokenisation now, speak with [email protected].
Tokenisation is the io.vault module for deploying and managing tokenised assets and stablecoins. Your vault deploys each token, so every deployment, mint, burn, and control action is a transaction your signers approve with io.sign Multi-Party Computation (MPC) approvals.
Requirements
Tokenisation requires io.sign and Treasury.
Token lifecycle
| Stage | What happens | Who acts |
|---|---|---|
| Deploy | Your vault deploys the token and holds its roles. | Your vault's signers approve; io.vault broadcasts |
| Mint | New supply is issued. | The vault holding the minting role |
| Transfer | Holders move tokens through Treasury, like any other asset. Permissioned tokens check each transfer on chain. | The holder's vault |
| Control | Pause, block, freeze, or force-transfer, depending on the token type. | The vault holding the relevant role |
| Burn | Supply is destroyed. | The vault holding the burning role |
Before you submit an operation, you can build it first to see the exact transaction your signers approve.
What Tokenisation supports
| Token type | Variants | Networks |
|---|---|---|
| ERC-20 | Standard, Standard with signed approvals, Managed issuer | Any EVM network |
| ERC-3643 (T-REX) | One permissioned token suite with ONCHAINID identities | Any EVM network |
| Liquid AMP2 | Transfer-restricted, Standard, Issuer | Liquid |
See Supported networks for the networks enabled at launch.
In this section
Related products
io.network builds on Tokenisation to transfer tokenised assets on our private blockchain network.
Updated 17 days ago