Documentation

0.9.2 — 2025-12-05 🩹 Fixes • wallet-gateway-remote: display gateway version in startup logs + UI ( #992 ) • wallet-gateway-remote: defaults for server config ( #990 ) 🧱 Updated Dependencies • Updated @canton-network/core-wallet-dapp-rpc-client to 0.15.3 • Updated @canton-network/core-walle

1.2.0 — 2026-05-05 🚀 Features • add dfns signing driver ( #1682 ) 🩹 Fixes • wallet-gateway-remote: support scp scoping in jwt ( #1702 ) • wallet-gateway-remote: updates to creating a party in the wallet gateway ( #1676 ) 🧱 Updated Dependencies • Updated @canton-network/core-wallet-dapp-

1.2.1 — 2026-05-08 🧱 Updated Dependencies • Updated @canton-network/core-wallet-dapp-rpc-client to 1.2.1 • Updated @canton-network/core-wallet-user-rpc-client to 1.2.1 • Updated @canton-network/core-wallet-store-inmemory to 1.2.1 • Updated @canton-network/core-wallet-ui-components to 1.2.1 •

1.3.0 — 2026-05-13 🧱 Updated Dependencies • Updated @canton-network/core-signing-dfns to 0.3.0

The Wallet Gateway is a self-hosted component that lets dApps connect to your infrastructure on Canton Network. You run it in your own environment, next to a validator you already operate, so any CIP-0103 dApp can connect to the Wallet Gateway while it talks to your validator and signs through your

Release of Canton 3.6.4 Canton 3.6.4 has been released on October 22, 2026. Summary This is a security maintenance release that updates the canton docker base image. What’s New Security Improvements Bumped the docker base image to 1.0.17 which includes the updated version of CA CERT that

Canton Special Interest Groups (SIGs) Special Interest Groups (SIGs) are groups of architects, software engineers, and domain experts focused on specific technical or domain areas within the Canton ecosystem. SIGs help coordinate…

This page covers Canton-side pruning for participant nodes and automatic pruning configuration. For Super Validator pruning of the sequencer and CometBFT layers, see SV Pruning . Participant node pruning Pruning helps bound the size of the database storage. Participant Node pruning refers to th

1. Configure your Validator Node Ensure you are running the same splice version on your node as is run on the primary validator and other covalidating node(s), keeping up to date with the Canton Foundation schedule . Create / configure the validator node which you will use as your covalidating n

Release of Canton 3.6.3 Canton 3.6.3 has been released on October 20, 2026. Summary This patch release fixes slow topology store lookups on Postgres that could cause high participant database load and make the ACS commitment processor fall behind on large topology states. What’s New Faster

Canton applications need different configurations for each environment — LocalNet, DevNet, TestNet, and MainNet. This page covers the configuration layers you work with: DPM global settings, project-level daml.yaml, environment variables, and authentication setup. DPM Configuration DPM is Daml

This tutorial demonstrates how to query contracts and transactions using SQL in the Participant Query Store (PQS). Overview This tutorial shows how to: • connect a PQS instance to a Daml ledger • connect a PQS instance to a PostgreSQL database • query contracts that get exported with SQL A

When things go wrong, it is important to be able to diagnose the problem quickly and effectively. This section aims to get an operator up to speed with the most common troubleshooting techniques and tools available in PQS. You might want to refer to it for ideas when devising your own troubleshootin

Query optimization It is important to ensure that proper capacity planning of resources is performed to match the expected workload. Host infrastructure The following are the minimum requirements for the host operating system running any kind of production workload, and should be seen as a sta

PQS ascertains its configuration from the following sources, in order of priority: • HOCON configuration files (--config argument) • command-line arguments • Java system properties (-D arguments to java command) • environment variables Consult the command ./pqs.jar pipeline --help-v

PQS (Participant Query Store) subscribes to a validator’s transaction stream and projects contract data into a PostgreSQL database. Your backend queries this database with standard SQL, enabling: filtered queries, aggregations, joins, and full-text search that would be impractical through the Ledger

This page captures the Ledger Client Standard functionality that should be provided by fully conformant library implementations. It is written for developers who build Canton ledger client libraries. This standard reflects Canton 3.5. The Functionality Requirement column marks each capability as

Beyond the officially supported Java and TypeScript bindings, community members have built client libraries for other languages. These bindings are not maintained or supported by Canton Network and may not cover the full Ledger API surface or keep pace with every Canton release. Available Communit

Multiple support channels are available depending on your needs and relationship with Canton Network. Community Support Free, community-driven support channels available to everyone. Slack The primary community channel for real-time discussion. Channel | Purpose | #validator-operations |

A common deployment pattern on Canton Network combines dedicated synchronizers with the Global Synchronizer. Your validators connect to both, running high-volume or confidential workflows on the dedicated synchronizer while settling or sharing results through the Global Synchronizer. Why use a hyb

You can run validators exclusively on a dedicated synchronizer, with no connection to the Global Synchronizer. However, a dedicated synchronizer must have at least one validator that maintains a persistent connection to the Global Synchronizer for accounting and settlement purposes. This connection

Party Management Parties are the entities that interact with the Daml ledger, representing users or organizations. They can be onboarded to a Participant Node, which allows them to submit transactions and access the ledger. The following section explains how to onboard a (local) party. Refer to t

Canton validators can connect to multiple synchronizers at the same time. This is how the MainNet is extended — your validator participates in the Global Synchronizer for network-wide interoperability while also connecting to one or more dedicated synchronizers for specialized workflows with dedicat

Release of Canton 3.6.2 Canton 3.6.2 has been released on October 15, 2026. Summary This patch release fixes a slow Ledger API query that could stall the initialization of the ACS commitment processor in Canton 3.6.1 by using index lookups. What’s New Event sequential id range lookup of Le

The sequencer, participant and CometBFT have pruning options that can be used to ensure storage use is kept within reasonable bounds. Sequencer pruning Can be enabled in helm through the following config: synchronizers: current: sequencerPruningConfig: Enable or disable sequen

Minting delegations allow a delegate to instruct their validator node to automate the minting of rewards on behalf of an external party (the beneficiary) hosted on the same validator node. The delegate can be any party onboarded to the validator node’s wallet (e.g., the validator operator party, but

cURL Python JavaScript PHP Go Java Ruby curl --request GET \ --url 'https://example.com/api/validator/v0/scan-proxy/registry/metadata/v1/info' import json import requests url = "https://example.com/api/validator/v0/scan-proxy/registry/metadata/v1/info" response = requests.req

cURL Python JavaScript PHP Go Java Ruby curl --request POST \ --url 'https://example.com/api/validator/v0/scan-proxy/registry/allocations/v1/{allocationId}/choice-contexts/execute-transfer' \ --header 'Content-Type: application/json' \ --data '{ "meta": {}, "excludeDebugFields"

cURL Python JavaScript PHP Go Java Ruby curl --request GET \ --url 'https://example.com/api/validator/v0/scan-proxy/registry/metadata/v1/instruments' import json import requests url = "https://example.com/api/validator/v0/scan-proxy/registry/metadata/v1/instruments" response

cURL Python JavaScript PHP Go Java Ruby curl --request POST \ --url 'https://example.com/api/validator/v0/scan-proxy/registry/allocation-instruction/v2/allocation-factory' \ --header 'Content-Type: application/json' \ --data '{ "choiceArguments": {}, "excludeDebugFields": false