From 77caa2dba23ce6483b3a885e717e58b718abe7ed Mon Sep 17 00:00:00 2001 From: "github-actions[bot]" <41898282+github-actions[bot]@users.noreply.github.com> Date: Fri, 3 Jul 2026 06:15:43 +0000 Subject: [PATCH] Update generated docs Signed-off-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com> --- config/repo-version-config.json | 112 +++++++++--------- .../appdev/deep-dives/token-standard.mdx | 12 +- .../deployment/kubernetes-deployment.mdx | 66 +++++------ .../deployment/onboarding-process.mdx | 6 +- .../required-network-parameters.mdx | 6 +- .../deployment/sv-network-resets.mdx | 6 +- .../deployment/synchronizer-traffic.mdx | 6 +- .../deployment/validator-docker-compose.mdx | 30 ++--- .../deployment/validator-kubernetes.mdx | 42 +++---- .../validator-disaster-recovery.mdx | 12 +- .../reference/canton-console-reference.mdx | 48 ++++---- .../api-reference/splice-daml-apis.mdx | 12 +- .../api-reference/splice-http-apis.mdx | 12 +- .../splice-scan-bulk-data-api.mdx | 12 +- .../splice-scan-gs-connectivity-api.mdx | 6 +- .../generated/version-dashboard-data.mdx | 90 +++++++------- 16 files changed, 239 insertions(+), 239 deletions(-) diff --git a/config/repo-version-config.json b/config/repo-version-config.json index 1b4f1ec9b..5e18fc2c1 100644 --- a/config/repo-version-config.json +++ b/config/repo-version-config.json @@ -1,11 +1,11 @@ { "_generated": { - "generatedAt": "2026-06-22T14:22:07+00:00", + "generatedAt": "2026-07-03T06:15:24+00:00", "generatorMode": "public_source_collection_with_manual_fallbacks", "sourceContract": { "splice": "Network /info endpoint: MainNet https://docs.global.canton.network.sync.global/info, TestNet https://docs.test.global.canton.network.sync.global/info, DevNet https://docs.dev.global.canton.network.sync.global/info. Cross-check against the same network's /index.html Docker image tag and Helm chart version.", "canton": "Use the observed Splice version from the network /info endpoint, derive the matching canton-network/splice release-line branch, then read version from nix/canton-sources.json. The config key remains damlSdk for compatibility with the existing dashboard component.", - "damlSdkInstaller": "DPM installer channel: curl https://get.digitalasset.com/install/install.sh | sh; latest stable SDK from https://get.digitalasset.com/install/latest currently resolves to 3.5.1.", + "damlSdkInstaller": "DPM installer channel: curl https://get.digitalasset.com/install/install.sh | sh; latest stable SDK from https://get.digitalasset.com/install/latest currently resolves to 3.5.2.", "tokenStandard": "npm latest dist-tag for @canton-network/core-token-standard.", "walletSdk": "npm latest dist-tag for @canton-network/wallet-sdk.", "dappSdk": "npm latest dist-tag for @canton-network/dapp-sdk.", @@ -18,20 +18,20 @@ "mainnet": { "infoUrl": "https://docs.global.canton.network.sync.global/info", "indexUrl": "https://docs.global.canton.network.sync.global/index.html", - "cantonSourcesUrl": "https://github.com/canton-network/splice/blob/release-line-0.6.7/nix/canton-sources.json", - "darVersionsUrl": "https://github.com/canton-network/splice/blob/release-line-0.6.7/daml/dars.lock" + "cantonSourcesUrl": "https://github.com/canton-network/splice/blob/release-line-0.6.8/nix/canton-sources.json", + "darVersionsUrl": "https://github.com/canton-network/splice/blob/release-line-0.6.8/daml/dars.lock" }, "testnet": { "infoUrl": "https://docs.test.global.canton.network.sync.global/info", "indexUrl": "https://docs.test.global.canton.network.sync.global/index.html", - "cantonSourcesUrl": "https://github.com/canton-network/splice/blob/release-line-0.6.8/nix/canton-sources.json", - "darVersionsUrl": "https://github.com/canton-network/splice/blob/release-line-0.6.8/daml/dars.lock" + "cantonSourcesUrl": "https://github.com/canton-network/splice/blob/release-line-0.6.9/nix/canton-sources.json", + "darVersionsUrl": "https://github.com/canton-network/splice/blob/release-line-0.6.9/daml/dars.lock" }, "devnet": { "infoUrl": "https://docs.dev.global.canton.network.sync.global/info", "indexUrl": "https://docs.dev.global.canton.network.sync.global/index.html", - "cantonSourcesUrl": "https://github.com/canton-network/splice/blob/release-line-0.6.9/nix/canton-sources.json", - "darVersionsUrl": "https://github.com/canton-network/splice/blob/release-line-0.6.9/daml/dars.lock" + "cantonSourcesUrl": "https://github.com/canton-network/splice/blob/release-line-0.6.10/nix/canton-sources.json", + "darVersionsUrl": "https://github.com/canton-network/splice/blob/release-line-0.6.10/daml/dars.lock" } } }, @@ -55,7 +55,7 @@ "version": "0.1.25" } ], - "releaseUrl": "https://github.com/canton-network/splice/releases/tag/0.6.7" + "releaseUrl": "https://github.com/canton-network/splice/releases/tag/0.6.8" }, "endpoint": "scan.sv-1.global.canton.network.sync.global", "substitutions": { @@ -66,19 +66,19 @@ "gsf_scan_url": "https://scan.sv-1.global.canton.network.sync.global", "generic_scan_url": "https://scan.sv-1.global.canton.network.YOUR_SV_SPONSOR", "gsf_sequencer_url": "https://sequencer-MIGRATION_ID.sv-1.global.canton.network.sync.global", - "version": "0.6.7", - "version_literal": "0.6.7", - "chart_version_literal": "0.6.7", - "chart_version_set": "export CHART_VERSION=0.6.7", - "image_tag_set": "export IMAGE_TAG=0.6.7", - "image_tag_set_plain": "export IMAGE_TAG=0.6.7", + "version": "0.6.8", + "version_literal": "0.6.8", + "chart_version_literal": "0.6.8", + "chart_version_set": "export CHART_VERSION=0.6.8", + "image_tag_set": "export IMAGE_TAG=0.6.8", + "image_tag_set_plain": "export IMAGE_TAG=0.6.8", "bundle_download_link": { "label": "Download Bundle", - "href": "https://github.com/digital-asset/decentralized-canton-sync/releases/download/v0.6.7/0.6.7_splice-node.tar.gz" + "href": "https://github.com/digital-asset/decentralized-canton-sync/releases/download/v0.6.8/0.6.8_splice-node.tar.gz" }, "openapi_download_link": { "label": "Download OpenAPI specs", - "href": "https://github.com/digital-asset/decentralized-canton-sync/releases/download/v0.6.7/0.6.7_openapi.tar.gz" + "href": "https://github.com/digital-asset/decentralized-canton-sync/releases/download/v0.6.8/0.6.8_openapi.tar.gz" }, "helm_repo_prefix": "oci://ghcr.io/digital-asset/decentralized-canton-sync/helm", "docker_repo_prefix": "ghcr.io/digital-asset/decentralized-canton-sync/docker" @@ -92,18 +92,18 @@ "darVersions": [ { "name": "splice-amulet", - "version": "0.1.19" + "version": "0.1.20" }, { "name": "splice-wallet", - "version": "0.1.20" + "version": "0.1.21" }, { "name": "splice-dso-governance", - "version": "0.1.25" + "version": "0.1.26" } ], - "releaseUrl": "https://github.com/canton-network/splice/releases/tag/0.6.8" + "releaseUrl": "https://github.com/canton-network/splice/releases/tag/0.6.9" }, "endpoint": "scan.sv-1.test.global.canton.network.sync.global", "substitutions": { @@ -114,19 +114,19 @@ "gsf_scan_url": "https://scan.sv-1.test.global.canton.network.sync.global", "generic_scan_url": "https://scan.sv-1.test.global.canton.network.YOUR_SV_SPONSOR", "gsf_sequencer_url": "https://sequencer-MIGRATION_ID.sv-1.test.global.canton.network.sync.global", - "version": "0.6.8", - "version_literal": "0.6.8", - "chart_version_literal": "0.6.8", - "chart_version_set": "export CHART_VERSION=0.6.8", - "image_tag_set": "export IMAGE_TAG=0.6.8", - "image_tag_set_plain": "export IMAGE_TAG=0.6.8", + "version": "0.6.9", + "version_literal": "0.6.9", + "chart_version_literal": "0.6.9", + "chart_version_set": "export CHART_VERSION=0.6.9", + "image_tag_set": "export IMAGE_TAG=0.6.9", + "image_tag_set_plain": "export IMAGE_TAG=0.6.9", "bundle_download_link": { "label": "Download Bundle", - "href": "https://github.com/digital-asset/decentralized-canton-sync/releases/download/v0.6.8/0.6.8_splice-node.tar.gz" + "href": "https://github.com/digital-asset/decentralized-canton-sync/releases/download/v0.6.9/0.6.9_splice-node.tar.gz" }, "openapi_download_link": { "label": "Download OpenAPI specs", - "href": "https://github.com/digital-asset/decentralized-canton-sync/releases/download/v0.6.8/0.6.8_openapi.tar.gz" + "href": "https://github.com/digital-asset/decentralized-canton-sync/releases/download/v0.6.9/0.6.9_openapi.tar.gz" }, "helm_repo_prefix": "oci://ghcr.io/digital-asset/decentralized-canton-sync/helm", "docker_repo_prefix": "ghcr.io/digital-asset/decentralized-canton-sync/docker" @@ -151,7 +151,7 @@ "version": "0.1.26" } ], - "releaseUrl": "https://github.com/canton-network/splice/releases/tag/0.6.9" + "releaseUrl": "https://github.com/canton-network/splice/releases/tag/0.6.10" }, "endpoint": "scan.sv-1.dev.global.canton.network.sync.global", "substitutions": { @@ -162,19 +162,19 @@ "gsf_scan_url": "https://scan.sv-1.dev.global.canton.network.sync.global", "generic_scan_url": "https://scan.sv-1.dev.global.canton.network.YOUR_SV_SPONSOR", "gsf_sequencer_url": "https://sequencer-MIGRATION_ID.sv-1.dev.global.canton.network.sync.global", - "version": "0.6.9", - "version_literal": "0.6.9", - "chart_version_literal": "0.6.9", - "chart_version_set": "export CHART_VERSION=0.6.9", - "image_tag_set": "export IMAGE_TAG=0.6.9", - "image_tag_set_plain": "export IMAGE_TAG=0.6.9", + "version": "0.6.10", + "version_literal": "0.6.10", + "chart_version_literal": "0.6.10", + "chart_version_set": "export CHART_VERSION=0.6.10", + "image_tag_set": "export IMAGE_TAG=0.6.10", + "image_tag_set_plain": "export IMAGE_TAG=0.6.10", "bundle_download_link": { "label": "Download Bundle", - "href": "https://github.com/digital-asset/decentralized-canton-sync/releases/download/v0.6.9/0.6.9_splice-node.tar.gz" + "href": "https://github.com/digital-asset/decentralized-canton-sync/releases/download/v0.6.10/0.6.10_splice-node.tar.gz" }, "openapi_download_link": { "label": "Download OpenAPI specs", - "href": "https://github.com/digital-asset/decentralized-canton-sync/releases/download/v0.6.9/0.6.9_openapi.tar.gz" + "href": "https://github.com/digital-asset/decentralized-canton-sync/releases/download/v0.6.10/0.6.10_openapi.tar.gz" }, "helm_repo_prefix": "oci://ghcr.io/digital-asset/decentralized-canton-sync/helm", "docker_repo_prefix": "ghcr.io/digital-asset/decentralized-canton-sync/docker" @@ -187,17 +187,17 @@ "versionMapping": { "mainnet": { "branch": "main", - "externalVersion": "0.6.7", + "externalVersion": "0.6.8", "folderPathRepo": "splice-wallet-kernel" }, "testnet": { "branch": "main", - "externalVersion": "0.6.8", + "externalVersion": "0.6.9", "folderPathRepo": "splice-wallet-kernel" }, "devnet": { "branch": "main", - "externalVersion": "0.6.9", + "externalVersion": "0.6.10", "folderPathRepo": "splice-wallet-kernel" } } @@ -206,19 +206,19 @@ "url": "https://github.com/canton-network/splice", "versionMapping": { "mainnet": { - "branch": "release-line-0.6.7", - "externalVersion": "3.5.3", - "folderPathRepo": "nix/canton-sources.json" - }, - "testnet": { "branch": "release-line-0.6.8", "externalVersion": "3.5.4", "folderPathRepo": "nix/canton-sources.json" }, - "devnet": { + "testnet": { "branch": "release-line-0.6.9", "externalVersion": "3.5.5", "folderPathRepo": "nix/canton-sources.json" + }, + "devnet": { + "branch": "release-line-0.6.10", + "externalVersion": "3.5.6", + "folderPathRepo": "nix/canton-sources.json" } } }, @@ -247,17 +247,17 @@ "versionMapping": { "mainnet": { "branch": "", - "externalVersion": "1.6.1", + "externalVersion": "1.7.0", "folderPathRepo": "" }, "testnet": { "branch": "", - "externalVersion": "1.6.1", + "externalVersion": "1.7.0", "folderPathRepo": "" }, "devnet": { "branch": "", - "externalVersion": "1.6.1", + "externalVersion": "1.7.0", "folderPathRepo": "" } } @@ -287,17 +287,17 @@ "versionMapping": { "mainnet": { "branch": "", - "externalVersion": "1.2.0", + "externalVersion": "1.3.0", "folderPathRepo": "" }, "testnet": { "branch": "", - "externalVersion": "1.2.0", + "externalVersion": "1.3.0", "folderPathRepo": "" }, "devnet": { "branch": "", - "externalVersion": "1.2.0", + "externalVersion": "1.3.0", "folderPathRepo": "" } } @@ -307,17 +307,17 @@ "versionMapping": { "mainnet": { "branch": "", - "externalVersion": "1.4.0", + "externalVersion": "1.5.0", "folderPathRepo": "@canton-network/wallet-gateway-remote" }, "testnet": { "branch": "", - "externalVersion": "1.4.0", + "externalVersion": "1.5.0", "folderPathRepo": "@canton-network/wallet-gateway-remote" }, "devnet": { "branch": "", - "externalVersion": "1.4.0", + "externalVersion": "1.5.0", "folderPathRepo": "@canton-network/wallet-gateway-remote" } } diff --git a/docs-main/appdev/deep-dives/token-standard.mdx b/docs-main/appdev/deep-dives/token-standard.mdx index 5dec0631e..82b7b311e 100644 --- a/docs-main/appdev/deep-dives/token-standard.mdx +++ b/docs-main/appdev/deep-dives/token-standard.mdx @@ -35,33 +35,33 @@ We recommend wallet providers to implement a UTXO management strategy that: {/* NETWORKVARS_START source="/snippets/networkvars/appdev/deep-dives/token-standard-1.mdx" */} - + Assuming you are a wallet provider that runs a validator node for your users, you can set up `MergeDelegation` contracts for your users as follows. -1. Extract the latest version of the `splice-util-token-standard-wallet.dar` file from the release bundle (Download Bundle (DevNet 0.6.9)). +1. Extract the latest version of the `splice-util-token-standard-wallet.dar` file from the release bundle (Download Bundle (DevNet 0.6.10)). 2. Upload the extracted `.dar` file to your validator node. 3. Adjust your user onboarding procedure such that the users signs the creation of a `MergeDelegationProposal` contract (see docs). 4. Accept the `MergeDelegationProposal` contracts by exercising their `Accept` choice using your wallet provider's party. - + Assuming you are a wallet provider that runs a validator node for your users, you can set up `MergeDelegation` contracts for your users as follows. -1. Extract the latest version of the `splice-util-token-standard-wallet.dar` file from the release bundle (Download Bundle (TestNet 0.6.8)). +1. Extract the latest version of the `splice-util-token-standard-wallet.dar` file from the release bundle (Download Bundle (TestNet 0.6.9)). 2. Upload the extracted `.dar` file to your validator node. 3. Adjust your user onboarding procedure such that the users signs the creation of a `MergeDelegationProposal` contract (see docs). 4. Accept the `MergeDelegationProposal` contracts by exercising their `Accept` choice using your wallet provider's party. - + Assuming you are a wallet provider that runs a validator node for your users, you can set up `MergeDelegation` contracts for your users as follows. -1. Extract the latest version of the `splice-util-token-standard-wallet.dar` file from the release bundle (Download Bundle (MainNet 0.6.7)). +1. Extract the latest version of the `splice-util-token-standard-wallet.dar` file from the release bundle (Download Bundle (MainNet 0.6.8)). 2. Upload the extracted `.dar` file to your validator node. 3. Adjust your user onboarding procedure such that the users signs the creation of a `MergeDelegationProposal` contract (see docs). 4. Accept the `MergeDelegationProposal` contracts by exercising their `Accept` choice using your wallet provider's party. diff --git a/docs-main/global-synchronizer/deployment/kubernetes-deployment.mdx b/docs-main/global-synchronizer/deployment/kubernetes-deployment.mdx index dd642114a..573c92e85 100644 --- a/docs-main/global-synchronizer/deployment/kubernetes-deployment.mdx +++ b/docs-main/global-synchronizer/deployment/kubernetes-deployment.mdx @@ -37,7 +37,7 @@ This section describes deploying a Super Validator (SV) node in kubernetes using {/* NETWORKVARS_START source="/snippets/networkvars/global-synchronizer/deployment/kubernetes-deployment-1.mdx" */} - + 1) A running Kubernetes cluster in which you have administrator access to create and manage namespaces. @@ -48,10 +48,10 @@ This section describes deploying a Super Validator (SV) node in kubernetes using 3) Your cluster needs a static egress IP. After acquiring that, propose to the other SVs to add it to the IP allowlist. -4) Please download the release artifacts containing the sample Helm value files, from here: Download Bundle (DevNet 0.6.9), and extract the bundle: +4) Please download the release artifacts containing the sample Helm value files, from here: Download Bundle (DevNet 0.6.10), and extract the bundle: ```bash -tar xzvf 0.6.9_splice-node.tar.gz +tar xzvf 0.6.10_splice-node.tar.gz ``` 5) Please inquire the migration id and serial id of the global synchronizer on your target network. The migration ID is frozen at the value after the last major upgrade and is only used for `migration.id` in the helm chart values. The serial ID is 0 for the initial synchronizer deployment and is incremented by 1 for each [logical synchronizer upgrade](/global-synchronizer/production-operations/logical-synchronizer-upgrade). The serial ID is used for helm release names, DNS entries, database names, and deployment naming. @@ -82,7 +82,7 @@ you can only rely on your own backups. - + 1) A running Kubernetes cluster in which you have administrator access to create and manage namespaces. @@ -93,10 +93,10 @@ you can only rely on your own backups. 3) Your cluster needs a static egress IP. After acquiring that, propose to the other SVs to add it to the IP allowlist. -4) Please download the release artifacts containing the sample Helm value files, from here: Download Bundle (TestNet 0.6.8), and extract the bundle: +4) Please download the release artifacts containing the sample Helm value files, from here: Download Bundle (TestNet 0.6.9), and extract the bundle: ```bash -tar xzvf 0.6.8_splice-node.tar.gz +tar xzvf 0.6.9_splice-node.tar.gz ``` 5) Please inquire the migration id and serial id of the global synchronizer on your target network. The migration ID is frozen at the value after the last major upgrade and is only used for `migration.id` in the helm chart values. The serial ID is 0 for the initial synchronizer deployment and is incremented by 1 for each [logical synchronizer upgrade](/global-synchronizer/production-operations/logical-synchronizer-upgrade). The serial ID is used for helm release names, DNS entries, database names, and deployment naming. @@ -127,7 +127,7 @@ you can only rely on your own backups. - + 1) A running Kubernetes cluster in which you have administrator access to create and manage namespaces. @@ -138,10 +138,10 @@ you can only rely on your own backups. 3) Your cluster needs a static egress IP. After acquiring that, propose to the other SVs to add it to the IP allowlist. -4) Please download the release artifacts containing the sample Helm value files, from here: Download Bundle (MainNet 0.6.7), and extract the bundle: +4) Please download the release artifacts containing the sample Helm value files, from here: Download Bundle (MainNet 0.6.8), and extract the bundle: ```bash -tar xzvf 0.6.7_splice-node.tar.gz +tar xzvf 0.6.8_splice-node.tar.gz ``` 5) Please inquire the migration id and serial id of the global synchronizer on your target network. The migration ID is frozen at the value after the last major upgrade and is only used for `migration.id` in the helm chart values. The serial ID is 0 for the initial synchronizer deployment and is incremented by 1 for each [logical synchronizer upgrade](/global-synchronizer/production-operations/logical-synchronizer-upgrade). The serial ID is used for helm release names, DNS entries, database names, and deployment naming. @@ -354,7 +354,7 @@ Every SV node also deploys a CometBFT node. This node must be configured to join {/* NETWORKVARS_START source="/snippets/networkvars/global-synchronizer/deployment/kubernetes-deployment-2.mdx" */} - + To generate the node config you use the CometBFT docker image provided through Github Container Registry (ghcr.io/digital-asset/decentralized-canton-sync/docker). @@ -365,9 +365,9 @@ Use the following shell commands to generate the proper keys: mkdir cometbft cd cometbft # Init the node -docker run --rm -v "$(pwd):/init" ghcr.io/digital-asset/decentralized-canton-sync/docker/cometbft:0.6.9 init --home /init +docker run --rm -v "$(pwd):/init" ghcr.io/digital-asset/decentralized-canton-sync/docker/cometbft:0.6.10 init --home /init # Read the node id and keep a note of it for the deployment -docker run --rm -v "$(pwd):/init" ghcr.io/digital-asset/decentralized-canton-sync/docker/cometbft:0.6.9 show-node-id --home /init +docker run --rm -v "$(pwd):/init" ghcr.io/digital-asset/decentralized-canton-sync/docker/cometbft:0.6.10 show-node-id --home /init ``` Please keep a note of the node ID printed out above. @@ -381,7 +381,7 @@ Any other files can be ignored. - + To generate the node config you use the CometBFT docker image provided through Github Container Registry (ghcr.io/digital-asset/decentralized-canton-sync/docker). @@ -392,9 +392,9 @@ Use the following shell commands to generate the proper keys: mkdir cometbft cd cometbft # Init the node -docker run --rm -v "$(pwd):/init" ghcr.io/digital-asset/decentralized-canton-sync/docker/cometbft:0.6.8 init --home /init +docker run --rm -v "$(pwd):/init" ghcr.io/digital-asset/decentralized-canton-sync/docker/cometbft:0.6.9 init --home /init # Read the node id and keep a note of it for the deployment -docker run --rm -v "$(pwd):/init" ghcr.io/digital-asset/decentralized-canton-sync/docker/cometbft:0.6.8 show-node-id --home /init +docker run --rm -v "$(pwd):/init" ghcr.io/digital-asset/decentralized-canton-sync/docker/cometbft:0.6.9 show-node-id --home /init ``` Please keep a note of the node ID printed out above. @@ -408,7 +408,7 @@ Any other files can be ignored. - + To generate the node config you use the CometBFT docker image provided through Github Container Registry (ghcr.io/digital-asset/decentralized-canton-sync/docker). @@ -419,9 +419,9 @@ Use the following shell commands to generate the proper keys: mkdir cometbft cd cometbft # Init the node -docker run --rm -v "$(pwd):/init" ghcr.io/digital-asset/decentralized-canton-sync/docker/cometbft:0.6.7 init --home /init +docker run --rm -v "$(pwd):/init" ghcr.io/digital-asset/decentralized-canton-sync/docker/cometbft:0.6.8 init --home /init # Read the node id and keep a note of it for the deployment -docker run --rm -v "$(pwd):/init" ghcr.io/digital-asset/decentralized-canton-sync/docker/cometbft:0.6.7 show-node-id --home /init +docker run --rm -v "$(pwd):/init" ghcr.io/digital-asset/decentralized-canton-sync/docker/cometbft:0.6.8 show-node-id --home /init ``` Please keep a note of the node ID printed out above. @@ -508,7 +508,7 @@ All apps support reading the Postgres password from a Kubernetes secret. Current {/* NETWORKVARS_START source="/snippets/networkvars/global-synchronizer/deployment/kubernetes-deployment-3.mdx" */} - + If you wish to run the Postgres instances as pods in your cluster, you can use the `splice-postgres` Helm chart to install them: @@ -521,7 +521,7 @@ helm install apps-pg oci://ghcr.io/digital-asset/decentralized-canton-sync/helm/ - + If you wish to run the Postgres instances as pods in your cluster, you can use the `splice-postgres` Helm chart to install them: @@ -534,7 +534,7 @@ helm install apps-pg oci://ghcr.io/digital-asset/decentralized-canton-sync/helm/ - + If you wish to run the Postgres instances as pods in your cluster, you can use the `splice-postgres` Helm chart to install them: @@ -579,12 +579,12 @@ To remove it, set `enableReloader: false` in your Helm values file. {/* NETWORKVARS_START source="/snippets/networkvars/global-synchronizer/deployment/kubernetes-deployment-4.mdx" */} - + To install the Helm charts needed to start an SV node connected to the cluster, you will need to meet a few preconditions. The first is that there needs to be an environment variable defined to refer to the version of the Helm charts necessary to connect to this environment: ```bash -export CHART_VERSION=0.6.9 +export CHART_VERSION=0.6.10 ``` Unless CantonBFT is being used, you also need to configure a CometBFT node for your SV. Please modify the file `splice-node/examples/sv-helm/cometbft-values.yaml` as follows: @@ -697,12 +697,12 @@ These environment variables will be used below. - + To install the Helm charts needed to start an SV node connected to the cluster, you will need to meet a few preconditions. The first is that there needs to be an environment variable defined to refer to the version of the Helm charts necessary to connect to this environment: ```bash -export CHART_VERSION=0.6.8 +export CHART_VERSION=0.6.9 ``` Unless CantonBFT is being used, you also need to configure a CometBFT node for your SV. Please modify the file `splice-node/examples/sv-helm/cometbft-values.yaml` as follows: @@ -815,12 +815,12 @@ These environment variables will be used below. - + To install the Helm charts needed to start an SV node connected to the cluster, you will need to meet a few preconditions. The first is that there needs to be an environment variable defined to refer to the version of the Helm charts necessary to connect to this environment: ```bash -export CHART_VERSION=0.6.7 +export CHART_VERSION=0.6.8 ``` Unless CantonBFT is being used, you also need to configure a CometBFT node for your SV. Please modify the file `splice-node/examples/sv-helm/cometbft-values.yaml` as follows: @@ -941,7 +941,7 @@ These environment variables will be used below. {/* NETWORKVARS_START source="/snippets/networkvars/global-synchronizer/deployment/kubernetes-deployment-5.mdx" */} - + With these files in place, you can execute the following helm commands in sequence. It's generally a good idea to wait until each deployment reaches a stable state prior to moving on to the next step. @@ -996,7 +996,7 @@ Note also that `Pod` restarts may happen during bringup, particularly if all hel - + With these files in place, you can execute the following helm commands in sequence. It's generally a good idea to wait until each deployment reaches a stable state prior to moving on to the next step. @@ -1051,7 +1051,7 @@ Note also that `Pod` restarts may happen during bringup, particularly if all hel - + With these files in place, you can execute the following helm commands in sequence. It's generally a good idea to wait until each deployment reaches a stable state prior to moving on to the next step. @@ -1186,7 +1186,7 @@ In order to install the reference charts, the following must be satisfied in you {/* NETWORKVARS_START source="/snippets/networkvars/global-synchronizer/deployment/kubernetes-deployment-6.mdx" */} - + Create a `cluster-ingress` namespace: @@ -1308,7 +1308,7 @@ helm install cluster-ingress-sv oci://ghcr.io/digital-asset/decentralized-canton - + Create a `cluster-ingress` namespace: @@ -1430,7 +1430,7 @@ helm install cluster-ingress-sv oci://ghcr.io/digital-asset/decentralized-canton - + Create a `cluster-ingress` namespace: diff --git a/docs-main/global-synchronizer/deployment/onboarding-process.mdx b/docs-main/global-synchronizer/deployment/onboarding-process.mdx index ae338ceda..078199a01 100644 --- a/docs-main/global-synchronizer/deployment/onboarding-process.mdx +++ b/docs-main/global-synchronizer/deployment/onboarding-process.mdx @@ -36,7 +36,7 @@ Onboarding a Validator involves the following steps (for each network you want t {/* NETWORKVARS_START source="/snippets/networkvars/global-synchronizer/deployment/onboarding-process-1.mdx" */} - + To validate that the SVs have added you to their respective IP allowlists, you can query their Scan URLs. Note that this must be run from the same egress IP from which you want to deploy your validator, e.g., from the VM that you want to run your docker compose setup on, or from within your Kubernetes cluster. @@ -118,7 +118,7 @@ The default configuration for both of these requires access to at least 2/3 of t - + To validate that the SVs have added you to their respective IP allowlists, you can query their Scan URLs. Note that this must be run from the same egress IP from which you want to deploy your validator, e.g., from the VM that you want to run your docker compose setup on, or from within your Kubernetes cluster. @@ -200,7 +200,7 @@ The default configuration for both of these requires access to at least 2/3 of t - + To validate that the SVs have added you to their respective IP allowlists, you can query their Scan URLs. Note that this must be run from the same egress IP from which you want to deploy your validator, e.g., from the VM that you want to run your docker compose setup on, or from within your Kubernetes cluster. diff --git a/docs-main/global-synchronizer/deployment/required-network-parameters.mdx b/docs-main/global-synchronizer/deployment/required-network-parameters.mdx index c1ff4e1a0..744a32385 100644 --- a/docs-main/global-synchronizer/deployment/required-network-parameters.mdx +++ b/docs-main/global-synchronizer/deployment/required-network-parameters.mdx @@ -8,7 +8,7 @@ description: "Parameters required to initialise a validator node and connect to {/* NETWORKVARS_START source="/snippets/networkvars/global-synchronizer/deployment/required-network-parameters-1.mdx" */} - + To initialize your validator node, you need the following parameters that define the network you're onboarding to and the secret required for doing so. @@ -34,7 +34,7 @@ Note that this self-served secret is only valid for 1 hour. - + To initialize your validator node, you need the following parameters that define the network you're onboarding to and the secret required for doing so. @@ -46,7 +46,7 @@ The onboarding secret provided by your sponsor. If you don't already have one, a - + To initialize your validator node, you need the following parameters that define the network you're onboarding to and the secret required for doing so. diff --git a/docs-main/global-synchronizer/deployment/sv-network-resets.mdx b/docs-main/global-synchronizer/deployment/sv-network-resets.mdx index 62e5f7a9f..adda00c54 100644 --- a/docs-main/global-synchronizer/deployment/sv-network-resets.mdx +++ b/docs-main/global-synchronizer/deployment/sv-network-resets.mdx @@ -8,7 +8,7 @@ description: "Handling DevNet and TestNet resets on Super Validator nodes" {/* NETWORKVARS_START source="/snippets/networkvars/global-synchronizer/deployment/sv-network-resets-1.mdx" */} - + DevNet and TestNet get reset roughly every 3 months with the resets spread out such that they never happen at the same time on DevNet and TestNet. The exact time is announced in the `#supervalidator-operations` channel run by the [Global Synchronizer Foundation](https://sync.global/). @@ -85,7 +85,7 @@ To complete the reset, go through the following steps: - + DevNet and TestNet get reset roughly every 3 months with the resets spread out such that they never happen at the same time on DevNet and TestNet. The exact time is announced in the `#supervalidator-operations` channel run by the [Global Synchronizer Foundation](https://sync.global/). @@ -162,7 +162,7 @@ To complete the reset, go through the following steps: - + DevNet and TestNet get reset roughly every 3 months with the resets spread out such that they never happen at the same time on DevNet and TestNet. The exact time is announced in the `#supervalidator-operations` channel run by the [Global Synchronizer Foundation](https://sync.global/). diff --git a/docs-main/global-synchronizer/deployment/synchronizer-traffic.mdx b/docs-main/global-synchronizer/deployment/synchronizer-traffic.mdx index 03b9cace9..01d4b6793 100644 --- a/docs-main/global-synchronizer/deployment/synchronizer-traffic.mdx +++ b/docs-main/global-synchronizer/deployment/synchronizer-traffic.mdx @@ -39,7 +39,7 @@ Traffic accounting is "by participant"; all parties hosted on the same participa {/* NETWORKVARS_START source="/snippets/networkvars/global-synchronizer/deployment/synchronizer-traffic-1.mdx" */} - + The current synchronizer traffic parameters are recorded on the global `AmuletRules` contract and can be obtained from Scan. You can obtain them via the Scan UI or by querying the Scan API using, for example, this command (requires installing [jq](https://jqlang.org/)): @@ -78,7 +78,7 @@ Like all parts of the `AmuletRulesConfig`, the `SynchronizerFeesConfig` is set b - + The current synchronizer traffic parameters are recorded on the global `AmuletRules` contract and can be obtained from Scan. You can obtain them via the Scan UI or by querying the Scan API using, for example, this command (requires installing [jq](https://jqlang.org/)): @@ -117,7 +117,7 @@ Like all parts of the `AmuletRulesConfig`, the `SynchronizerFeesConfig` is set b - + The current synchronizer traffic parameters are recorded on the global `AmuletRules` contract and can be obtained from Scan. You can obtain them via the Scan UI or by querying the Scan API using, for example, this command (requires installing [jq](https://jqlang.org/)): diff --git a/docs-main/global-synchronizer/deployment/validator-docker-compose.mdx b/docs-main/global-synchronizer/deployment/validator-docker-compose.mdx index 4ca4f7dc4..223003f59 100644 --- a/docs-main/global-synchronizer/deployment/validator-docker-compose.mdx +++ b/docs-main/global-synchronizer/deployment/validator-docker-compose.mdx @@ -33,7 +33,7 @@ This deployment is useful for: {/* NETWORKVARS_START source="/snippets/networkvars/global-synchronizer/deployment/validator-docker-compose-1.mdx" */} - + 1) A linux/MacOS machine with the following: @@ -57,10 +57,10 @@ Features: alt-svc AsynchDNS brotli GSS-API HSTS HTTP2 HTTPS-proxy IDN IPv6 Kerbe jq-1.7.1 ``` 2) Your machine should either be connected to a VPN that is whitelisted on the network (contact your sponsor SV to obtain access), or have a static egress IP address. In the latter case, please provide that IP address to your sponsor SV to add it to the firewall rules. -3) Please download the release artifacts containing the docker-compose files, from here: Download Bundle (DevNet 0.6.9), and extract the bundle: +3) Please download the release artifacts containing the docker-compose files, from here: Download Bundle (DevNet 0.6.10), and extract the bundle: ```bash -tar xzvf 0.6.9_splice-node.tar.gz +tar xzvf 0.6.10_splice-node.tar.gz ``` @@ -122,7 +122,7 @@ Additional parameters describing your own setup as opposed to the connection to - + 1) A linux/MacOS machine with the following: @@ -146,10 +146,10 @@ Features: alt-svc AsynchDNS brotli GSS-API HSTS HTTP2 HTTPS-proxy IDN IPv6 Kerbe jq-1.7.1 ``` 2) Your machine should either be connected to a VPN that is whitelisted on the network (contact your sponsor SV to obtain access), or have a static egress IP address. In the latter case, please provide that IP address to your sponsor SV to add it to the firewall rules. -3) Please download the release artifacts containing the docker-compose files, from here: Download Bundle (TestNet 0.6.8), and extract the bundle: +3) Please download the release artifacts containing the docker-compose files, from here: Download Bundle (TestNet 0.6.9), and extract the bundle: ```bash -tar xzvf 0.6.8_splice-node.tar.gz +tar xzvf 0.6.9_splice-node.tar.gz ``` @@ -190,7 +190,7 @@ Additional parameters describing your own setup as opposed to the connection to - + 1) A linux/MacOS machine with the following: @@ -214,10 +214,10 @@ Features: alt-svc AsynchDNS brotli GSS-API HSTS HTTP2 HTTPS-proxy IDN IPv6 Kerbe jq-1.7.1 ``` 2) Your machine should either be connected to a VPN that is whitelisted on the network (contact your sponsor SV to obtain access), or have a static egress IP address. In the latter case, please provide that IP address to your sponsor SV to add it to the firewall rules. -3) Please download the release artifacts containing the docker-compose files, from here: Download Bundle (MainNet 0.6.7), and extract the bundle: +3) Please download the release artifacts containing the docker-compose files, from here: Download Bundle (MainNet 0.6.8), and extract the bundle: ```bash -tar xzvf 0.6.7_splice-node.tar.gz +tar xzvf 0.6.8_splice-node.tar.gz ``` @@ -299,14 +299,14 @@ Example that proxies external [traffic](/global-synchronizer/deployment/synchron {/* NETWORKVARS_START source="/snippets/networkvars/global-synchronizer/deployment/validator-docker-compose-2.mdx" */} - + 1) Change to the `docker-compose` directory inside the extracted bundle: ```bash cd splice-node/docker-compose/validator ``` -2) Export the current version to an environment variable: export IMAGE_TAG=0.6.9 +2) Export the current version to an environment variable: export IMAGE_TAG=0.6.10 3) Run the following command to start the validator node, and wait for it to become ready (could take a few minutes): > ```bash @@ -326,14 +326,14 @@ Note that the validator may be stopped with the command `./stop.sh` and restarte - + 1) Change to the `docker-compose` directory inside the extracted bundle: ```bash cd splice-node/docker-compose/validator ``` -2) Export the current version to an environment variable: export IMAGE_TAG=0.6.8 +2) Export the current version to an environment variable: export IMAGE_TAG=0.6.9 3) Run the following command to start the validator node, and wait for it to become ready (could take a few minutes): > ```bash @@ -353,14 +353,14 @@ Note that the validator may be stopped with the command `./stop.sh` and restarte - + 1) Change to the `docker-compose` directory inside the extracted bundle: ```bash cd splice-node/docker-compose/validator ``` -2) Export the current version to an environment variable: export IMAGE_TAG=0.6.7 +2) Export the current version to an environment variable: export IMAGE_TAG=0.6.8 3) Run the following command to start the validator node, and wait for it to become ready (could take a few minutes): > ```bash diff --git a/docs-main/global-synchronizer/deployment/validator-kubernetes.mdx b/docs-main/global-synchronizer/deployment/validator-kubernetes.mdx index 4ee71c501..f0d673411 100644 --- a/docs-main/global-synchronizer/deployment/validator-kubernetes.mdx +++ b/docs-main/global-synchronizer/deployment/validator-kubernetes.mdx @@ -32,7 +32,7 @@ This section describes how to deploy a standalone validator node in Kubernetes u {/* NETWORKVARS_START source="/snippets/networkvars/global-synchronizer/deployment/validator-kubernetes-1.mdx" */} - + 1) A running Kubernetes cluster in which you have administrator access to create and manage namespaces. @@ -43,10 +43,10 @@ This section describes how to deploy a standalone validator node in Kubernetes u 3) Your cluster needs a static egress IP. After acquiring that, provide it to your SV sponsor who will propose adding it to the IP allowlist to the other SVs. -4) Please download the release artifacts containing the sample Helm value files, from here: Download Bundle (DevNet 0.6.9), and extract the bundle: +4) Please download the release artifacts containing the sample Helm value files, from here: Download Bundle (DevNet 0.6.10), and extract the bundle: ```bash -tar xzvf 0.6.9_splice-node.tar.gz +tar xzvf 0.6.10_splice-node.tar.gz ``` @@ -108,7 +108,7 @@ Additional parameters describing your own setup as opposed to the connection to - + 1) A running Kubernetes cluster in which you have administrator access to create and manage namespaces. @@ -119,10 +119,10 @@ Additional parameters describing your own setup as opposed to the connection to 3) Your cluster needs a static egress IP. After acquiring that, provide it to your SV sponsor who will propose adding it to the IP allowlist to the other SVs. -4) Please download the release artifacts containing the sample Helm value files, from here: Download Bundle (TestNet 0.6.8), and extract the bundle: +4) Please download the release artifacts containing the sample Helm value files, from here: Download Bundle (TestNet 0.6.9), and extract the bundle: ```bash -tar xzvf 0.6.8_splice-node.tar.gz +tar xzvf 0.6.9_splice-node.tar.gz ``` @@ -163,7 +163,7 @@ Additional parameters describing your own setup as opposed to the connection to - + 1) A running Kubernetes cluster in which you have administrator access to create and manage namespaces. @@ -174,10 +174,10 @@ Additional parameters describing your own setup as opposed to the connection to 3) Your cluster needs a static egress IP. After acquiring that, provide it to your SV sponsor who will propose adding it to the IP allowlist to the other SVs. -4) Please download the release artifacts containing the sample Helm value files, from here: Download Bundle (MainNet 0.6.7), and extract the bundle: +4) Please download the release artifacts containing the sample Helm value files, from here: Download Bundle (MainNet 0.6.8), and extract the bundle: ```bash -tar xzvf 0.6.7_splice-node.tar.gz +tar xzvf 0.6.8_splice-node.tar.gz ``` @@ -446,12 +446,12 @@ To remove it, set `enableReloader: false` in your Helm values file. {/* NETWORKVARS_START source="/snippets/networkvars/global-synchronizer/deployment/validator-kubernetes-2.mdx" */} - + To install the Helm charts needed to start a Validator node connected to the cluster, you will need to meet a few preconditions. The first is that there needs to be an environment variable defined to refer to the version of the Helm charts necessary to connect to this environment: ```bash -export CHART_VERSION=0.6.9 +export CHART_VERSION=0.6.10 ``` Please modify the file `splice-node/examples/sv-helm/participant-values.yaml` as follows: @@ -557,12 +557,12 @@ Finally, please download the UI config values file from [https://github.com/glob - + To install the Helm charts needed to start a Validator node connected to the cluster, you will need to meet a few preconditions. The first is that there needs to be an environment variable defined to refer to the version of the Helm charts necessary to connect to this environment: ```bash -export CHART_VERSION=0.6.8 +export CHART_VERSION=0.6.9 ``` Please modify the file `splice-node/examples/sv-helm/participant-values.yaml` as follows: @@ -668,12 +668,12 @@ Finally, please download the UI config values file from [https://github.com/glob - + To install the Helm charts needed to start a Validator node connected to the cluster, you will need to meet a few preconditions. The first is that there needs to be an environment variable defined to refer to the version of the Helm charts necessary to connect to this environment: ```bash -export CHART_VERSION=0.6.7 +export CHART_VERSION=0.6.8 ``` Please modify the file `splice-node/examples/sv-helm/participant-values.yaml` as follows: @@ -787,7 +787,7 @@ Finally, please download the UI config values file from [https://github.com/glob {/* NETWORKVARS_START source="/snippets/networkvars/global-synchronizer/deployment/validator-kubernetes-3.mdx" */} - + With these files in place, you can execute the following helm commands in sequence. It's generally a good idea to wait until each deployment reaches a stable state prior to moving on to the next step. @@ -811,7 +811,7 @@ Note also that `Pod` restarts may happen during bringup, particularly if all hel - + With these files in place, you can execute the following helm commands in sequence. It's generally a good idea to wait until each deployment reaches a stable state prior to moving on to the next step. @@ -835,7 +835,7 @@ Note also that `Pod` restarts may happen during bringup, particularly if all hel - + With these files in place, you can execute the following helm commands in sequence. It's generally a good idea to wait until each deployment reaches a stable state prior to moving on to the next step. @@ -902,7 +902,7 @@ In order to install the reference charts, the following must be satisfied in you {/* NETWORKVARS_START source="/snippets/networkvars/global-synchronizer/deployment/validator-kubernetes-4.mdx" */} - + Create a `cluster-ingress` namespace: @@ -991,7 +991,7 @@ helm install cluster-ingress-validator oci://ghcr.io/digital-asset/decentralized - + Create a `cluster-ingress` namespace: @@ -1080,7 +1080,7 @@ helm install cluster-ingress-validator oci://ghcr.io/digital-asset/decentralized - + Create a `cluster-ingress` namespace: diff --git a/docs-main/global-synchronizer/production-operations/validator-disaster-recovery.mdx b/docs-main/global-synchronizer/production-operations/validator-disaster-recovery.mdx index 3deddf2d3..62f1deeed 100644 --- a/docs-main/global-synchronizer/production-operations/validator-disaster-recovery.mdx +++ b/docs-main/global-synchronizer/production-operations/validator-disaster-recovery.mdx @@ -135,7 +135,7 @@ In some cases you might want to force the migration attempt for a set of parties {/* NETWORKVARS_START source="/snippets/networkvars/global-synchronizer/production-operations/validator-disaster-recovery-1.mdx" */} - + If you still observe issues, in particular you observe `ACS_COMMITMENT_MISMATCH` warnings in your participant logs, something has likely gone wrong while importing the active contracts of at least one of the parties hosted on your node. Another common symptom (in case the validator party is affected) is that your your validator initialization fails with a `Unknown secret` error and your validator logs contain a `ValidatorLicense not found` message. To address a failed `ACS` import, you can usually: @@ -182,7 +182,7 @@ If you still observe issues, in particular you observe `ACS_COMMITMENT_MISMATCH` - + If you still observe issues, in particular you observe `ACS_COMMITMENT_MISMATCH` warnings in your participant logs, something has likely gone wrong while importing the active contracts of at least one of the parties hosted on your node. Another common symptom (in case the validator party is affected) is that your your validator initialization fails with a `Unknown secret` error and your validator logs contain a `ValidatorLicense not found` message. To address a failed `ACS` import, you can usually: @@ -229,7 +229,7 @@ If you still observe issues, in particular you observe `ACS_COMMITMENT_MISMATCH` - + If you still observe issues, in particular you observe `ACS_COMMITMENT_MISMATCH` warnings in your participant logs, something has likely gone wrong while importing the active contracts of at least one of the parties hosted on your node. Another common symptom (in case the validator party is affected) is that your your validator initialization fails with a `Unknown secret` error and your validator logs contain a `ValidatorLicense not found` message. To address a failed `ACS` import, you can usually: @@ -300,7 +300,7 @@ To work around this, follow these steps: {/* NETWORKVARS_START source="/snippets/networkvars/global-synchronizer/production-operations/validator-disaster-recovery-2.mdx" */} - + For a party relying on external signing, a similar procedure can be used to recover its coin balance in case the validator originally hosting it becomes unusable for whatever reason. @@ -413,7 +413,7 @@ The party is now hosted on the node and can participat in transactions. The last - + For a party relying on external signing, a similar procedure can be used to recover its coin balance in case the validator originally hosting it becomes unusable for whatever reason. @@ -526,7 +526,7 @@ The party is now hosted on the node and can participat in transactions. The last - + For a party relying on external signing, a similar procedure can be used to recover its coin balance in case the validator originally hosting it becomes unusable for whatever reason. diff --git a/docs-main/global-synchronizer/reference/canton-console-reference.mdx b/docs-main/global-synchronizer/reference/canton-console-reference.mdx index c9e05df22..f53886f2a 100644 --- a/docs-main/global-synchronizer/reference/canton-console-reference.mdx +++ b/docs-main/global-synchronizer/reference/canton-console-reference.mdx @@ -45,26 +45,26 @@ Welcome to Canton! {/* NETWORKVARS_START source="/snippets/networkvars/global-synchronizer/reference/canton-console-reference-1.mdx" */} - + ```bash -docker run -it --rm --network host -v $(pwd)/console.conf:/app/app.conf ghcr.io/digital-asset/decentralized-canton-sync/docker/canton:0.6.9 --console +docker run -it --rm --network host -v $(pwd)/console.conf:/app/app.conf ghcr.io/digital-asset/decentralized-canton-sync/docker/canton:0.6.10 --console ``` - + ```bash -docker run -it --rm --network host -v $(pwd)/console.conf:/app/app.conf ghcr.io/digital-asset/decentralized-canton-sync/docker/canton:0.6.8 --console +docker run -it --rm --network host -v $(pwd)/console.conf:/app/app.conf ghcr.io/digital-asset/decentralized-canton-sync/docker/canton:0.6.9 --console ``` - + ```bash -docker run -it --rm --network host -v $(pwd)/console.conf:/app/app.conf ghcr.io/digital-asset/decentralized-canton-sync/docker/canton:0.6.7 --console +docker run -it --rm --network host -v $(pwd)/console.conf:/app/app.conf ghcr.io/digital-asset/decentralized-canton-sync/docker/canton:0.6.8 --console ``` @@ -83,26 +83,26 @@ Running docker with the default network (`splice-validator`): {/* NETWORKVARS_START source="/snippets/networkvars/global-synchronizer/reference/canton-console-reference-2.mdx" */} - + ```bash -docker run -it --rm --network splice-validator -v $(pwd)/console.conf:/app/app.conf ghcr.io/digital-asset/decentralized-canton-sync/docker/canton:0.6.9 --console +docker run -it --rm --network splice-validator -v $(pwd)/console.conf:/app/app.conf ghcr.io/digital-asset/decentralized-canton-sync/docker/canton:0.6.10 --console ``` - + ```bash -docker run -it --rm --network splice-validator -v $(pwd)/console.conf:/app/app.conf ghcr.io/digital-asset/decentralized-canton-sync/docker/canton:0.6.8 --console +docker run -it --rm --network splice-validator -v $(pwd)/console.conf:/app/app.conf ghcr.io/digital-asset/decentralized-canton-sync/docker/canton:0.6.9 --console ``` - + ```bash -docker run -it --rm --network splice-validator -v $(pwd)/console.conf:/app/app.conf ghcr.io/digital-asset/decentralized-canton-sync/docker/canton:0.6.7 --console +docker run -it --rm --network splice-validator -v $(pwd)/console.conf:/app/app.conf ghcr.io/digital-asset/decentralized-canton-sync/docker/canton:0.6.8 --console ``` @@ -115,7 +115,7 @@ docker run -it --rm --network splice-validator -v $(pwd)/console.conf:/app/app.c {/* NETWORKVARS_START source="/snippets/networkvars/global-synchronizer/reference/canton-console-reference-3.mdx" */} - + 1. Ensure you can access the sequencer's ports 5008 and 5009 @@ -143,12 +143,12 @@ canton { 3. Run the docker command ```bash -docker run -it --rm --network host -v $(pwd)/console.conf:/app/app.conf ghcr.io/digital-asset/decentralized-canton-sync/docker/canton:0.6.9 --console +docker run -it --rm --network host -v $(pwd)/console.conf:/app/app.conf ghcr.io/digital-asset/decentralized-canton-sync/docker/canton:0.6.10 --console ``` - + 1. Ensure you can access the sequencer's ports 5008 and 5009 @@ -176,12 +176,12 @@ canton { 3. Run the docker command ```bash -docker run -it --rm --network host -v $(pwd)/console.conf:/app/app.conf ghcr.io/digital-asset/decentralized-canton-sync/docker/canton:0.6.8 --console +docker run -it --rm --network host -v $(pwd)/console.conf:/app/app.conf ghcr.io/digital-asset/decentralized-canton-sync/docker/canton:0.6.9 --console ``` - + 1. Ensure you can access the sequencer's ports 5008 and 5009 @@ -209,7 +209,7 @@ canton { 3. Run the docker command ```bash -docker run -it --rm --network host -v $(pwd)/console.conf:/app/app.conf ghcr.io/digital-asset/decentralized-canton-sync/docker/canton:0.6.7 --console +docker run -it --rm --network host -v $(pwd)/console.conf:/app/app.conf ghcr.io/digital-asset/decentralized-canton-sync/docker/canton:0.6.8 --console ``` @@ -222,7 +222,7 @@ docker run -it --rm --network host -v $(pwd)/console.conf:/app/app.conf ghcr.io/ {/* NETWORKVARS_START source="/snippets/networkvars/global-synchronizer/reference/canton-console-reference-4.mdx" */} - + 1. Ensure you can access the mediator's port 5007 @@ -246,12 +246,12 @@ canton { 3. Run the docker command ```bash -docker run -it --rm --network host -v $(pwd)/console.conf:/app/app.conf ghcr.io/digital-asset/decentralized-canton-sync/docker/canton:0.6.9 --console +docker run -it --rm --network host -v $(pwd)/console.conf:/app/app.conf ghcr.io/digital-asset/decentralized-canton-sync/docker/canton:0.6.10 --console ``` - + 1. Ensure you can access the mediator's port 5007 @@ -275,12 +275,12 @@ canton { 3. Run the docker command ```bash -docker run -it --rm --network host -v $(pwd)/console.conf:/app/app.conf ghcr.io/digital-asset/decentralized-canton-sync/docker/canton:0.6.8 --console +docker run -it --rm --network host -v $(pwd)/console.conf:/app/app.conf ghcr.io/digital-asset/decentralized-canton-sync/docker/canton:0.6.9 --console ``` - + 1. Ensure you can access the mediator's port 5007 @@ -304,7 +304,7 @@ canton { 3. Run the docker command ```bash -docker run -it --rm --network host -v $(pwd)/console.conf:/app/app.conf ghcr.io/digital-asset/decentralized-canton-sync/docker/canton:0.6.7 --console +docker run -it --rm --network host -v $(pwd)/console.conf:/app/app.conf ghcr.io/digital-asset/decentralized-canton-sync/docker/canton:0.6.8 --console ``` diff --git a/docs-main/sdks-tools/api-reference/splice-daml-apis.mdx b/docs-main/sdks-tools/api-reference/splice-daml-apis.mdx index 35670eaa6..d73e183b0 100644 --- a/docs-main/sdks-tools/api-reference/splice-daml-apis.mdx +++ b/docs-main/sdks-tools/api-reference/splice-daml-apis.mdx @@ -43,13 +43,13 @@ Earning featured app rewards for direct transfers of non-CC tokens to your walle {/* NETWORKVARS_START source="/snippets/networkvars/sdks-tools/api-reference/splice-daml-apis-1.mdx" */} - + Assuming you are a wallet provider that runs a validator node for your users, you can use the `WalletUserProxy` template to get credit for the activity of your wallet users as follows. 1. Apply for a featured app right for your wallet provider party, as explained on [how_to_become_a_featured_application](/overview/reference/canton-coin-tokenomics). -2. Extract the latest version of the `splice-util-featured-app-proxies.dar` file from the release bundle (Download Bundle (DevNet 0.6.9)). +2. Extract the latest version of the `splice-util-featured-app-proxies.dar` file from the release bundle (Download Bundle (DevNet 0.6.10)). 3. Upload the extracted `.dar` file to your validator node. @@ -67,13 +67,13 @@ Assuming you are a wallet provider that runs a validator node for your users, yo - + Assuming you are a wallet provider that runs a validator node for your users, you can use the `WalletUserProxy` template to get credit for the activity of your wallet users as follows. 1. Apply for a featured app right for your wallet provider party, as explained on [how_to_become_a_featured_application](/overview/reference/canton-coin-tokenomics). -2. Extract the latest version of the `splice-util-featured-app-proxies.dar` file from the release bundle (Download Bundle (TestNet 0.6.8)). +2. Extract the latest version of the `splice-util-featured-app-proxies.dar` file from the release bundle (Download Bundle (TestNet 0.6.9)). 3. Upload the extracted `.dar` file to your validator node. @@ -91,13 +91,13 @@ Assuming you are a wallet provider that runs a validator node for your users, yo - + Assuming you are a wallet provider that runs a validator node for your users, you can use the `WalletUserProxy` template to get credit for the activity of your wallet users as follows. 1. Apply for a featured app right for your wallet provider party, as explained on [how_to_become_a_featured_application](/overview/reference/canton-coin-tokenomics). -2. Extract the latest version of the `splice-util-featured-app-proxies.dar` file from the release bundle (Download Bundle (MainNet 0.6.7)). +2. Extract the latest version of the `splice-util-featured-app-proxies.dar` file from the release bundle (Download Bundle (MainNet 0.6.8)). 3. Upload the extracted `.dar` file to your validator node. diff --git a/docs-main/sdks-tools/api-reference/splice-http-apis.mdx b/docs-main/sdks-tools/api-reference/splice-http-apis.mdx index ea026e5f7..c22d8975f 100644 --- a/docs-main/sdks-tools/api-reference/splice-http-apis.mdx +++ b/docs-main/sdks-tools/api-reference/splice-http-apis.mdx @@ -25,21 +25,21 @@ Some of the Splice apps also define additional HTTP APIs that are considered int {/* NETWORKVARS_START source="/snippets/networkvars/sdks-tools/api-reference/splice-http-apis-1.mdx" */} - + -The HTTP APIs of Splice apps are documented using [OpenAPI specifications](https://www.openapis.org/). You can download the OpenAPI specification for Splice's applications here: Download OpenAPI specs (DevNet 0.6.9). +The HTTP APIs of Splice apps are documented using [OpenAPI specifications](https://www.openapis.org/). You can download the OpenAPI specification for Splice's applications here: Download OpenAPI specs (DevNet 0.6.10). - + -The HTTP APIs of Splice apps are documented using [OpenAPI specifications](https://www.openapis.org/). You can download the OpenAPI specification for Splice's applications here: Download OpenAPI specs (TestNet 0.6.8). +The HTTP APIs of Splice apps are documented using [OpenAPI specifications](https://www.openapis.org/). You can download the OpenAPI specification for Splice's applications here: Download OpenAPI specs (TestNet 0.6.9). - + -The HTTP APIs of Splice apps are documented using [OpenAPI specifications](https://www.openapis.org/). You can download the OpenAPI specification for Splice's applications here: Download OpenAPI specs (MainNet 0.6.7). +The HTTP APIs of Splice apps are documented using [OpenAPI specifications](https://www.openapis.org/). You can download the OpenAPI specification for Splice's applications here: Download OpenAPI specs (MainNet 0.6.8). diff --git a/docs-main/sdks-tools/api-reference/splice-scan-bulk-data-api.mdx b/docs-main/sdks-tools/api-reference/splice-scan-bulk-data-api.mdx index 96cea434d..d1832e2d5 100644 --- a/docs-main/sdks-tools/api-reference/splice-scan-bulk-data-api.mdx +++ b/docs-main/sdks-tools/api-reference/splice-scan-bulk-data-api.mdx @@ -29,7 +29,7 @@ The Bulk Data Scan API provides access to the update history and ACS snapshots a {/* NETWORKVARS_START source="/snippets/networkvars/sdks-tools/api-reference/splice-scan-bulk-data-api-1.mdx" */} - + The [scan_openapi](/sdks-tools/api-reference/splice-apis) describes the Scan API in detail. The below table provides a quick overview of the endpoints that the Scan Bulk Data API consists of: @@ -51,7 +51,7 @@ Please note the `api/scan` prefix in the URLs, which is the base path for the Sc - + The [scan_openapi](/sdks-tools/api-reference/splice-apis) describes the Scan API in detail. The below table provides a quick overview of the endpoints that the Scan Bulk Data API consists of: @@ -73,7 +73,7 @@ Please note the `api/scan` prefix in the URLs, which is the base path for the Sc - + The [scan_openapi](/sdks-tools/api-reference/splice-apis) describes the Scan API in detail. The below table provides a quick overview of the endpoints that the Scan Bulk Data API consists of: @@ -418,7 +418,7 @@ The ACS snapshots are periodically taken and stored in the Scan App. This endpoi {/* NETWORKVARS_START source="/snippets/networkvars/sdks-tools/api-reference/splice-scan-bulk-data-api-2.mdx" */} - + The /v0/state/acs/snapshot-timestamp endpoint returns the timestamp of the most recent snapshot before the given date, for the given `migration_id`. Specify `migration_id = 0` for the beginning of the network. The returned timestamp corresponds to the record time of the last transaction in the snapshot. @@ -438,7 +438,7 @@ The response returns the timestamp of the most recent snapshot before the given - + The /v0/state/acs/snapshot-timestamp endpoint returns the timestamp of the most recent snapshot before the given date, for the given `migration_id`. Specify `migration_id = 0` for the beginning of the network. The returned timestamp corresponds to the record time of the last transaction in the snapshot. @@ -458,7 +458,7 @@ The response returns the timestamp of the most recent snapshot before the given - + The /v0/state/acs/snapshot-timestamp endpoint returns the timestamp of the most recent snapshot before the given date, for the given `migration_id`. Specify `migration_id = 0` for the beginning of the network. The returned timestamp corresponds to the record time of the last transaction in the snapshot. diff --git a/docs-main/sdks-tools/api-reference/splice-scan-gs-connectivity-api.mdx b/docs-main/sdks-tools/api-reference/splice-scan-gs-connectivity-api.mdx index 6497c3545..42fef7690 100644 --- a/docs-main/sdks-tools/api-reference/splice-scan-gs-connectivity-api.mdx +++ b/docs-main/sdks-tools/api-reference/splice-scan-gs-connectivity-api.mdx @@ -12,7 +12,7 @@ Splice network applications and validators need to be able to connect to multipl {/* NETWORKVARS_START source="/snippets/networkvars/sdks-tools/api-reference/splice-scan-gs-connectivity-api-1.mdx" */} - + Every Scan can list all approved SV scans connected to the network. For example, query from /v0/scans from https://scan.sv-1.dev.global.canton.network.sync.global, and the response will be something like @@ -42,7 +42,7 @@ Every Scan can list all approved SV scans connected to the network. For example, - + Every Scan can list all approved SV scans connected to the network. For example, query from /v0/scans from https://scan.sv-1.test.global.canton.network.sync.global, and the response will be something like @@ -72,7 +72,7 @@ Every Scan can list all approved SV scans connected to the network. For example, - + Every Scan can list all approved SV scans connected to the network. For example, query from /v0/scans from https://scan.sv-1.global.canton.network.sync.global, and the response will be something like diff --git a/docs-main/snippets/generated/version-dashboard-data.mdx b/docs-main/snippets/generated/version-dashboard-data.mdx index 35669a730..a727cd5bb 100644 --- a/docs-main/snippets/generated/version-dashboard-data.mdx +++ b/docs-main/snippets/generated/version-dashboard-data.mdx @@ -4,13 +4,13 @@ export const networkData = { description: 'Production network for live applications. Data is permanent and never reset. Upgrades follow DevNet and TestNet validation.', color: '#22c55e', versions: { - splice: '0.6.7', - damlSdk: '3.5.3', + splice: '0.6.8', + damlSdk: '3.5.4', pqs: '3.5.2', - tokenStandard: '1.6.1', + tokenStandard: '1.7.0', walletSdk: '1.3.1', - dappSdk: '1.2.0', - walletGateway: '1.4.0', + dappSdk: '1.3.0', + walletGateway: '1.5.0', }, advanced: { minProtocolVersion: '6', @@ -20,7 +20,7 @@ export const networkData = { { name: 'splice-wallet', version: '0.1.20' }, { name: 'splice-dso-governance', version: '0.1.25' }, ], - releaseUrl: 'https://github.com/canton-network/splice/releases/tag/0.6.7', + releaseUrl: 'https://github.com/canton-network/splice/releases/tag/0.6.8', }, endpoint: 'scan.sv-1.global.canton.network.sync.global', substitutions: { @@ -31,19 +31,19 @@ export const networkData = { gsf_scan_url: 'https://scan.sv-1.global.canton.network.sync.global', generic_scan_url: 'https://scan.sv-1.global.canton.network.YOUR_SV_SPONSOR', gsf_sequencer_url: 'https://sequencer-MIGRATION_ID.sv-1.global.canton.network.sync.global', - version: '0.6.7', - version_literal: '0.6.7', - chart_version_literal: '0.6.7', - chart_version_set: 'export CHART_VERSION=0.6.7', - image_tag_set: 'export IMAGE_TAG=0.6.7', - image_tag_set_plain: 'export IMAGE_TAG=0.6.7', + version: '0.6.8', + version_literal: '0.6.8', + chart_version_literal: '0.6.8', + chart_version_set: 'export CHART_VERSION=0.6.8', + image_tag_set: 'export IMAGE_TAG=0.6.8', + image_tag_set_plain: 'export IMAGE_TAG=0.6.8', bundle_download_link: { label: 'Download Bundle', - href: 'https://github.com/digital-asset/decentralized-canton-sync/releases/download/v0.6.7/0.6.7_splice-node.tar.gz', + href: 'https://github.com/digital-asset/decentralized-canton-sync/releases/download/v0.6.8/0.6.8_splice-node.tar.gz', }, openapi_download_link: { label: 'Download OpenAPI specs', - href: 'https://github.com/digital-asset/decentralized-canton-sync/releases/download/v0.6.7/0.6.7_openapi.tar.gz', + href: 'https://github.com/digital-asset/decentralized-canton-sync/releases/download/v0.6.8/0.6.8_openapi.tar.gz', }, helm_repo_prefix: 'oci://ghcr.io/digital-asset/decentralized-canton-sync/helm', docker_repo_prefix: 'ghcr.io/digital-asset/decentralized-canton-sync/docker', @@ -54,23 +54,23 @@ export const networkData = { description: 'Pre-production environment for final validation. Requires MainNet approval to join. May be reset periodically.', color: '#eab308', versions: { - splice: '0.6.8', - damlSdk: '3.5.4', + splice: '0.6.9', + damlSdk: '3.5.5', pqs: '3.5.2', - tokenStandard: '1.6.1', + tokenStandard: '1.7.0', walletSdk: '1.3.1', - dappSdk: '1.2.0', - walletGateway: '1.4.0', + dappSdk: '1.3.0', + walletGateway: '1.5.0', }, advanced: { minProtocolVersion: '6', migrationId: '1', darVersions: [ - { name: 'splice-amulet', version: '0.1.19' }, - { name: 'splice-wallet', version: '0.1.20' }, - { name: 'splice-dso-governance', version: '0.1.25' }, + { name: 'splice-amulet', version: '0.1.20' }, + { name: 'splice-wallet', version: '0.1.21' }, + { name: 'splice-dso-governance', version: '0.1.26' }, ], - releaseUrl: 'https://github.com/canton-network/splice/releases/tag/0.6.8', + releaseUrl: 'https://github.com/canton-network/splice/releases/tag/0.6.9', }, endpoint: 'scan.sv-1.test.global.canton.network.sync.global', substitutions: { @@ -81,19 +81,19 @@ export const networkData = { gsf_scan_url: 'https://scan.sv-1.test.global.canton.network.sync.global', generic_scan_url: 'https://scan.sv-1.test.global.canton.network.YOUR_SV_SPONSOR', gsf_sequencer_url: 'https://sequencer-MIGRATION_ID.sv-1.test.global.canton.network.sync.global', - version: '0.6.8', - version_literal: '0.6.8', - chart_version_literal: '0.6.8', - chart_version_set: 'export CHART_VERSION=0.6.8', - image_tag_set: 'export IMAGE_TAG=0.6.8', - image_tag_set_plain: 'export IMAGE_TAG=0.6.8', + version: '0.6.9', + version_literal: '0.6.9', + chart_version_literal: '0.6.9', + chart_version_set: 'export CHART_VERSION=0.6.9', + image_tag_set: 'export IMAGE_TAG=0.6.9', + image_tag_set_plain: 'export IMAGE_TAG=0.6.9', bundle_download_link: { label: 'Download Bundle', - href: 'https://github.com/digital-asset/decentralized-canton-sync/releases/download/v0.6.8/0.6.8_splice-node.tar.gz', + href: 'https://github.com/digital-asset/decentralized-canton-sync/releases/download/v0.6.9/0.6.9_splice-node.tar.gz', }, openapi_download_link: { label: 'Download OpenAPI specs', - href: 'https://github.com/digital-asset/decentralized-canton-sync/releases/download/v0.6.8/0.6.8_openapi.tar.gz', + href: 'https://github.com/digital-asset/decentralized-canton-sync/releases/download/v0.6.9/0.6.9_openapi.tar.gz', }, helm_repo_prefix: 'oci://ghcr.io/digital-asset/decentralized-canton-sync/helm', docker_repo_prefix: 'ghcr.io/digital-asset/decentralized-canton-sync/docker', @@ -104,13 +104,13 @@ export const networkData = { description: 'Development environment with latest features. Open to any validator (IP allowlist required). Reset every 3 months. Best for testing upgrades.', color: '#a78bfa', versions: { - splice: '0.6.9', - damlSdk: '3.5.5', + splice: '0.6.10', + damlSdk: '3.5.6', pqs: '3.5.2', - tokenStandard: '1.6.1', + tokenStandard: '1.7.0', walletSdk: '1.3.1', - dappSdk: '1.2.0', - walletGateway: '1.4.0', + dappSdk: '1.3.0', + walletGateway: '1.5.0', }, advanced: { minProtocolVersion: '6', @@ -120,7 +120,7 @@ export const networkData = { { name: 'splice-wallet', version: '0.1.21' }, { name: 'splice-dso-governance', version: '0.1.26' }, ], - releaseUrl: 'https://github.com/canton-network/splice/releases/tag/0.6.9', + releaseUrl: 'https://github.com/canton-network/splice/releases/tag/0.6.10', }, endpoint: 'scan.sv-1.dev.global.canton.network.sync.global', substitutions: { @@ -131,19 +131,19 @@ export const networkData = { gsf_scan_url: 'https://scan.sv-1.dev.global.canton.network.sync.global', generic_scan_url: 'https://scan.sv-1.dev.global.canton.network.YOUR_SV_SPONSOR', gsf_sequencer_url: 'https://sequencer-MIGRATION_ID.sv-1.dev.global.canton.network.sync.global', - version: '0.6.9', - version_literal: '0.6.9', - chart_version_literal: '0.6.9', - chart_version_set: 'export CHART_VERSION=0.6.9', - image_tag_set: 'export IMAGE_TAG=0.6.9', - image_tag_set_plain: 'export IMAGE_TAG=0.6.9', + version: '0.6.10', + version_literal: '0.6.10', + chart_version_literal: '0.6.10', + chart_version_set: 'export CHART_VERSION=0.6.10', + image_tag_set: 'export IMAGE_TAG=0.6.10', + image_tag_set_plain: 'export IMAGE_TAG=0.6.10', bundle_download_link: { label: 'Download Bundle', - href: 'https://github.com/digital-asset/decentralized-canton-sync/releases/download/v0.6.9/0.6.9_splice-node.tar.gz', + href: 'https://github.com/digital-asset/decentralized-canton-sync/releases/download/v0.6.10/0.6.10_splice-node.tar.gz', }, openapi_download_link: { label: 'Download OpenAPI specs', - href: 'https://github.com/digital-asset/decentralized-canton-sync/releases/download/v0.6.9/0.6.9_openapi.tar.gz', + href: 'https://github.com/digital-asset/decentralized-canton-sync/releases/download/v0.6.10/0.6.10_openapi.tar.gz', }, helm_repo_prefix: 'oci://ghcr.io/digital-asset/decentralized-canton-sync/helm', docker_repo_prefix: 'ghcr.io/digital-asset/decentralized-canton-sync/docker',