Technical Reference
⚠️
Token Details
Section titled “Token Details”| Property | Value |
|---|---|
| Name | CBTC (Canton Bitcoin) |
| Standard | CIP-56 (Token Standard V1) and CIP-112 (Token Standard V2) |
| Backing | 1:1 with native BTC |
| Network | Canton Network |
| Deposit requirement | Taproot-compatible Bitcoin wallet (P2TR) |
| Transaction limits | 0.0001 BTC minimum, 5 BTC maximum by default. Set per account and adjustable on request |
| Confirmations | 6 Bitcoin blocks (~60 minutes) |
| Audit | Quantstamp |
Network Environments
Section titled “Network Environments”| Environment | Registry URL | Coordinator URL | Bitcoin Network |
|---|---|---|---|
| Devnet | https://api.utilities.digitalasset-dev.com |
https://devnet.dlc.link/attestor-2 |
Bitcoin Testnet |
| Testnet | https://api.utilities.digitalasset-staging.com |
https://testnet.dlc.link/attestor-1 |
Bitcoin Testnet |
| Mainnet | https://api.utilities.digitalasset.com |
https://mainnet.dlc.link/attestor-1 |
Bitcoin Mainnet |
For full Instrument IDs per network, see Instrument ID Management.
Canton Network Requirements
Section titled “Canton Network Requirements”To interact with CBTC you need:
- Canton participant node - connected to the target network (devnet/testnet/mainnet)
- CBTC DAR files - installed on your participant. All versions must be installed to access all live contract versions.
- Download: github.com/DLC-link/cbtc-lib/tree/v0.9.0/cbtc-dars (latest DAR:
cbtc-1.2.1)
- OIDC provider - Keycloak (officially supported) or Auth0 (community example)
- Canton CLI - version 3.3.0+ for DAR upload scripts
- Prerequisites for CLI:
jq,curl,java(11+)
DAR Upload
Section titled “DAR Upload”git clone https://github.com/DLC-link/cbtc-libcd cbtc-lib/cbtc-dars# Edit misc/connect.conf to point to your participantcanton run 00_UploadDars.sc -c ./misc/connect.confThe upload script is idempotent - safe to re-run.
Fee Structure
Section titled “Fee Structure”✅ Confirmed: Mint and burn fees are 0%. There are no BitSafe fees on CBTC mint or burn operations.
Canton Transfer Costs
Section titled “Canton Transfer Costs”- CBTC transfers on Canton cost approximately $3-5 per transaction (network gas, not BitSafe fees)
- Cost varies based on payload size and UTXO count
- Sending CBTC is generally more expensive than sending Canton Coin (CC) due to larger payload
GitHub Repositories
Section titled “GitHub Repositories”| Repository | Version | Description | Link |
|---|---|---|---|
| cbtc-lib | v0.9.0 |
Rust SDK for CBTC operations (mint, burn, transfer) | GitHub |
| canton-lib | v0.11.0 |
Lower-level Canton interaction library | GitHub |
| CBTC DAR | cbtc-1.2.1 |
Daml packages, upload scripts, connect config | GitHub |
Note: The crate name is cbtc. DAR versions and crate versions are numbered independently: cbtc-lib v0.9.0 ships DAR cbtc-1.2.1.
Transfer Speed
Section titled “Transfer Speed”- Canton transfers take a few seconds each
- Practical throughput: ~500 transfers per 10-minute period
- UTXO limit: 10 UTXOs per party (Canton recommendation). Exceeding this increases load and fees.
External Links
Section titled “External Links”- CBTC Technical Documentation (live site)
- Canton Network
- Canton Developer Docs
- FROST Whitepaper
- Quantstamp Audit Report
- Canton Whitepaper
- Chainlink Proof of Reserve (CBTC)
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: