Institutional Vault Release v3.2.0

Versions

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

Audit log CSV export includes CAIP-2 chain identifiers alongside existing columns.
Solana cold-wallet registration requests use the same CAIP-19-based asset path pattern as other assets.
Cold signing views refresh when batch WebSocket updates arrive instead of relying on synchronous batch polling.
Staking withdrawal requests accept an optional CAIP-19 field for consistency with other asset-aware transfer APIs.
Pending operations lists and detail views surface approver and rejector attribution using the supported operations APIs.
Vault per-asset detail requests use a single CAIP-19 path segment instead of separate protocol, network, and symbol segments.

Canton Contract Management derives CAIP-2 for signing and registry calls from the connected ledger synchronizer instead of a static gateway CAIP-2 field, preventing chain registration mismatches.

Deprecated v2 configuration, compliance screening, events, automated approver listing, group listing, key backup download, raw transfer, user listing, user creation, user-by-id, staking listing, staking withdrawal submission, transaction listing, transaction detail, and transaction deletion. Use GET /api/transactions, the v1 transaction detail routes, GET /api/operations/{id}, and other v1 or CWP routes described in the published OpenAPI specifications.
POST /api/transactions/transfer and POST /api/staking/stake request bodies require a CAIP19 field instead of separate Asset, Protocol, and Network fields.