Documentation

cURL Python JavaScript PHP Go Java Ruby curl --request GET \ --url 'https://example.com/api/validator/v0/scan-proxy/ans-entries' import json import requests url = "https://example.com/api/validator/v0/scan-proxy/ans-entries" response = requests.request("GET", url) print(resp

cURL Python JavaScript PHP Go Java Ruby curl --request GET \ --url 'https://example.com/api/validator/v0/scan-proxy/dso-party-id' import json import requests url = "https://example.com/api/validator/v0/scan-proxy/dso-party-id" response = requests.request("GET", url) print(re

cURL Python JavaScript PHP Go Java Ruby curl --request GET \ --url 'https://example.com/api/validator/v0/wallet/transfer-offers' \ --header 'Authorization: Bearer $TOKEN' import json import requests url = "https://example.com/api/validator/v0/wallet/transfer-offers" headers

cURL Python JavaScript PHP Go Java Ruby curl --request POST \ --url 'https://scan.sv-1.global.canton.network.sync.global/api/scan/v0/state/acs/force' import json import requests url = "https://scan.sv-1.global.canton.network.sync.global/api/scan/v0/state/acs/force" response =

cURL Python JavaScript PHP Go Java Ruby curl --request POST \ --url 'https://example.com/registry/transfer-instruction/v1/{transferInstructionId}/choice-contexts/reject' \ --header 'Content-Type: application/json' \ --data '{ "meta": {}, "excludeDebugFields": false }'

cURL Python JavaScript PHP Go Java Ruby curl --request POST \ --url 'https://example.com/registry/transfer-instruction/v2/{transferInstructionId}/choice-contexts/reject' \ --header 'Content-Type: application/json' \ --data '{ "meta": {}, "excludeDebugFields": false }'

adjust style of write-up below to the rest of docs cometbft helm values • disable state sync stateSync: • enable: true • rpcServers: ”…” • enable: false • For the single sv config, you are now bootstrapping a single sv so put your own keys in: sv1: • keyAddress: ”…” • nodeId: ”…” • pub

External Signing Hashing Algorithm Introduction This document specifies the encoding algorithm used to produce a deterministic hash of a com.daml.ledger.api.v2.interactive.PreparedTransaction. The resulting hash is signed by the holder of the external party’s private key. The signature authori

SV nodes protect their HTTP and gRPC endpoints against excessive load with two complementary layers: • Application-level rate limits , enforced by the SV app, the Scan app and the sequencer. They are enabled by default and values are tuned based on observed traffic patterns. Temporary overrides can

Canton Network validators can be deployed using Docker Compose or Kubernetes with Helm charts. Your choice depends on the target environment, operational maturity, and scale requirements. Docker Compose Docker Compose is the simplest path to running a validator. It packages all components into a

The ordering consensus layer is one half of Canton’s two-layer consensus architecture . While the smart contract consensus layer validates transaction correctness among affected parties, the ordering layer establishes a single, global sequence of events on a given synchronizer. It does so without ac

Release of Canton 3.5.14 Canton 3.5.14 has been released on August 19, 2026. Summary This is a maintenance release with improvements for CantonBFT. What’s New CantonBFT Improvements • Added a configuration option to override the view change timeout that is set via a topology transaction (

The purpose of this page is to: • Introduce you to the importance and problems of multi-party applications. • Provide a high-level overview of how Canton can help you build and run multi-party applications. • Explain the different components of the Canton ecosystem and how they fit together.

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