Technical Reference
👥 Audience: All developers. Quick-reference for contract addresses, token details, network info, and fee structure.
⚠️ All addresses and technical details require Engineering verification before publication. Values below are sourced from internal documentation and may not reflect the latest live deployments.
Token Details
Name
CBTC (Canton Bitcoin)
Standard
CIP-56 (Canton Instrument Protocol)
Backing
1:1 with native BTC
Network
Canton Network
Deposit requirement
Taproot-compatible Bitcoin wallet (P2TR)
Minimum mint
0.001 BTC
Confirmations
6 Bitcoin blocks (~60 minutes)
Audit
Network Environments
Testnet
Bitcoin Testnet
For full Instrument IDs per network, see Instrument ID Management.
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.
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
The upload script is idempotent — safe to re-run.
Fee Structure
✅ Confirmed: Mint and burn fees are 0%. There are no BitSafe fees on CBTC mint or burn operations.
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
Note: cbtc-lib (crate name: cbtc) is at v0.3.0. It depends on canton-lib v0.3.0. Update your dependencies if using an earlier version. See the cleanup PR.
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
🔴 ⚙️ Engineering Review Required — All addresses, URLs, fee information, and technical details must be validated by Engineering (Jesse or Robert) against live deployments before publication.
Last updated