> 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-1.11/validator-management/validator-upgrade-policy-and-release-schedule.md).

# Validator Upgrade Policy and Release Schedule

## Overview

CatalyX follows the official Canton Foundation release lifecycle for validator upgrades. New Canton releases are continuously monitored, evaluated, and validated by IntellectEU before being recommended for customer environments.

The objective of the upgrade process is to maintain compatibility with the Canton Network while minimizing operational risk and service disruption.

{% hint style="info" %}
CatalyX does not automatically upgrade validator nodes. Upgrades are performed in a controlled manner following internal validation, customer communication, and agreed maintenance windows where applicable.
{% endhint %}

***

## Upgrade Policy

Validator upgrades are performed according to the release schedule published by the Canton Foundation.

When a new supported version becomes available, IntellectEU:

* Reviews the Canton Foundation release notes.
* Evaluates compatibility with supported CatalyX components.
* Performs internal validation and testing.
* Reviews migration requirements and known issues.
* Updates internal and customer documentation where necessary.
* Recommends the validated release to customers.
* Assists customers with upgrade planning and execution.

This process ensures that validator nodes remain compatible with the Canton Network while reducing the risk of introducing regressions into production environments.

***

## Release Validation Process

Before a validator version is recommended for customer use, IntellectEU follows an internal release validation process:

1. Reviewing the new Canton Foundation release.
2. Validating compatibility with supported CatalyX services.
3. Testing validator deployment and upgrade procedures.
4. Verifying database migrations (if applicable).
5. Validating package compatibility.
6. Reviewing known issues and workarounds.
7. Updating operational documentation.
8. Recommending the validated release for customer deployment.

{% hint style="info" %}
Only validated releases are recommended for production environments.
{% endhint %}

***

## Release Schedule

CatalyX does not maintain its own fixed release calendar for Canton validator versions. Validator upgrades follow the availability of new Canton Foundation releases.

Customers can monitor upcoming and released versions through:

* Canton Foundation release announcements
* CatalyX Blockchain Manager [Release Notes](/catalyx-blockchain-manager/canton-network/version-1.11/release-notes.md)
* CatalyX Product Roadmap

After a new Canton release becomes available, IntellectEU performs validation before recommending customer upgrades.

***

## Typical Upgrade Process

A validator upgrade generally consists of four stages.

{% stepper %}
{% step %}

#### Preparation

Before performing an upgrade, it is recommended to:

* Schedule an appropriate maintenance window.
* Review the release notes for the target version.
* Verify that recent database backups are available.
* Verify that a recent Validator Identity Dump (IDDump) exists.
* Review any migration requirements.

{% hint style="info" %}
See [Validator Backups and Identity Dumps](/catalyx-blockchain-manager/canton-network/version-1.11/validator-management/identity-backup-and-recovery.md) for how to schedule and verify backups and IDDumps.
{% endhint %}
{% endstep %}

{% step %}

#### Upgrade the Validator Version

The validator application version is upgraded by updating the validator image.

Using the CatalyX UI:

* Open the validator.
* Edit the validator configuration.
* Select the new Image Tag.
* Save the configuration.

Using the [Validator CRD](/catalyx-blockchain-manager/canton-network/version-1.11/validator-management/validator-custom-resource-definition.md):

```yaml
spec:
  imageTag: 0.6.x
```

The operator deploys the updated validator version.
{% endstep %}

{% step %}

#### Execute Migration (When Required)

Some validator releases require an application or data migration.

When migration is required:

1. Increment the Migration ID.
2. Set **Migrating** to **true**.
3. Wait for the migration to complete.
4. Set **Migrating** back to **false**.

Example:

```yaml
spec:
  migrationId: "3"
  migrationMigrating: true
```

After successful completion:

```yaml
spec:
  migrationMigrating: false
```

{% hint style="warning" %}
Migration should only be executed once for each required upgrade.
{% endhint %}
{% endstep %}

{% step %}

#### Post-Upgrade Validation

After the upgrade completes, verify that the validator is operating normally:

* Validator status is **Running**.
* Participant successfully joins and synchronizes with the network.
* Wallet login succeeds.
* Applications start successfully.
* No startup errors are present in the logs.
* Scan API responds successfully.
* Health status is normal.
  {% endstep %}
  {% endstepper %}

***

## Backup Recommendations Before Upgrading

Before every upgrade, IntellectEU recommends creating both a database backup and a Validator Identity Dump (IDDump). See [Validator Backups and Identity Dumps](/catalyx-blockchain-manager/canton-network/version-1.11/validator-management/identity-backup-and-recovery.md) for scheduling and restore procedures.

| Backup Type            | Preserves                                                                     | Does Not Preserve                                    |
| ---------------------- | ----------------------------------------------------------------------------- | ---------------------------------------------------- |
| Database Backup        | Validator database, participant database, ledger state, transaction history   | Validator identities and cryptographic keys          |
| Identity Dump (IDDump) | Validator identity, cryptographic keys, wallet identity, participant identity | Database contents, ledger state, transaction history |

{% hint style="warning" %}
For complete disaster recovery, both database backups and Identity Dumps should be available before performing an upgrade.
{% endhint %}

***

## Upgrade Best Practices

To minimize operational risk, IntellectEU recommends:

* Test upgrades in DevNet or TestNet before Production.
* Create a database backup.
* Create an Identity Dump.
* Review release notes.
* Perform upgrades during planned maintenance windows.
* Verify validator health immediately after the upgrade.
* Monitor logs until validator initialization completes successfully.

***

## Version Compatibility

Validator nodes should remain on a supported Canton version validated by IntellectEU.

Although older versions may continue operating for a period of time, remaining significantly behind the supported version increases operational risk and may eventually lead to incompatibility with newer network components.

Customers are encouraged to upgrade after IntellectEU validates and recommends a new release.

### Consequences of Running an Outdated Validator

If a validator remains on an older version after the Canton Network has moved forward, the following issues may occur:

* Application initialization failures.
* Package compatibility conflicts.
* Migration failures.
* Validator remaining in **Pending** state.
* Failure to join or synchronize with the network.
* Inability to deploy newer applications or packages.
* Reduced compatibility with newer Canton protocol features.
* Unsupported configuration for future incident resolution.

{% hint style="danger" %}
In some cases, the validator must be upgraded before normal operation can resume.
{% endhint %}

***

## Customer Communication Process

When a new supported validator version becomes available, IntellectEU typically follows this process:

1. Review the official Canton Foundation release.
2. Perform internal compatibility testing.
3. Validate upgrade and migration procedures.
4. Update operational documentation if required.
5. Notify customers of the recommended upgrade.
6. Schedule or assist with the upgrade.
7. Verify validator health after deployment.

***

## Frequently Asked Questions

<details>

<summary>How often should validator nodes be upgraded?</summary>

Validator nodes should be upgraded after IntellectEU has validated and recommended the corresponding Canton Foundation release. There is no fixed calendar for upgrades, as they depend on the Canton Foundation release schedule and the validation process performed by IntellectEU.

</details>

<details>

<summary>Does every upgrade require a migration?</summary>

No. Some releases only require updating the validator application version, while others introduce schema or application changes that require a migration. Migration requirements are documented as part of each supported release.

</details>

<details>

<summary>Can upgrades be rolled back?</summary>

Application versions can generally be reverted if necessary. However, migrations may introduce irreversible data changes. Always create a database backup and Identity Dump before upgrading to ensure recovery options are available.

</details>

<details>

<summary>How long does an upgrade take?</summary>

Upgrade duration depends on validator size, database size, whether migrations are required, and infrastructure performance. Most routine upgrades complete within a planned maintenance window.

</details>


---

# 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-1.11/validator-management/validator-upgrade-policy-and-release-schedule.md?ask=<question>&goal=<endgoal>
```

`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.