Admin Login
HomeGuidesAPI ReferenceChangelogBlockdaemon Main Docs
Log In
Changelog
Back to All
Added

Institutional Vault Release v3.7.0

August 18th, 2026 by ReadMe GitHub Action

Versions

mothership: v3.7.0
wallet-frontend: v3.7.0
policy-node: v9.13.0
nats: v3.7.0
evm-tracker: v3.7.0
cold-wallet: v3.7.0
db-setup: v3.7.0
nats-secrets: v3.7.0
configmap-init: v0.3.0
policy-node-enclave: v3.7.0

Updates

User interface

  • Audit logs load additional results with cursor-based pagination instead of fetching a fixed page.
  • Audit logs show a Token ID column, carrying the EVM contract address or the Canton instrument identifier.
  • The policy configuration form supports exceptions, and the transaction restriction form supports except-only destination account and address filters. See Config Restrictions and Transaction Restrictions.
  • Policy tables show an Initiated By column.
  • Canton Contract Management adds an Interfaces section on the Contract v3 view, presenting the token standard's own interfaces alongside templates.
  • Canton Contract Management adds a party switcher to the Contract v3 view, keeps the selected package across visits, and allows the panels to be collapsed.
  • Canton Contract Management offers instrument identifiers from the ledger in a dropdown, listing the instruments the acting party already holds first.
  • Canton Contract Management loads party identities in a single request rather than several hundred, and serves the contract catalog compressed and cached, so large catalogs load faster.

Wallet & API

  • Wallet distributed tracing is available for HTTP requests, transfer operations, dependencies and asynchronous transaction events. Tracing is off by default and is enabled by setting an OTLP endpoint, with a configurable sample ratio and service name. Exporter credentials are supplied from a secret reference and never written into generated configuration.
  • Audit log summaries accept limit and cursor query parameters for cursor-based pagination.
  • The audit log download no longer requires a date range when an operation ID or transaction ID is supplied.
  • User audit events record the source IP address and the operation ID.
  • Policy audit events record before and after state, and the forensics CSV export gains a Change Summary column describing restriction changes in readable form.
  • The audit Function column records the on-chain function or Daml choice name rather than the internal policy class or operation type, including Stellar host-function names. Canton amounts are recorded as Daml display numerics and the asset symbol is used for the token.
  • Audit entries for EVM burn operations show the zero address as the destination and resolve the ERC-20 token name.
  • Log verbosity is configurable per component. See Metrics and Health.
  • Event streaming can be switched off by setting webhook_active to false.
  • OIDC issuer, audience and client identifiers move from secret storage into deployment configuration.
  • GET /api/cwp/masterkeys/list returns each master key's name and whether it is external.
  • The create-tenant endpoint accepts an optional API key label per user and returns the generated API keys in the response.
  • A CIP-103 dApp API is available on the Core Wallet Platform.
  • WalletConnect supports Canton, so Canton dApp sessions can be signed through the same connection flow as the existing chains.
  • Canton enrollment accepts optional confirming participant identifiers and a confirmation threshold; when omitted these are still chosen automatically.

Policy Nodes

  • ECDSA signing uses an optimised protocol that reuses oblivious transfers when key material is precomputed, giving a significant improvement in signing throughput. Corrupted player detection is enabled: a node that catches a player deviating from the protocol exits immediately and records the event, and the system must be returned to a safe state manually before that node is restarted.
  • The Encryptor Master Password can be rotated without interrupting service. Set RotateFromEncryptorMasterPassword to the old password and EncryptorMasterPassword to the new one, then restart the node. Each tenant rotates on its first request after restart, and the rotation is idempotent. Remove RotateFromEncryptorMasterPassword once every node has rotated. See Rotate Encryptor Master Password.
  • The metrics endpoint exposes database connection-pool statistics, per-query timing and active MPC session counts. See Metrics and Health.
  • Postgres connections support Microsoft Entra ID authentication on Azure, with dedicated managed identities per Policy Node and passwordless connection strings. (Azure)
  • The allowed contract list is extended to cover an additional distributed asset distribution contract version.

Deployment

  • Microsoft Entra ID authentication is available for both Policy Node and wallet PostgreSQL connections, enabled with the entra_db_auth setting. (Azure)
  • Helm charts are published to the Nexus OCI registry. See Helm Deployment.
  • OIDC metadata is exposed as Helm chart values.
  • NATS health checks use the monitoring port, and the mpc chart probes align with the /live and /ready endpoints. See Metrics and Health.
  • Existing AWS Secrets Manager NATS certificates can be imported for mutual TLS rather than reissued. (AWS)
  • Secret placeholders in TOML configuration are escaped with the tomlEscape pipe, and configmap-init moves to v0.3.0.
  • The evm-tracker accepts custom RPC authentication headers backed by the secret store, configured with rpc_header_key and rpc_header_value under custom_event_streaming and resolved into the generated configuration without Kubernetes Secrets.

Fixes

User interface

  • Canton Contract Management no longer offers Allocate on a delivery-versus-payment leg that already has an allocation.
  • Canton Contract Management reports a recoverable error state when the contract catalog fails to build, instead of leaving the view blank.

Wallet & API

  • The /canton-contract-management/api/identities endpoint is served behind the authentication stack.
  • The ERC-20 balance backfill is retried, so balances are populated when the first attempt fails.
  • Reset and delete user operations started from the wallet interface carry the initiator identifier.

Policy Nodes

  • Configuration templates accept the tomlEscape pipe on secret helpers as a no-op, matching configmap-init template syntax without escaping twice.

Breaking Changes

Wallet & API

  • Existing API User keys issued through /api/systems no longer authenticate. Create replacement keys with POST /api/cwp/users/apikeys/create or in the Vault UI, then update clients to use the new keys.
  • The deprecated legacy user endpoints are removed: GET /api/users, POST /api/users/register, POST /api/users/pair, POST /api/users/id/delete and POST /api/users/id/reset. Use the Core Wallet Platform equivalents: GET /api/cwp/users/list, POST /api/cwp/operations/start/registerUser, POST /api/cwp/operations/start/setUserPublicKey, POST /api/cwp/operations/start/deleteUser and POST /api/cwp/operations/start/resetUser. These endpoints were announced as deprecated in v3.6.0.
  • The /api/systems endpoints for API Users are removed: GET /api/systems/confirmers, POST /api/systems/create and POST /api/systems/id/delete. Use POST /api/cwp/users/apikeys/create, POST /api/cwp/users/apikeys/delete and GET /api/cwp/users/apikeys/list, and GET /api/cwp/users/list to enumerate users. These endpoints were announced as deprecated in v3.6.0.

Policy Nodes

  • Prometheus metric names for Vault operations and Policy Nodes now use the cwp prefix with underscores (for example cwp_function_time, cwp_operation_time, cwp_in_memory_operations, and cwp_broker_publish_size). Update scrape rules, dashboards, and alerts that used the previous unprefixed names. See Metrics and Health.