Product overview
How io.sign, io.vault, and io.network fit together
Version 2 betaThese docs describe version 2, which is in public beta. Content and setup instructions may change before general availability.
io.finnet is built as a stack of products. io.sign is the core that everything else depends on. io.vault adds three modules on top of io.sign: Treasury, Tokenisation, and Compliance. io.network builds on io.sign, Treasury, and Tokenisation, and runs on io.chain, our private blockchain network.
This page summarises each product and how they depend on one another. Follow the links to learn more about each one.
The core signing product. Every other product depends on it to produce threshold signatures.
Digital asset custody with your keys secured by io.sign. Includes Treasury, Tokenisation, and Compliance.
Treasury and Tokenisation on io.chain, our private blockchain network, for banks and their clients.
Platform basics
How the products fit together
The products layer on top of each other. Each layer requires everything below it:
- io.sign is required by everything. You can't run any other product without it.
- Treasury requires io.sign. You can deploy Treasury with io.sign alone, without Tokenisation.
- Tokenisation requires io.sign and Treasury.
- io.network requires io.sign, Treasury, and Tokenisation.
io.sign
io.sign is the core signing product. It produces threshold signatures using Multi-Party Computation (MPC), and every other product relies on it to sign transactions and messages. io.sign returns a raw signature that you can broadcast yourself, or hand to io.vault to broadcast automatically.
- Produces raw ECDSA and EdDSA signatures using threshold signing.
- Each signer holds its own key share, so no single party ever holds the full private key.
- Supports Mobile Signers on people's own devices and automated Virtual Signers.
Start with the io.sign overview to choose a deployment, configure the service, and complete your first signing request.
io.vault
io.vault is the digital asset custody product, with your keys secured by io.sign. It manages signers and broadcasts signed transactions to the blockchain. io.vault provides three modules: Treasury, Tokenisation, and Compliance.
Treasury
Treasury is the custody and asset management module. It manages vaults and signers, screens transactions with Blockaid, broadcasts signed transactions on your behalf, and indexes your vaults' transactions and balances.
- Requires io.sign. You can deploy Treasury with io.sign alone, without Tokenisation.
- Manages vaults, signers, and thresholds.
- Screens transactions with Blockaid on supported chains.
- Broadcasts signed transactions to supported blockchains automatically.
- Indexes each vault's transactions and balances on supported blockchains.
Tokenisation
Available on enquiry. General availability is planned for Q1 2027. To activate Tokenisation now, speak with [email protected].
Tokenisation builds on Treasury to deploy and manage tokenised assets and stablecoins: ERC-20 and ERC-3643 tokens on io.network and EVM networks, and Liquid AMP2 assets.
- Requires io.sign and Treasury.
Compliance
Coming soon. Compliance will hold the transaction policies every transfer must pass. It will also record Travel Rule data on transfers and keep a full audit trail.
Learn more in Compliance.
io.network
io.network runs io.vault Treasury and Tokenisation on io.chain, our private, permissioned blockchain, for banks and their clients. Transactions are private, gas-free, and final as soon as they are included in a block.
- Requires io.sign, Treasury, and Tokenisation.
- Banks and other institutions join as principal members, and invite their clients as members.
- Designed for banks, investment firms, and other financial institutions.
Learn more in the io.network section.
Updated 17 days ago