> 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/support-and-resources.md).

# Support & Resources

Additional support and resources for CAT-BM 2.0 for Canton.

<table data-view="cards"><thead><tr><th></th><th></th><th data-hidden data-card-target data-type="content-ref"></th></tr></thead><tbody><tr><td><strong>FAQ</strong></td><td>Frequently asked questions.</td><td><a href="https://docs.catalyx.solutions/catalyx-blockchain-manager/canton-network/version-2.0/support-and-resources/faq.md">FAQ</a></td></tr><tr><td><strong>API Reference</strong></td><td>The CatalyX REST API — endpoints, authentication, and error handling.</td><td><a href="https://docs.catalyx.solutions/catalyx-blockchain-manager/canton-network/version-2.0/support-and-resources/api-reference.md">API Reference</a></td></tr><tr><td><strong>Troubleshooting</strong></td><td>Common problems and where to look.</td><td><a href="https://docs.catalyx.solutions/catalyx-blockchain-manager/canton-network/version-2.0/support-and-resources/troubleshooting.md">Troubleshooting</a></td></tr><tr><td><strong>Open Source Licenses</strong></td><td>Licences used for the CAT-BM platform.</td><td><a href="https://docs.catalyx.solutions/catalyx-blockchain-manager/canton-network/version-2.0/support-and-resources/open-source-licenses.md">Open Source Licenses</a></td></tr></tbody></table>

## Getting help

For support requests, see the [Support Center](https://docs.catalyx.solutions/support-center.md) — it covers the service desk, contact details, and how to stay up to date with releases.

## External documentation

CAT-BM operates Canton; it does not replace Canton's own documentation. For protocol-level detail, go to the source:

| Resource                                                                  | Covers                                                                                                            |
| ------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------- |
| [Canton Network documentation](https://docs.canton.network/)              | Canton Network documentation and resources.                                                                       |
| [Digital Asset documentation](https://docs.digitalasset.com/)             | Daml documentation and resources, including topology, party hosting, KMS drivers, and the Participant Query Store |
| [Global Synchronizer Foundation](https://sync.global/)                    | Network governance, upgrade schedules, and validator operator guidance                                            |
| [Splice](https://github.com/hyperledger-labs/splice)                      | The open-source validator app, Wallet UI, and CNS UI                                                              |
| [Canton Improvement Proposals](https://github.com/canton-foundation/cips) | Proposed and accepted protocol and network changes                                                                |


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.catalyx.solutions/catalyx-blockchain-manager/canton-network/version-2.0/support-and-resources.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.
