> For the complete documentation index, see [llms.txt](https://docs.catalyx.solutions/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.catalyx.solutions/catalyx-blockchain-manager/canton-network/version-2.0/release-notes.md). # Release Notes Product updates and release notes for CAT-BM 2.0 for Canton. ## Version 2.0.0 **Released 31 July 2026** CAT-BM 2.0 is a **complete rewrite succeeding the 1.x line**: a new operator, a new REST API, and a rebuilt web UI. {% hint style="danger" %} **2.0 is not an in-place upgrade from 1.x.** Install it fresh. Contact IntellectEU support before planning a migration from an existing 1.10 or 1.11 deployment. {% endhint %} ### Operator Apply a single `Validator` custom resource and the operator provisions the full stack — the identity provider realm objects and OIDC clients, the Canton participant node, the validator app, the Wallet UI, and the CNS UI, plus an optional Participant Query Store. Components are managed as child `Application` resources with per-component readiness and reconciliation status. Traefik ingress, and PostgreSQL-backed participant and validator databases provisioned automatically. ### REST API Read-only against the Kubernetes custom resources, read/write through the Canton Ledger API proxy: balances, traffic status, participant health, DAR packages, ledger users and wallet users, parties — local, external, and onboarding — and participant public keys. Stateless OAuth 2.0 resource server with per-validator scoped tokens. An interactive Canton console over WebSocket. OpenAPI description published at `/v3/api-docs`. ### Web UI A React single-page application for operating validators without cluster access: a Dashboard, a Validators list, and a 13-tab validator detail view — Summary, Specification, Status, Balances, Traffic, Identity, DARs, Users, Wallet Users, Parties, Endpoints, Participant, and Keys. Application health and resource metrics, with optional Grafana deep links. External party onboarding, and the Canton console. ### Artifacts | Artifact | Version | | ------------------------------------------------------------------ | -------- | | `catalyx-console` image (multi-arch `linux/amd64`, `linux/arm64`) | `v2.0.0` | | `catalyx-operator` image (multi-arch `linux/amd64`, `linux/arm64`) | `v2.0.0` | | `catalyx-ui` image (multi-arch `linux/amd64`, `linux/arm64`) | `v2.0.0` | | `catalyx-canton` Helm chart | 2.0.0 | | `catalyx-canton-validator` Helm chart | 2.0.0 | ### Upgrading from 1.x 2.0 is a fresh installation. Contact IntellectEU support for the migration procedure that applies to your deployment. ### Known limitations * The CRD served version is `catalyx.manager.canton/v1alpha1`. **Field-level changes may still occur in a future minor release.** * Ledger pruning is not exposed in the UI. Use the [Canton console](/catalyx-blockchain-manager/canton-network/version-2.0/console-guide-canton/canton-console.md). * Traffic purchases and balance top-ups are not exposed in the UI. The Balances and Traffic tabs are read-only. * Participant key generation, rotation, and import are not exposed in the UI. * The UI has no per-validator or per-screen authorisation. Restrict access at token issuance in your identity provider. *** ## Later 2.0 updates The following landed after the 2.0.0 release and are available in the current 2.0 line. Confirm the exact version that carries each with IntellectEU support before planning around them. {% hint style="info" %} Each feature page carries a version note where the behaviour differs from 2.0.0, so you can tell what your build supports. {% endhint %} ### Multi-host external parties A party can now be hosted on **several participants**, including participants operated by other organisations, so it survives the loss of any single validator. * The external party onboarding wizard gained a **Hosting** step: name additional hosting participants as confirming or observing, set the confirmation threshold, and optionally make the local validator observation-only. * A new **Hosting Proposals** sub-tab on the Parties tab lists proposals naming this participant, with an **Approve** action. Local and remote co-hosts follow the identical path — nothing is transferred between operators. * An advisory participant lookup warns when a named participant UID is not present on the synchronizer. * The **Hosted Parties** sub-tab shows each party's hosts, their permissions, and its confirmation threshold, with a permission filter. See [External & Multi-Host Parties](/catalyx-blockchain-manager/canton-network/version-2.0/validator-management/external-and-multi-host-parties.md). ### Hosting amendments An existing externally-signed party's hosting can be changed — add a host, remove one, change a permission, or change the threshold — via **Edit hosting** on the Hosted Parties sub-tab. The party's key holder signs the change, and every participant taking on more responsibility approves it from its own Hosting Proposals tab. ### Wallet Gateway A new optional validator component providing a remote wallet whose signing keys are held by an external Wallet-as-a-Service provider. See [Wallet Gateway](/catalyx-blockchain-manager/canton-network/version-2.0/validator-management/wallet-gateway.md). ### AWS KMS An AWS KMS provider alongside Azure Key Vault, using Canton's native AWS KMS support with either IAM Roles for Service Accounts or static credentials. Unlike Azure, it does not require a purpose-built participant image. See [Key Management Service (KMS)](/catalyx-blockchain-manager/canton-network/version-2.0/validator-management/kms-integration.md). ### Azure KMS hardening New Azure Key Vault options: a `credentialType` selector supporting workload and managed identity, a configurable key-encryption-key size, an audit node identifier, and six strict-mode security checks — pinned key versions, key spec validation, key operation validation, rejection of exportable keys, hardened generated keys, and a minimum key-encryption-key strength. {% hint style="warning" %} **Two Azure KMS defaults changed.** Audit logging is now enabled by default, and the default AES key size changed. If you depend on either value, set it explicitly rather than relying on the default. {% endhint %} ### Availability hardening Pod disruption budgets for the operator, API, and UI deployments, so voluntary node disruptions do not take the management plane offline. *** ## Earlier versions Release notes for the 1.x line are published under their own versions in this space.
Version 1.11Release notes for the 1.11 line.Release Notes
Version 1.10Release notes for the 1.10 line.Release Notes
--- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.catalyx.solutions/catalyx-blockchain-manager/canton-network/version-2.0/release-notes.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.