Institutional Vault streamlines crypto operations and treasury management for institutional banks, stock brokers, and large institutional companies. The most reliable blockchain infrastructure backs it. With a single integration, the Institutional Vault assists the institution in managing its digital assets.

You can also check out our video guide on how to onboard the Institutional Vault here:

1. Institutional Vault Features

Institutional Vault offers five important features that make it suited for numerous industries, including traditional Web2 companies, crypto-accepting payment companies and custodians, and Web3 or crypto foundations.

2. Institutional Vault Environments

Institutional Vault offers three different environments that can be used to demonstrate the experience to prospective customers or users.

2.1. Demo Sandbox

Our team leverages this environment for product demonstrations, allowing you to evaluate the wallet without needing personal installation. To obtain access to the Demo sandbox, please get in touch with us at [email protected].

2.2. Self-Installed Sandbox Environment - Testnet

This option allows you to fully experience and evaluate the complete feature set and configuration process of the Institutional Vault while also assessing the product's security. The sandbox environment is not a limited version of the wallet. Instead, it offers comprehensive functionality for testnet network(s) and enables users to engage in the entire process of setting up and managing the wallet.

📘

Note:

This environment is not intended for production.

2.3. Self-Installed Production Environment - Mainnet

The Production Environment of the Institutional Vault refers to the fully operational and functional state of the wallet specifically designed for utilization on mainnet network(s). It serves as the live and active environment where users can engage with the Institutional Vault's complete set of features and capabilities in a production-ready setting.

3. Assets Support

The term "asset" in this context refers to the tokens or native tokens of each cryptocurrency network. Institutional Vault supports numerous cryptocurrency networks that have their own tokens, including the following networks:

Institutional Vault supports the aforementioned networks and enables its users to store, see, transact, and withdraw their tokens.

4. Institutional Vault Policies

Institutional Vault applies a set of principles to a specific set of operations, including both transaction and staking operations. The policy framework guides the decision-making process to determine whether an operation should be approved, rejected, or completed.

📘

Note:

For more details regarding Institutional Vault Policy, please see here.

4.1. Three Types of Policies

Institutional Vault divides the policies into three categories based on the wallet configuration:

4.1.1. Administration Policy

Administration Policy is a collection of rules governing all wallet operations. This policy specifies the behaviour of a wallet for every operation performed on it. This policy is only modifiable by users with the Admin role. This policy addresses user management, group management, and the modification of the transfer policy.

4.1.2. Transfer Policy

A transfer policy is a list of rules for making transfers or transactions. It is only modifiable via the administration policy.

📘

Note:

Launching a wallet with default transfer policies or without transfer policies is possible.

4.1.3. Staking Policy

A staking policy serves as a guidebook for how staking functions in the Institutional Vault. This policy provides clear directions and settings for overseeing the asset staking process, ensuring its smooth and secure operation.

5. User Management

User Management refers to the process of defining and controlling access within the Institutional Vault system. It involves categorizing users into different types and assigning them roles.

5.1. User Types

User types categorize users based on access and interaction with the wallet:

• Users (Human Users): A non-administrator with general access. They can access features but cannot modify policies or settings. Each user must belong to at least one group. If not explicitly assigned, they default to the "all-approvers" group.
• System Users: Programmatic users created for automated access. They are managed by admins, can have roles, and use API keys for authentication in API requests.

👍

Tips

Both types of users can be assigned the same roles, meaning they could have the same privileges in terms of what actions they are allowed to perform.

5.2. Roles

Roles define what a user can do within the wallet system. Regardless of whether the user is a human or system user, roles define the specific actions or permissions granted to that user. Available roles are:

📘

Note:

For more information regarding the privileges of each roles, please see here.

6. Approval Process User Role

Institutional Vault is a secure platform that allows users to manage their cryptocurrencies easily. The platform includes features such as transaction intents, policies, and approval rules, which help ensure transaction security and integrity. The approver and the confirmer are two distinct roles in the transaction approval process.

6.1. Approver

The approver is any user granted permission to approve transactions through the approval app. These users are typically part of a group quorum defined by the wallet's policy and related rules. The approver is responsible for evaluating the transaction request and deciding whether or not to approve it. This role is critical for preventing fraud and unauthorized access to user funds.

6.2. Confirmer

The confirmer is typically the user who initiated the transaction intent and is responsible for initiating the confirmation process by sending a confirmation request to the approval app.

By separating the confirmer and approver roles and requiring multiple approvals for certain transactions, Institutional Vault ensures that all transactions are securely executed.

7. Supported Protocols and Networks

Institutional Vault supports the following protocols and networks:

8. Supported Confidential Computing Configurations