Documentation

cURL cURL curl --request POST \ --url https://api.utilities.digitalasset.com/api/utilities/v0/registry/mint/v0/offer \ --header 'Content-Type: application/json' \ --data ' { "holder": "<string>", "instrumentId": { "admin": "<string>", "id": "<string>" } } ' import

cURL cURL curl --request POST \ --url https://api.utilities.digitalasset.com/api/token-standard/v0/registrars/{registrarParty}/registry/allocations/v1/{allocationId}/choice-contexts/cancel \ --header 'Content-Type: application/json' \ --data '{ "meta": {} }' import requests u

cURL cURL curl --request POST \ --url https://api.utilities.digitalasset.com/api/token-standard/v0/registrars/{registrarParty}/registry/allocations/v1/{allocationId}/choice-contexts/withdraw \ --header 'Content-Type: application/json' \ --data '{ "meta": {} }' import requests

cURL cURL curl --request POST \ --url https://api.utilities.digitalasset.com/api/token-standard/v0/registrars/{registrarParty}/registry/allocations/v1/{allocationId}/choice-contexts/execute-transfer \ --header 'Content-Type: application/json' \ --data '{ "meta": {} }' import r

cURL cURL curl --request POST \ --url https://api.utilities.digitalasset.com/api/token-standard/v0/registrars/{registrarParty}/registry/allocation-instruction/v1/allocation-factory \ --header 'Content-Type: application/json' \ --data ' { "choiceArguments": {}, "excludeDebugFields": f

cURL cURL curl --request POST \ --url https://api.utilities.digitalasset.com/api/token-standard/v0/registrars/{registrarParty}/registry/transfer-instruction/v1/{transferInstructionId}/choice-contexts/withdraw \ --header 'Content-Type: application/json' \ --data '{ "meta": {} }'

cURL cURL curl --request POST \ --url https://api.utilities.digitalasset.com/api/token-standard/v0/registrars/{registrarParty}/registry/transfer-instruction/v1/{transferInstructionId}/choice-contexts/reject \ --header 'Content-Type: application/json' \ --data '{ "meta": {} }'

cURL cURL curl --request POST \ --url https://api.utilities.digitalasset.com/api/token-standard/v0/registrars/{registrarParty}/registry/transfer-instruction/v1/{transferInstructionId}/choice-contexts/accept \ --header 'Content-Type: application/json' \ --data '{ "meta": {} }'

cURL cURL curl --request POST \ --url https://api.utilities.digitalasset.com/api/token-standard/v0/registrars/{registrarParty}/registry/transfer-instruction/v1/transfer-factory \ --header 'Content-Type: application/json' \ --data ' { "choiceArguments": {}, "excludeDebugFields": false

cURL cURL curl --request GET \ --url https://api.utilities.digitalasset.com/api/token-standard/v0/registrars/{registrarParty}/registry/metadata/v1/instruments/{instrumentId} import requests url = "https://api.utilities.digitalasset.com/api/token-standard/v0/registrars/{registrarPar

cURL cURL curl --request GET \ --url https://api.utilities.digitalasset.com/api/token-standard/v0/registrars/{registrarParty}/registry/metadata/v1/instruments import requests url = "https://api.utilities.digitalasset.com/api/token-standard/v0/registrars/{registrarParty}/registry/me

cURL cURL curl --request GET \ --url https://api.utilities.digitalasset.com/api/token-standard/v0/registrars/{registrarParty}/registry/metadata/v1/info import requests url = "https://api.utilities.digitalasset.com/api/token-standard/v0/registrars/{registrarParty}/registry/metadata/

Release of Canton 3.5.7 Canton 3.5.7 has been released on July 01, 2026. Summary This release provides a new Ledger API endpoint to obtain command completions and fixes a number of minor issues. What’s New New GetCompletions endpoint on the command completion service Background The c

The Java bindings produce type-safe classes from your compiled Daml packages. These classes let you create contracts, exercise choices, and process ledger events in Java without manually constructing gRPC messages or JSON payloads. Code Generation Generate Java bindings from a compiled DAR file:

Daml Script is the primary testing tool for Daml contracts. You write test scenarios as Script () values in Daml source files, then run them with dpm test. Scripts execute on a fresh, empty ledger and can allocate parties, submit commands, query state, and assert expected outcomes. For the comp

Release of Canton 3.5.5 Canton 3.5.5 has been released on June 17, 2026. Summary This is a maintenance release that fixes an exceptional but severe bug around logical synchronizer upgrades and brings a few improvements. What’s New Dependencies of vetted packages can be unvetted (PV35+) O

Release of Canton 3.5.2 Canton 3.5.2 has been released on June 03, 2026. Summary This is a maintenance release that fixes an out of memory issue during synchronizer reconnect, addresses security vulnerabilities in the Canton docker base image, as well as minor improvements. Minor Improvement

Release of Canton 3.5.3 Canton 3.5.3 has been released on June 03, 2026. Summary This is a maintenance release that fixes an issue around mediator restart and LSU. Bugfixes Mediator cannot reconnect to sequencer after processing LSU sequencing test message During LSU, after processing a

Release of Canton 3.5.4 Canton 3.5.4 has been released on June 10, 2026. Summary This is a maintenance release that fixes a bug around modify synchronizers and brings a few improvements. What’s New Minor Improvements • Config flag canton.participants.participant.parameter.alpha-multi-syn

Release of Canton 3.5.1 Canton 3.5.1 has been released on May 27, 2026. What’s New Contract Keys Overview Canton 3.5 introduces contract keys. Compared to a similar feature available in Canton 2.x, there are two notable differences: • The keys are not unique, meaning multiple contracts may sha

Release of Canton 3.5.6 Canton 3.5.6 has been released on June 24, 2026. Summary This is a maintenance release that fixes an exceptional severe bug around logical synchronizer upgrades and brings a few improvements. What’s New Minor Improvements • Connection pool metrics: • Add a psid

Participants form the core part of Canton’s distributed ledger architecture. A Participant provides a party-specific view of the distributed ledger, processes its Daml logic, and participates in the Canton protocol with other participants via the synchronizer. In essence, a Canton Participant is the

The Active Contracts Head Snapshot (ACHS) is an optional feature that maintains a continuously updated snapshot of the currently active contracts. When enabled, the ACHS accelerates GetActiveContracts (ACS) queries by allowing them to read directly from a pre-computed snapshot rather than scanning

The backend is the layer between your frontend and the Canton ledger. It submits commands, reads transactions, and queries contract state. This page uses cn-quickstart as a running example. cn-quickstart is a full-stack reference application that implements a software licensing workflow on Canton N

Daml Codegen for JavaScript Use the Daml Codegen for JavaScript (dpm codegen-js) to generate JavaScript/TypeScript code representing all Daml data types defined in a Daml Archive (.dar) file. The generated code makes it easier to construct types and work with JSON when using the JSON Ledger API

The Daml Compiler At the core of the Daml toolchain lies the Daml Compiler, also known as damlc. Its primary usage is to compile Daml source code, which defines smart contracts and their behaviours, into a lower-level language called Daml-LF, which Canton participants can evaluate in order to ru

Canton application development spans four environments, each serving a different stage of the development and deployment lifecycle. Your application moves through them sequentially: LocalNet for development, DevNet for early integration, TestNet for pre-production validation, and MainNet for product

The interaction of a Daml application with the ledger is inherently asynchronous: applications send commands to the ledger, and some time later they see the effect of that command on the ledger. Many things can fail during this time window: • The application can crash. • The participant node can c

Daml Studio is the Visual Studio Code extension for Daml development. It provides real-time feedback as you write Daml code, including type errors, syntax highlighting, and integrated test visualization. Installation Via dpm The extension is installed automatically when you set up the Daml SDK

The Admin API provides administrative access to Canton participant, sequencer, and mediator nodes. It is used for node configuration, topology management, key management, and operational tasks that are not exposed through the Ledger API. Never expose the Admin API to the public internet. Restrict