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 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.

2.1. Three Types of Policies

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

2.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. Changes to this policy follow Policy Restrictions. This policy addresses user management, group management, and the modification of the transfer policy.

2.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.

2.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.

3. User Management

User Management refers to the process of defining and controlling access within the Institutional Vault system. Register users under Register a User, assign them to groups, and enforce what they can initiate or must get approved for with Config Restrictions and Transaction Restrictions (including Block rules).

3.1. User Types

User types categorize how users authenticate and interact with the wallet:

• Users (Human Users): Individuals who authenticate through your identity provider (IdP) to use the UI and ApproverApp.
• API Users: Programmatic identities that authenticate with API keys for automated access. They can initiate operations; they do not approve or reject in ApproverApp. See API User.

👍

Tips

Put users in groups, then use config, transaction, and policy restrictions to require approvals or Block initiation. That replaces historical Admin / MarketOps / Viewer privilege matrices.

3.2. Groups and restrictions

Groups define membership for approvals and for When initiated by filters on Block rules. Available restriction categories:

📘

Note:

For Block-based initiator restrictions and config approval examples, see Config Restrictions and Transaction Restrictions.

4. Approval process

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 participants in the transaction approval process.

4.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 is critical for preventing fraud and unauthorized access to user funds.

4.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 and requiring multiple approvals for certain transactions, Institutional Vault ensures that all transactions are securely executed.

5. Supported Protocols and Networks

Institutional Vault supports the following protocols and networks:

6. Supported Confidential Computing Configurations

For how MPC key shares are protected inside TEEs, including attestation, encryption at rest and in transit, and comparison with physical HSMs, see MPC and TEE Security Architecture.