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

Institutional Vault Release v3.4.0

June 3rd, 2026 by ReadMe GitHub Action

Versions

Institutional Vault: v3.4.0
Policy Nodes: v9.3.1
NATS: v3.4.0
configmap-init: v0.1.0

Updates

  • Approvers can receive email notifications when an operation requires approval, using a customer-hosted SMTP relay configured for the deployment. See wallet.yaml SMTP configuration in the Cloud-agnostic Install Guide.
  • Native blockchain drivers support optional per-chain RPC authentication via native_driver_auth_token on each blockchains entry in wallet.yaml, overriding mpa_adapter_config.auth_token for that chain's native_driver_url only (Bearer token or Authorization Basic). See wallet.yaml native driver configuration in the Cloud-agnostic Install Guide.
  • Canton Contract Management endpoints are available to MarketOps users as well as Admins.
  • Canton Contract Management selects the correct on-ledger instrument configuration when a registrar hosts more than one instrument, preventing Instrument id must match failures on transfers and mint-related flows.
  • Azure Helm chart now includes liveness and readiness probes for the Wallet, Policy Nodes, and NATS.

Fixes

  • Policy Nodes correct ERC-20 mint transaction validation.
  • A background poller reconciles transactions left in Broadcasting when event streaming does not deliver a final status, marking them finished or failed from on-chain state.
  • WalletConnect call_contract operations no longer remain stuck in Broadcasting when on-chain confirmation arrives before the transaction hash is persisted.
  • Balance sync updates the on-chain block cursor even when the reported balance is unchanged.
  • Audit logging captures Core Wallet Platform request bodies for API-initiated operations.
  • Outgoing Ethereum transfers no longer create duplicate records when confirmation arrives before the transaction hash is written.
  • Direct Mint, Direct Burn, and Offer Mint or Burn delegator lists in Canton Contract Management include only parties eligible under the registrar MasterAllowList claim chain, avoiding submit failures from delegators that appear in the ledger but cannot mint or burn.
  • Canton Contract Management classifies parties without Vault signing keys as read-only instead of offering sign actions that cannot complete from the browser session.