> For the complete documentation index, see [llms.txt](https://docs.catalyx.solutions/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.catalyx.solutions/catalyx-blockchain-manager/canton-network/version-2.0/introduction-to-canton-network.md). # Introduction to Canton Network This section covers the introduction to the Canton Network, including its core components, architecture, and key concepts relevant to operating nodes with CatalyX Blockchain Manager. ## What is Canton Network? Canton Network is a public layer 1 blockchain designed for privacy-preserving transactions. Unlike traditional blockchains where all transactions are visible to all participants, Canton enables selective disclosure - parties see only the data they’re entitled to see. {% embed url="" %} ## Core Concepts Please refer to the Canton Network documentation to learn more about the core concepts of the Canton Network. {% embed url="" %} *** ## Glossary This section defines the key business and technical terms used throughout CatalyX Blockchain Manager and the Canton integration. Use it as the first reference when encountering unfamiliar terminology.
Business Concepts | **Term** | **Definition** | | --------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | **Party** | A **party** is an on-ledger identity in Canton—analogous to an address or account on other blockchains, but with explicit authorization semantics. | | **Validator** | A **validator** hosts parties, stores their contract data, and participates in the Canton protocol. A validator contains a participant node (the Daml execution engine) plus a validator process. | | **Super Validator** | A special Canton participant node that participates in network governance, permissioning, and topology management on the global sync domain. | | **Splice** | The open-source governance and reward infrastructure for the Canton Network. | | **CatalyX** | IntellectEU's suite of blockchain infrastructure products built on Canton and other protocols. | | **CAT-BM** | CatalyX Blockchain Manager, IntellectEU's platform for deploying and operating Canton and other DLT infrastructure. | | **CPM** | CatalyX Package Manager, the application registry for discovering, publishing, and downloading Canton applications. | | **GSF / Canton Foundation** | Global Synchronizer Foundation, which governs the Global Sync Domain on Canton. |
Technical Concepts | **Term** | **Definition** | | ------------------------------------ | --------------------------------------------------------------------------------------------------------------- | | **Ledger API** | The gRPC API exposed by Canton participant nodes for submitting and reading transactions. | | **Admin API** | The API for managing participant configuration, parties, and packages. | | **Topology** | The configuration of domains, participants, parties, and their relationships on the network. | | **PartyToParticipant mapping** | The topology record that says which participants host a party, with what permission and confirmation threshold. | | **Confirmation threshold** | How many confirming hosts must confirm each of a party's transactions. | | **PQS (Participant Query Store)** | A queryable off-ledger store for Canton contract data. | | **KMS driver** | Canton integration module that delegates key operations to an external KMS or HSM. | | **WaaS** | Wallet-as-a-Service — an external key custody and signing service supported by CAT-BM. | | **ArgoCD** | GitOps continuous-delivery tool used to synchronise desired state from Git into the Kubernetes cluster. | | **Helm chart** | Kubernetes packaging format used to deploy Canton components. | | **CRD (Custom Resource Definition)** | Kubernetes extension used by the CAT-BM Canton Operator to manage node lifecycle. | | **CAT-BM Canton Operator** | Custom Kubernetes operator that watches CRDs and reconciles Canton component state. | | **Round** | 10-minute cycle on Canton Network governing minting and distribution of Canton Coin. |
*** ## Learn More | **Resource** | **Purpose** | | --------------------------------------------------------------------------------------------------------------- | ---------------------------------------------------------- | | [Canton Network Website](https://canton.network/) | Official Canton Network site | | [Canton Network Docs](https://docs.canton.network/) | Official Canton Network documentation | | [Canton Network Github](https://github.com/canton-network) | Canton Network repositories, including Splice | | [Canton Network Whitepaper](https://www.digitalasset.com/hubfs/Canton/Canton%20Network%20-%20White%20Paper.pdf) | Official Canton Network whitepaper | | [Digital Asset / Daml Documentation](https://docs.digitalasset.com/) | Canton and Daml technical documentation from Digital Asset | | [Canton Foundation Website](https://canton.foundation/) | GSF governance, committees, and network information | | [CIPs](https://github.com/canton-foundation/cips) | Canton Improvement Proposals | *** --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.catalyx.solutions/catalyx-blockchain-manager/canton-network/version-2.0/introduction-to-canton-network.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.