Documentation

Canton Participant Node exposes a package management service that allows uploading and discovery of the Daml packages. This guide explains how to programmatically manipulate the packages using the JSON Ledger API, which is described using OpenAPI specifications. To learn about the Daml packages, se

This section features solutions shared by community members. While they haven’t been formally tested by the Splice maintainers, users are encouraged to verify the information independently. Contributions to enhance accuracy and completeness are always welcome. To deploy a validator node, configure

PostgreSQL 14, the version all Splice deployment options ship today, reaches end-of-life on 2026-11-12. For Kubernetes deployments, the splice-postgres Helm chart is deprecated and will not be supported after that date. Published chart versions remain available, but receive no further updates. No

Canton Network supports multiple synchronizers operating simultaneously. Each contract on the ledger is assigned to a specific synchronizer, and contracts can be moved between synchronizers as needed. This design allows the network to scale horizontally and supports specialized synchronizers for dif

add more architecture docs (possibly starting with the architecture currently in the scan bulk api docs) Daml Code Architecture Package Structure The Daml code implementing Canton Coin (CC), the Canton Name Service (CNS), and Global Synchronizer governance is implemented in seven packages: •

The complete OpenAPI specification for the Scan API is published as a generated reference under Splice APIs Scan API . It is organized by tag and includes the request and response schemas for every endpoint. For an overview of the individual Scan API surfaces (current state, bulk data, aggregates,

cURL Python JavaScript PHP Go Java Ruby curl --request GET \ --url 'http://localhost:7575/v2/traffic/accounts/{account-id}' \ --header 'Authorization: Bearer $TOKEN' import json import requests url = "http://localhost:7575/v2/traffic/accounts/{account-id}" headers = {'Autho

cURL Python JavaScript PHP Go Java Ruby curl --request POST \ --url 'http://localhost:7575/v2/traffic/accounts' \ --header 'Authorization: Bearer $TOKEN' \ --header 'Content-Type: application/json' \ --data '{ "accountId": "<string>", "balanceDelta": 123, "deduplicationId":

Semantic versioning, release cadence, and support duration are defined in Releases and Versioning . This page defines: the public API surface, status labels, and the compatibility rules between components. The public API Stable features and components constitute the “public API” in the sense of

This page walks through a Delivery-versus-Payment (DvP) trade between two parties whose assets live on different synchronizers. The example shows how Canton’s reassignment protocol enables atomic settlement without requiring all assets to originate on the same infrastructure. Setup Parties and r

Release of Canton 3.5.16 Canton 3.5.16 has been released on September 03, 2026. Summary This is a maintenance release that brings few minor improvements and bug fixes. What’s New Bugfixes • Added additional validation of the request timestamp in confirmation response processing. CantonB

Local Traffic Accounting The validator provides an optional local traffic accounting feature, that allows participant operators to track the synchronizer traffic spent per transaction and tie it back to an account. The account is implicitly tied to the (actAs) party that submitted the transactio

Canton returns structured error information through gRPC responses. Every error carries a machine-readable code, a category that determines the gRPC status code, and a human-readable description. You can use these components to build automated error handling in your application. Machine-readable e

SV Operations Schedule and release calendar The official SV Operations Schedule (also called the Canton Network release calendar ) lives at: https://sv-cal.canton.foundation/ Use that calendar whenever you need a specific release date , upgrade window, or network operations timeline. It is the s

The Ledger API is structured as a set of services. This page gives more detail about each of the services in the API, and will be relevant whichever way you’re accessing it. If you want to read low-level detail about each service, see the protobuf documentation of the API . Overview The API is

Overview Privacy-enabled assets on the Canton Network, such as DA Registry assets, require a specialized mechanism for users to verify transaction outcomes while preserving the privacy of the involved parties. Users need a way to independently and indisputably verify that an asset transfer was suc

1.10.0 — 2026-09-01 🚀 Features • allow to alter signing provider for wallets ( #2333 ) • make hashing scheme configurable ( #2372 ) • add BitGo TSS MPC signing driver ( #2163 ) 🩹 Fixes • enable use of env var for specifying postgres password in WG config ( #2385 ) • fix build ( #2377 ) •

The Canton Network incentivizes application providers through a reward system tied to network activity. Applications that generate value on the network can earn Canton Coin (CC) as rewards. The network is transitioning from on-ledger activity markers to traffic-based app rewards under CIP-0104 . B

Canton Coin (CC) is the native utility token of the Global Synchronizer. It is implemented through the Splice open-source infrastructure, where it is referred to as “Amulet” at the Daml contract level. CC serves three functions: paying for network usage (traffic), rewarding infrastructure operators

If you’re coming from Ethereum, Solana, or another blockchain platform, Canton will feel both familiar and fundamentally different. This section maps concepts you know to their Canton equivalents - and highlights where mental models must shift. Core Concept Mapping The following table maps famil

cURL Python JavaScript PHP Go Java Ruby curl --request GET \ --url 'http://localhost:7575/v2/packages' \ --header 'Authorization: Bearer $TOKEN' import json import requests url = "http://localhost:7575/v2/packages" headers = {'Authorization': 'Bearer <token>'} response = re

cURL Python JavaScript PHP Go Java Ruby curl --request GET \ --url 'http://localhost:7575/v2/idps' \ --header 'Authorization: Bearer $TOKEN' import json import requests url = "http://localhost:7575/v2/idps" headers = {'Authorization': 'Bearer <token>'} response = requests.r

cURL Python JavaScript PHP Go Java Ruby curl --request GET \ --url 'http://localhost:7575/v2/interactive-submission/preferred-package-version' \ --header 'Authorization: Bearer $TOKEN' import json import requests url = "http://localhost:7575/v2/interactive-submission/prefer

cURL Python JavaScript PHP Go Java Ruby curl --request GET \ --url 'http://localhost:7575/v2/packages/{package-id}' \ --header 'Authorization: Bearer $TOKEN' import json import requests url = "http://localhost:7575/v2/packages/{package-id}" headers = {'Authorization': 'Bear

cURL Python JavaScript PHP Go Java Ruby curl --request GET \ --url 'http://localhost:7575/readyz' \ --header 'Authorization: Bearer $TOKEN' import json import requests url = "http://localhost:7575/readyz" headers = {'Authorization': 'Bearer <token>'} response = requests.req

cURL Python JavaScript PHP Go Java Ruby curl --request GET \ --url 'http://localhost:7575/v2/authenticated-user' \ --header 'Authorization: Bearer $TOKEN' import json import requests url = "http://localhost:7575/v2/authenticated-user" headers = {'Authorization': 'Bearer <to

cURL Python JavaScript PHP Go Java Ruby curl --request GET \ --url 'http://localhost:7575/v2/package-vetting' \ --header 'Authorization: Bearer $TOKEN' \ --header 'Content-Type: application/json' \ --data '{ "packageMetadataFilter": { "packageIds": [ "<string>" ],

cURL Python JavaScript PHP Go Java Ruby curl --request DELETE \ --url 'http://localhost:7575/v2/users/{user-id}' \ --header 'Authorization: Bearer $TOKEN' import json import requests url = "http://localhost:7575/v2/users/{user-id}" headers = {'Authorization': 'Bearer <token

cURL Python JavaScript PHP Go Java Ruby curl --request GET \ --url 'http://localhost:7575/livez' \ --header 'Authorization: Bearer $TOKEN' import json import requests url = "http://localhost:7575/livez" headers = {'Authorization': 'Bearer <token>'} response = requests.reque

cURL Python JavaScript PHP Go Java Ruby curl --request GET \ --url 'http://localhost:7575/v2/idps/{idp-id}' \ --header 'Authorization: Bearer $TOKEN' import json import requests url = "http://localhost:7575/v2/idps/{idp-id}" headers = {'Authorization': 'Bearer <token>'} res