Institutional Vault Release v2.2.0

Extended Blockchain Protocol Support

Added native support for Canton Network and Base chain, expanding the wallet's blockchain compatibility to include enterprise-grade distributed ledger technology and Coinbase's Layer 2 solution.

Bring Your Own Identity Provider (BYOIDP)

Standardized authentication framework based on OpenID Connect (OIDC) protocol, enabling customers to integrate their existing enterprise Identity Providers for user authentication to the Institutional Vault UI. This implementation supports major providers including Microsoft Azure Entra ID, Okta, and any OIDC-compliant identity platform, allowing organizations to maintain centralized user management, enforce existing security policies, and leverage established authentication workflows without requiring migration to a proprietary identity system.

API v2 Enhancements

Extended the v2 API to support direct smart contract deployment through the Transfer API, streamlining complex contract interaction workflows. Added explicit transaction nonce and gas parameter controls to enable Replace-By-Fee (RBF) scenarios, providing institutions with precise control over transaction prioritization and fee optimization strategies during network congestion.

ClientSDK Code Generation

Introduced OpenAPI specification-based code generation for client SDKs across TypeScript, Java, Go, Python, and C#. This standardized approach ensures type-safe API integration, reduces integration complexity, and accelerates development cycles by providing native library support for all major enterprise programming languages.

MPA Horizontal Scalability

Implemented horizontal scaling capabilities for Multi-Party Authorization (MPA) nodes. This distributed architecture enhances system throughput, provides fault tolerance through node redundancy, and ensures consistent performance under high-load conditions for mission-critical operations.

AWS RDS IAM Authentication

Enhanced database security through AWS RDS IAM authentication with automatic token rotation, eliminating static credential storage and reducing credential compromise risks. This implementation maintains backward compatibility with existing deployments while providing a seamless migration path to identity-based access control for database connections.