Overview
Digital asset custody with Treasury, Tokenisation, and Compliance, and your keys secured with io.sign
io.vault brings Treasury, Tokenisation, and Compliance together in one custody platform. Every module shares the same vaults, signers, threshold, and audit trail, all secured by io.sign Multi-Party Computation (MPC).
io.vault modules
Hold and move assets across Bitcoin, EVM, Solana, Tron, and XRP with vaults and io.sign MPC approvals. Blockaid* screens every transaction before it reaches your signers.
Screening by Blockaid*
*Supported Blockaid chains only.
Issue and manage tokenised assets and stablecoins from your vaults, with minting and burning approved by your signers.
Available on enquiry
General availability Q1 2027. Speak with [email protected].
Set the transaction policies every transfer must pass before it reaches your signers. Transfers carry Travel Rule data, and every action is recorded in a full audit trail.
Coming soon
How io.vault works
io.vault is a self-custody platform: your organisation keeps control of its keys instead of handing them to a third-party custodian. Your keys are secured with io.sign, which signs with MPC:
- Each vault's private key is split into key shares held by its signers. No single party, including io.finnet, holds the complete key. It can only be reconstructed from backups during disaster recovery.
- A transaction is signed only when signers whose combined weight meets the vault's threshold approve it.
- Signers are people approving on the Mobile Signer app, or Virtual Signers that apply your approval policy automatically. A vault can combine both.
io.vault adds the custody workflow around those signatures: building and broadcasting transactions, screening them, and issuing tokenised assets. Transaction policies are coming soon. You work with io.vault through the Dashboard and the API.
Key concepts
| Term | Meaning |
|---|---|
| Vault | An ECDSA and EdDSA key pair, split between the vault's signers according to their weights. |
| Signer | A Mobile Signer or Virtual Signer that holds a key share for a vault and approves its requests. |
| Key share | The part of a vault's private key held by one signer. Shares are never combined into a complete key during signing. |
| Weight | Each signer's contribution towards the threshold. |
| Threshold | The minimum combined weight of approving signers needed to sign. |
| Resharing | Changing a vault's signers, weights, or threshold without changing its public key or addresses. |
See Vaults, signers, and thresholds for worked examples of how weights combine.
Where to start
Updated 17 days ago