| This article is relevant for all io.vault and io.network subscriptions, except where otherwise noted. |
Concepts
- Asset card: An asset card displays asset quantity and equivalent US$ value, as well as the wallet address of a particular asset within a given vault. Displayed or hidden assets for a given vault can be managed by selecting “manage assets” from within the vault page
- Deposit address: A deposit address is the specific public address for the digital asset on the relevant blockchain/network that is cryptographically controlled by the underlying secret shares of the given vault
- Reshare request: Users may submit a request to amend an existing vault threshold and/or signing party, including the distribution of signing power. This request must be approved by reaching the existing vault threshold and “signed” by the resulting signing party. This is known as a vault reshare
- Signer or signing device: A specific user device which contains the allocated secret shares of the vaults for which it is a member of the signing party. A signer can be recovered from an old or lost device on a new device by “restoring” the signer on a new device. However, this process requires the up-to-date signer’s encrypted backup file and the signer passphrase or secret recovery phrase generated upon registration of the signer
- Signing party: The collection of signers and their specified signers that contain the secret shares which control a particular vault
- Signing power: The number of secret shares a user controls on their specified signing device as part of a particular vault signing party
- Secret share(s): Sensitive cryptographic data that is required to enable the generation of a valid cryptographic signature for a given vault
- Threshold: The number of secret shares required to enable the signature process or vault reshare for a particular vault
- Transaction request: A transaction request may be submitted via the dashboard and is transmitted to the devices of the signing party of the vault. The request includes the network, asset, destination address, and the quantity to be sent. The request must be approved and signed by members of the signing party for the given vault that have sufficient combined signing power to meet or exceed the vault threshold
- Vault: A grouping of digital wallets for any supported networks or assets, which are controlled by the same Signing Party and underlying secret shares
- Vault card: A Vault Card displays the name of the Vault, assets held within the vault, Vault Threshold
- Vault-to-Vault transfer: This is used for the special case when a transaction is made between two vaults, a transaction that has been sent from one vault to another will be displayed as “Successful”
Additional io.network concepts (io.network Principal Member subscriptions only)
- io.network: A private and permissioned distributed ledger based network, can be referred as ION
- Principal Member or PM: An io.network principal member is a network node operator and is capable of issuing and administering its own assets in a private sub-network for its own underlying clients on io.network
- PM dedicated network account: A dedicated network account for the principal member is used for two processes:
- Where their underlying clients will deposit funds into when they want to deposit into the network
- Is the location where the PM will transfer fund back to the underlying client when withdrawing from the network
- PM dashboard: Naming convention for the dashboard of principal member
- PM support service: Naming convention for the io.network support service
- Underlying client: An io.network underlying client is a principal members direct client that wishes to transact within the PM’s sub-network
- Minting tokens: The action of depositing / creating tokens within the network for an aligned underlying client
- Burning tokens: The action of withdrawing / removing tokens within the network for a specific underlying client
- Enable address: In order for any io.network address to interact with a PM administered assets it must be enable by the PM to their allowlist smart contract which governs access for network users to their administered assets
Dashboard statuses
- Pending: The transaction request is pending approval and signature
- Signing: The transaction request has met the threshold for approval and is pending completion of the signature process
- Rejected: The transaction was rejected by enough of the vault signing party to make it impossible to reach to vault approval threshold
- Expired: The transaction request has expired
- Failed: The transaction was either determined to be invalid by the blockchain node/network, or the signature process failed during signing
- Contract reverted: The associated smart contract interaction on the network has failed, this can occur for various reasons such as incorrect permissions or attempting to send an invalid quantity of tokens
- Submitted: The transaction has been signed and broadcast successfully to the relevant network. Broadcast transactions may remain unconfirmed on the blockchain for some time and may still result in an incomplete transaction in certain circumstances, notably a failed smart contract interaction
- Successful: A request has been approved, signed, submitted and successfully mined on the network
- Received: The transaction has been received