Canton Network is a public layer 1 blockchain with native privacy, designed for regulated assets and multi-party financial workflows.
Canton distributes transaction processing across the participant nodes involved in each transaction instead of requiring every node to execute and store every transaction. Capacity can scale horizontally as parties and workloads are distributed across more participant nodes.
Canton is designed for regulated financial workflows including tokenized securities and cash, payments, collateral, repo and securities financing, trading, custody, clearing, and settlement.
Start today with Canton Network infrastructure deployed in the cloud or self-hosted, and managed by your team or ours.
| Consensus | Canton uses two consensus layers. Affected participant nodes validate Daml transaction views using Proof of Stakeholder. Synchronizer sequencers establish a consistent order with Byzantine Fault Tolerant consensus, while mediators collect confirmations and issue commit or reject verdicts. The Global Synchronizer is operated by independent Super Validators. |
| Public / Private / Permissioned | Public network with configurable application access and privacy. Validator onboarding currently requires sponsorship, and TestNet and MainNet deployments require approval. Applications can be permissioned or permissionless, while Daml contracts define who can see and act on data. |
| Smart contracts | Yes |
| Smart contract language(s) supported | Daml |
| Transaction privacy | Native sub-transaction privacy. Each transaction is divided into encrypted views and sent only to entitled participants. Synchronizers cannot read transaction payloads. |
| Transaction visibility | Canton application transactions are not published to every network participant. Participant nodes store only the data relevant to the parties they host. Canton Coin balances and transaction history are publicly visible through the network's Scan service. |
| Transaction ordering | Sequencers establish a total order for messages on each synchronizer. Affected participants validate their transaction views, mediators collect confirmations, and participants commit the result atomically. Once a commit verdict is sequenced, it is final with no forks or reorganizations. |