> For the complete documentation index, see [llms.txt](https://docs.bitsafe.finance/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.bitsafe.finance/cbtc-1/overview.md).

# Overview

### CBTC brings Bitcoin into Canton workflows

CBTC is BitSafe’s representation of Bitcoin for applications and institutions operating on Canton Network. It gives teams a documented path to hold, transfer, mint, redeem, and integrate Bitcoin-backed value within Canton applications.

This page explains what CBTC is and routes readers to the right task. Detailed lifecycles, setup values, APIs, architecture, and security controls live in their canonical pages.

### What you can do

* Hold and transfer CBTC between authorized Canton parties.
* Mint CBTC from an eligible Bitcoin deposit.
* Redeem CBTC to an approved Bitcoin destination.
* Integrate supported CBTC workflows through pinned libraries and APIs.
* Review custody, privacy, backing evidence, and operational controls.

### Choose a path

| Goal                             | Canonical page                                                                                                                                                                |
| -------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Understand the lifecycle         | [How CBTC works](/cbtc-1/how-cbtc-works.md)                                                                                                                                   |
| Choose an operation              | [Choose a CBTC path](/cbtc-1/choose-a-cbtc-path.md)                                                                                                                           |
| Build an integration             | [CBTC developer Quick Start](/cbtc-1/get-started/developer-quick-start.md)                                                                                                    |
| Review architecture and security | [CBTC architecture and trust boundaries](/cbtc-1/concepts-and-reference/architecture-and-trust-boundaries.md) and [CBTC security](/cbtc-1/concepts-and-reference/security.md) |
| Check releases and compatibility | [CBTC compatibility and release notes](/cbtc-1/concepts-and-reference/compatibility-and-release-notes.md)                                                                     |

### Product boundaries

CBTC spans Bitcoin and Canton, but Bitcoin does not move on Canton during every transfer. Bitcoin deposits and redemptions are coordinated with corresponding CBTC state changes. Canton’s configurable sub-transaction privacy applies to entitled Canton contract data; Bitcoin transactions remain visible on Bitcoin.

CBTC is intended to remain backed 1:1 by Bitcoin. The evidence, calculation path, and limitations belong in [CBTC Proof of Reserve](/cbtc-1/concepts-and-reference/proof-of-reserve.md).

### Technical sources

* [CBTC library](https://github.com/DLC-link/cbtc-lib)
* [Shared Canton library](https://github.com/DLC-link/canton-lib)

### Next step

👉 **Understand the operating model:** [How CBTC works](/cbtc-1/how-cbtc-works.md).


---

# 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.bitsafe.finance/cbtc-1/overview.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.