Products · Assets · CBTC
Overview
CBTC brings Bitcoin into Canton workflows
Section titled “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
Section titled “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
Section titled “Choose a path”| Goal | Canonical page |
|---|---|
| Understand the lifecycle | How CBTC works |
| Choose an operation | Choose a CBTC path |
| Build an integration | CBTC developer Quick Start |
| Review architecture and security | CBTC architecture and trust boundaries and CBTC security |
| Check releases and compatibility | CBTC compatibility and release notes |
Product boundaries
Section titled “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.
Technical sources
Section titled “Technical sources”Next step
Section titled “Next step”Understand the operating model: How CBTC works.
Ask the docs
Answers come only from this documentation and can be wrong. Check the linked pages.
Ask a question about BitSafe, CBTC or the developer guides. For example: