> 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/architecture/canton-network-topology.md).

# Canton Network Topology

CAT-BM can operate a private Canton subnet, participate in the global Canton Network, or bridge between the two.

<figure><img src="/files/BW5ITC1l2TFl6M4EYMiy" alt="Canton Network topology"><figcaption><p><strong>Figure 3.</strong> Canton Network topology</p></figcaption></figure>

## Private Canton subnet

**Private sync domain.** A dedicated sync domain operated by the organisation to coordinate transaction sequencing for private participants. This domain is isolated from the public internet and only accessible to authorised participants within the subnet.

**Multiple participants.** Several participant nodes are connected to the private sync domain. Each participant represents an entity within the consortium or organisation and can transact with other participants in the subnet without exposing transaction data externally.

## Bridge validator

**Dual-domain membership.** One validator node in the subnet is connected both to:

* the **private sync domain** — enabling it to validate and interact with the private subnet's transactions; and
* the **global sync domain** — providing access to the broader Canton ecosystem.

**Bridging role.** This validator acts as a controlled gateway between the private subnet and the global network. It allows specific assets, contracts, or parties to be visible and interoperable across domains while maintaining the privacy of all other data.

## Global Canton Network integration

**Global sync domain.** A publicly reachable sync domain operated by the global Canton Network, enabling interoperability between participants worldwide.

**Onboarding via a Super Validator.** The bridge validator is granted membership of the global sync domain through a Super Validator — an authoritative, trusted validator in the global domain that handles permissioning and trust establishment for new validators.

## Connectivity flow

<table><thead><tr><th width="230">Flow</th><th>Behaviour</th></tr></thead><tbody><tr><td><strong>Private transactions</strong></td><td>Participants in the private sync domain transact securely and privately.</td></tr><tr><td><strong>Selective exposure</strong></td><td>The bridge validator can selectively expose certain contracts or parties to the global Canton Network.</td></tr><tr><td><strong>Trust establishment</strong></td><td>The Super Validator ensures the bridge validator is recognised and trusted in the global sync domain.</td></tr><tr><td><strong>Cross-domain workflows</strong></td><td>Once onboarded, workflows can span both the private subnet and the global Canton Network, enabling collaboration without compromising confidentiality.</td></tr></tbody></table>

## Related Canton documentation

Canton's own protocol documentation covers network topology in depth. CAT-BM does not restate it; see the [Canton documentation](https://docs.canton.network/) for protocol-level detail.


---

# 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/architecture/canton-network-topology.md?ask=<question>&goal=<endgoal>
```

`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.