LEARN · DOCUMENTATION

Documentation

Pages from 29 sources, kept in sync: the official Canton Network and Digital Asset docs, documentation from teams building on Canton, and readmes from their code. Search all of it, or start from a path below.

3,253pages

synced 3h ago29 sources

This week489pages updated upstream NewestLogical Synchronizer UpgradesNov 6, 2026 Official1,638pages from Canton and Digital Asset

Try

validator onboarding token standard ledger api party upgrade

Search CIPs, forum and docs for “validator onboarding”

All sources150 Canton Network docs79 CatalyX docs34

11 more sources37 pages

GitHub code12 Digital Asset docs7 Canton Foundation4 CCView4 Five North docs4 Canton 1011 Canton Dev Fund1 Canton Ecosystem1 cc.itrocket.space1 CCView docs1 ftptech.xyz1

Showing“validator onboarding”Canton Network docs

OfficialCanton Network docs · … › Wallet SDK › Using the SDK › v0 to v1 migration

Party Namespace

The party namespace provides methods to manage wallet parties on the Canton Network. In v1, the party namespace replaces the stateful party management from v0. Availability The par…

OfficialCanton Network docs · Resources

…lobal Synchronizer, used for transaction fees (traffic) and validator rewards. Formerly referred to as “Amulet” in some contexts. Related : Traffic, Global Synchronizer, Splice Can…

OfficialCanton Network docs · Global Synchronizer & Tokenomics

SV Governance Reference

The Global Synchronizer is governed by its Super Validators (SVs) acting collectively as the Decentralized Synchronizer Operator (DSO). Governance decisions are made thr…

OfficialCanton Network docs · SDKs › Wallet SDK › Guides

Preparing and Signing a Transaction

…xamples use the Ping app which comes pre-installed with the validator and the cURL examples show the underlying HTTP requests using Canton Coin following a token standard transfer.…

OfficialCanton Network docs · Production Operations

… global topology state of the network: they determine which Validators host a party, what rights that party grants to the Validator (submission, confirmation, or observation), and …

OfficialCanton Network docs · Super Validator Deployment

Super Validator Helm Deployment

This section describes deploying a Super Validator (SV) node in kubernetes using Helm charts. The Helm charts deploy a complete node and connect it to a target c…

OfficialCanton Network docs · SDKs › Wallet SDK › Guides

Creating an External Party

Overview Parties represent acting entities in the network and all transaction happens between one or more parties. To understand more about parties see the Parties in the Overview.…

OfficialCanton Network docs · Deep Dives › QuickStart

Using the JSON Ledger API

… ├── licensing/daml/Licensing/ │ │ ├── AppInstall.daml user onboarding │ │ ├── License.daml license management │ │ └── Util.daml helper functions │ ├── licensing-tests/ Daml Script…

OfficialCanton Network docs · CIPs

CIP-0056 defines the Canton Network Token Standard — a set of Daml interfaces and off-ledger APIs that allow wallets and applications to interact with tokenized assets across regis…

OfficialCanton Network docs · Module 4: Full-Stack Application Development

Backend Development

…o the Ledger API The Ledger API is a service exposed by the validator’s participant node. Your backend connects to it as an authenticated client, acting on behalf of one or more pa…

OfficialCanton Network docs · Protocol Deep Dive

Ordering Consensus

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 pa…

OfficialCanton Network docs · Reference

Canton Console Commands

…lete new sequencer initialization. Fourth step of sequencer onboarding. In most cases, the onboarding command is preferred. Arguments • newSequencer: com.digitalasset.canton.consol…

OfficialCanton Network docs · Troubleshooting

Transaction Failures

…ist Wrong Party If you see authorization errors right after onboarding, verify that your party ID matches what was registered: @ participant1.parties.list() res1: Seq[ListPartiesRe…

OfficialCanton Network docs · Reference

Error Code Reference

Canton uses a structured error code system across all components. Every error logged or returned via the API follows the format ERROR_CODE_ID(category_id, correlation_id_prefix): h…

OfficialCanton Network docs · Deep Dives › QuickStart

Observability and Tracing

Canton Network Quickstart observability & troubleshooting overview The screenshots in this guide are taken from multiple sessions and are inconsistent with each other. This will be…

OfficialCanton Network docs · Admin API › gRPC API › Packages

com.digitalasset.canton.admin.participant.v30

Back to overview Protobuf Package com.digitalasset.canton.admin.participant.v30 12 services, 81 endpoints, 193 messages, 9 enums gRPC Added 3.7.0 Updated 3.5.1 Methods removed in 3…

OfficialCanton Network docs · Release Notes › Canton

… commitments landed in protocol version 36. • Decouples the validator memory usage from the number of hosted parties and their stakeholder groups to lift party growth restrictions …

OfficialCanton Network docs · Protocol Deep Dive

Pruning As a synchronizer orchestrates the execution of commands, the sequencers, mediators and participant persist records of the data/changes that they process: • For participant…

OfficialCanton Network docs · Protocol Deep Dive

Topology management All Participant Nodes and Synchronizer components must know the topology state of a Synchronizer, which includes all identities on the Synchronizer and their as…

Showing 61 to 79 of 79Search all sources →