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

Institutional Vault Release v3.8.0

August 31st, 2026 by ReadMe GitHub Action

Versions

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

Updates

User interface

  • Accounts, groups, and API keys can no longer be created with a name that is already in use.

Wallet & API

  • CWP API keys can list, approve, and reject pending operations through /api/cwp/approvals, acting as the authenticated user tied to the key. See Automated Approvals.
  • GET /api/config reports a Version field, stamped at build time from the wallet's git tag or commit and the linked Core Wallet Platform module.
  • The hosted API reference's Try it out sends the configured API key with each request.
  • The audit log Function column recognizes EVM pause, unpause, freeze, and unfreeze compliance-token calls, along with the wider set of ERC-3643 permissioned-token functions (forced transfer, batch operations, and related administrative calls), instead of leaving them undecoded.

Policy Nodes

  • Blockchain network configuration accepts an optional use_zero_fee setting for EVM native drivers, so unset fee fields default to zero on private or custom EVM chains where fee estimation does not apply.

Deployment

  • The mobile approver app has a registered redirect URI in the chart's bundled Keycloak realm, so it can complete sign-in against deployments that use the chart's own identity provider.
  • The Blockdaemon Pricing API configuration can be omitted for zero-egress installs; when the pricing API is unreachable, the wallet falls back to fixed crypto rates instead of failing to start.
  • Customers can read wallet and MPA artifacts from their delivery bucket, in addition to the shared, enclave, and wallet-frontend paths already available. (AWS)
  • Policy Node pods no longer run a separate init container to copy resolved configuration into place. The configurator's secret-resolving init container now writes directly to the path Policy Nodes read from, with the same volume also mounted at the certificate path so existing configuration referencing that path continues to work unchanged.

Fixes

User interface

  • The API key user dropdown is no longer clipped by its dialog.

Wallet & API

  • UTXO transfer history now resolves the owning account for a known address even when the transfer's other party is external, instead of leaving the account unresolved.
  • Canton audit log entries for a single, create-only prepared submission show the template's entity name in the Function column instead of leaving it blank.
  • Canton clawback amounts in audit logs show the actual amount instead of zero.

Deployment

  • CoreDNS can reach the Kubernetes API server on port 443, so AKS node upgrades are no longer blocked by CoreDNS's pod disruption budget. (Azure)