Documentation

Causality Daml ledgers do not totally order all transactions. So different parties may observe two transactions on different Participant Nodes in different orders via the gRPC Ledger API. Moreover, different Participant Nodes may output two transactions for the same party in different orders. This

Daml Shell Daml Shell is a component that enables you to interactively query ledger data made available in the Participant Query Store (PQS) PostgreSQL database. Overview Daml Shell provides an interactive terminal session to examine the current and historical state of the ledger by querying

Work through this checklist before running a Wallet Gateway in production. Each item links to the relevant configuration. Authentication and identity • Use OAuth / OpenID Connect IDPs. Reserve self-signed tokens for development. See Networks & identity providers . • Use client_credentials for

Use this table to look up the v1 equivalent of a v0 controller method. For context and before/after examples, see the migration overview and the namespace pages. Migration reference table v0 controller + method | v1 namespace + method | createKeyPair() | sdk.keys.generate() | sdk.userLedg

Release of Canton 3.5.10 Canton 3.5.10 has been released on July 23, 2026. Summary This is a maintenance release that brings UX and hardening improvements. What’s New Minor Improvements • Fixed an edge case that could cause deserialization of proto durations to fail • Fixed an issue wher

0.4.0 Released on September 10th, 2025 • Range filter for listHoldingTransactions(afterOffset?: string,beforeOffset?: string) • Transfer pre-approval support: const sdk = new WalletSDKImpl().configure({ logger, authFactory: localNetAuthDefault, ledgerFactory: localNetLedgerDef

To enable deposits to be sent to specific user accounts at exchanges, an account identifier needs to be sent to the exchange along with the transfer information. In Canton, this is implemented with the “memo tag” pattern . Exchanges — using memo tags to receive and allocate funds Memos are store

When integrating with the Canton Network, we recommend that wallet providers support the necessary features outlined below to optimal user experience. Additionally, there are optional features that can further enhance the integration and provide additional value to users. Necessary Features The

The dApp SDK is a TypeScript library for connecting web applications to wallets on Canton Network. It lets your frontend discover wallets, authenticate the user, read their parties, request signatures, and submit transactions. Use the SDK to: • Discover available wallets : browser extensions, remo

By default, sdk.init() makes the wallet picker list every CIP-103 wallet the SDK can discover: browser wallets that announce themselves, plus the SDK’s built-in list of remote wallets. Registering adapters lets you add more wallets (such as WalletConnect or a custom remote wallet) or restrict the

This guide covers the connection lifecycle: initializing the SDK, connecting a wallet, inspecting connection status, restoring a returning user’s session, and disconnecting. All examples use the high-level SDK. For the equivalent low-level calls, see the Provider API . Connection flow A dApp c

The dApp SDK emits events so your UI can stay in sync with the wallet’s state. Subscribe with the on* functions and unsubscribe with the matching off* function. For usage examples, see Handle Events . onStatusChanged(handler) / offStatusChanged(handler) Fires when the connection status o

The dApp SDK emits events so your UI can stay in sync with the wallet’s state. Subscribe with the on* functions and always unsubscribe with the matching off* function when your component unmounts. For the full list of events and their payloads, see the Events reference . React to connection

The Provider API is the low-level interface the dApp SDK is built on. It follows the EIP-1193 request/event pattern and implements CIP-103 . Most dApps should use the high-level SDK . Use the Provider API directly only when building lower-level infrastructure or adapting an existing provider-bas

This section is for wallet authors who want their wallet to be CIP-103 compatible, so it can interoperate with Canton dApps and be listed in the wallet picker the dApp SDK opens on connect(). Choose one or more of the integration paths below. Choose your integration How your wallet connects |

Lifecycle init(options?) Registers wallet adapters and silently restores a previous session without opening the wallet picker. Call once, early in the app lifecycle. Parameter | Type | Description | options.additionalAdapters | Adapter[] | Extra adapters to register alongside the default

WalletConnect lets mobile and cross-device wallets connect to dApps. Wallets add Canton support through the WalletConnect wallet SDK; dApps enable WalletConnect by registering the WalletConnectAdapter, which is covered in Wallet discovery . Add Canton support to your wallet Follow the officia

This page covers the configuration options available to validator and Super Validator (SV) operators on Canton Network. It covers Splice app configuration, Canton participant settings, database setup, authentication, traffic management, pruning, and observability. For application developer configur

Release of Canton 3.5.8 Canton 3.5.8 has been released on July 09, 2026. Summary This is a maintenance release that brings several operational improvements. What’s New Improvements to TopologyManagerReadService and TopologyAggregationService • The services return the error TOPOLOGY_S

Release of Canton 3.5.9 Canton 3.5.9 has been released on July 16, 2026. Summary This is a maintenance release that brings few minor improvements. What’s New Minor Improvements • Improved and relaxed DB locking-scheme to avoid colliding with pg_dump execution. Also introduced better visib

For detailed troubleshooting steps, see the topic guides below. For diagnostic and debugging tooling, see Debugging Tools . Installation Issues Nix shell failures, Docker configuration, memory allocation, JDK setup. Development Issues Daml compilation errors, API connection problems, transacti

Operating a validator on Canton Network comes with specific roles, responsibilities, and expectations. This page clarifies what’s expected of validators versus what the network handles. The Validator’s Role As a validator, you operate a participant node that: • Hosts parties for users and appli

The Canton Foundation (CF) is an independent non-profit organization created in partnership with the Linux Foundation. It governs the Global Synchronizer, the decentralized interoperability and synchronization infrastructure of the Canton Network. Purpose and role The CF provides transparent gov

Connectivity failures prevent your validator from communicating with the synchronizer. The symptoms vary — from outright connection refusals to subtle TLS handshake errors — but the diagnostic approach is consistent. Cannot Connect to Synchronizer If your validator logs show: Request failed

This page introduces the development stack you’ll use to build Canton applications. Understanding these components helps you see how everything fits together. Stack Overview Smart Contract Layer Daml Daml is Canton’s smart contract language—a functional language designed for multi-party work

This section provides an overview of which information can be collected to debug issues in a Canton Network node. For direct console access to a Canton node, see the Canton Console Reference . Where to find logs When launched locally , splice-node will create a log/ directory located at the ro

The cn-quickstart repository is a complete example application that demonstrates how to build, test, and run a Canton Network application. It includes Daml smart contracts, a Java backend, a React frontend, and a LocalNet environment for local development. Repository Overview Clone the repositor

Supported Cryptographic Schemes And Formats Within Canton, we use the cryptographic primitives of signing, symmetric encryption, and asymmetric encryption, with the following supported cryptographic schemes and formats. For asymmetric signing and encryption, each scheme is divided into a key and a

The Super Validators operate three(3) different networks: • DevNet • TestNet • MainNet DevNet This network functions as a staging ground for TestNet, enabling the configuration of DevNet to facilitate seamless exploration, including self-featured applications, CC tapping, and validator node s

You can check your validator’s health using the readiness endpoints. All CN applications provide the /readyz and /livez endpoints, which are used for readiness and liveness probes. • Checking readiness • In Kubernetes: readiness and liveness probes are already configured. You can also manua