Documentation

1.9.0 — 2026-08-18 🚀 Features • change default hashing scheme ( #2292 ) 🩹 Fixes • handle rejected wallet approvals ( #2278 ) 🧱 Updated Dependencies • Updated @canton-network/core-wallet-dapp-rpc-client to 1.10.1 • Updated @canton-network/core-wallet-user-rpc-client to 1.11.1 • Updated

Canton nodes use HOCON (Human-Optimized Config Object Notation) for its static configuration files. Static configuration covers settings that must be known at process startup, such as storage backends, API ports, and node identities. Dynamic settings like party registration and synchronizer connecti

The Canton console is built on Ammonite , a Scala-based scripting and REPL framework. Every command you type is valid Scala, which means you can write loops, define functions, bind variables, and compose operations just as you would in any Scala program. This page covers the practical side of scrip

Release of Canton 3.5.12 Canton 3.5.12 has been released on August 07, 2026. Summary This is a maintenance release that ships improvements for CantonBFT and the traffic enforcement app, as well as improving the mitigation for a critical fix shipped with 3.4.11. What’s New Traffic Enforceme

Release of Canton 3.5.13 Canton 3.5.13 has been released on August 13, 2026. Summary This is a maintenance release with a number of improvements in particular for CantonBFT and traffic enforcement app, as well as minor improvements in various areas. What’s New Traffic Enforcement App Impro

Release of Canton 3.5.11 Canton 3.5.11 has been released on July 30, 2026. Summary This is a maintenance release that fixes a bug in participants for LSU and provides minor operational improvements. What’s New Minor Improvements • Improved the resilience of the CachedJwtVerifierLoader JWK

Data types In Contract Templates , you learnt about contract templates, which specify the types of contracts that can be created on the ledger, and what data those contracts hold in their arguments. In Daml Script , you learnt about the script view in Daml Studio, which displays the current ledge

Parties and users on a Canton ledger Identifying parties and users is an important part of building a workable Canton application. • Parties are unique across the entire Canton network. These must be allocated before you can use them to log in, and allocation results in a random-looking (but not

1.8.1 — 2026-08-13 🩹 Fixes • drop token sub matches clientId assertion ( #2282 ) 🧱 Updated Dependencies • Updated @canton-network/core-wallet-ui-components to 1.12.1 ❤️ Thank You • Alex Matson @alexmatson-da • Pawel Stepien

Using an external KMS for managing participant keys By default, Canton participants use cryptographic keys that are generated by the participant itself and stored in the regular database used by the participant. To improve key security, participants can be configured to use an external Key Managem

Canton’s architecture provides built-in privacy and audit properties that differ substantially from public blockchains. This page summarizes the compliance-relevant characteristics you should understand when building applications on Canton Network. This page provides technical facts about Canton’s

Canton’s trust model differs fundamentally from traditional blockchains. Rather than “trust everyone” or “trust no one,” Canton enables selective trust —you choose who to trust for what purpose. The Core Question In any distributed system, the key question is: Who do you need to trust, and for w

A validator on Canton Network is more than a Canton participant node. It bundles a Canton participant with the Splice application layer — the software that implements Canton Coin, the wallet, the Canton Name Service, and network management automation. This page describes each component layer and how

The Global Synchronizer is the public infrastructure backbone of Canton Network, a decentralized synchronizer operated by Super Validators. What It Is The Global Synchronizer is: • A synchronizer instance (BFT configuration of several sequencer + mediator nodes) operated by multiple independent

Canton’s architecture enables use cases that are not feasible on public blockchains. This page explores key patterns and concrete examples. Delivery vs. Payment (DvP) The canonical example of Canton’s capabilities is atomic delivery vs. payment across different assets and parties. The Scenario

LocalNet provides a straightforward topology comprising three participants, three validators, a PostgreSQL database, and several web applications (wallet, sv, scan) behind an NGINX gateway. Each validator plays a distinct role within the Splice ecosystem: • app-provider : for the user operating the

Scaling and Performance Network Scaling The scaling and performance characteristics of a Canton-based system are determined by many factors. The simplest approach is to deploy Canton as a simple monolith where vertical scaling would add more CPUs, memory, etc. to the compute resource. However, t

When transactions fail, nodes disconnect, or the system behaves unexpectedly, the Canton Console provides the tools to diagnose the problem. This page walks through common debugging scenarios with concrete console commands. Debugging Stuck Transactions A transaction appears “stuck” when a comman

When a transaction fails, a contract goes missing, or your application behaves unexpectedly, Canton provides several tools to investigate. This page covers the debugging tools available and common workflows for diagnosing issues. dpm test Output dpm test runs your Daml Script tests and reports

Answers to questions that come up regularly in Canton Network application development. For validator operations questions, see the Common Issues FAQ . Getting Started What SDK version should I use? Use the latest stable Daml SDK (3.x series). The 2.x Daml SDK is for historical development and

This reference covers the most commonly used Canton Console commands, organized by task. All examples assume you’re connected to a participant console unless otherwise noted. When the Canton Console starts, it reads the configuration file and automatically binds a variable for each configured node.

Manage Daml packages and archives About A package is a unit of compiled Daml code corresponding to one Daml project. This package contains compiled Daml-LF code. Every package has a unique package-id. A Daml Archive (DAR) file consists of a main package along with all other packages on which t

Check and monitor Sequencer Node health This page describes how to inspect and understand the current status of a Sequencer Node, and how to continuously monitor it using health checks. See also the generic guide on How to check the status of a Node and monitor its health. Interactively check N

TLS API Configuration Both the gRPC Ledger API and the Admin API support the same TLS capabilities and can be configured using identical directives. TLS provides end-to-end channel encryption between the server and the client, and—depending on the configuration—can enforce either server-only or mu

Canton Console Canton offers a console (REPL) where entities can be dynamically started and stopped, and a variety of administrative or debugging commands can be run. All console commands must be valid Scala (the console is built on Ammonite - a Scala-based scripting and REPL framework). Note tha

API Configuration Participant nodes expose the Admin API, the gRPC Ledger API, and optionally the JSON Ledger API. This page explains how to configure general options that apply to both the Admin API and the gRPC Ledger API. For the configuration options that apply only to specific APIs, please r

The Canton Console is an interactive Scala REPL that connects to Canton nodes for administration, debugging, and automation. It provides direct access to participant, sequencer, and mediator operations through a typed API. For full operational documentation, see the Global Synchronizer section , wh

1.8.0 — 2026-08-10 🚀 Features • add securosys signing driver ( #2123 ) 🩹 Fixes • hide privileged auth credentials for non-admins ( #2257 ) • 1874 network connectivity UI ( #2211 ) 🧱 Updated Dependencies • Updated @canton-network/core-wallet-dapp-rpc-client to 1.10.0 • Updated @canton-n

Overview The Covalidation Service (CVS) is a managed infrastructure solution for the Canton Network that eliminates single points of failure for wallets and applications. By multi-hosting parties and distributing validation responsibilities across a redundant, high-availability network, CVS helps

Super Validators Where do I find all whitelisted node operators? All whitelisted SVs are listed in the public global synchronizer configurations repository . Where do I generate a Validator Onboarding Token? SVs generate a validator onboarding token in the SV UI. Validators How long is my V