Skip to content

Integrations

Integrate CBTC into a Canton wallet, DEX, or protocol. Use the same asset identifiers and registry URLs for each integration. Minting and redemption are separate workflows.

Use the fields for the intended environment. In Canton Token Standard calls, use the Registrar as InstrumentId.admin and CBTC as InstrumentId.id. Do not use the Operator as the instrument administrator.

Confirm current configuration before production use. Fields marked “Confirm with BitSafe” need confirmation before publication.

  • ID: CBTC
  • Operator: auth0_007c65f857f1c3d599cb6df73775::1220d2d732d042c281cee80f483ab80f3cbaa4782860ed5f4dc228ab03dedd2ee8f9
  • Provider: cbtc-network::12202a83c6f4082217c175e29bc53da5f2703ba2675778ab99217a5a881a949203ff
  • Registrar: cbtc-network::12202a83c6f4082217c175e29bc53da5f2703ba2675778ab99217a5a881a949203ff

Registry URL: https://api.utilities.digitalasset-dev.com

  • ID: CBTC
  • Operator: DigitalAsset-UtilityOperator::12202679f2bbe57d8cba9ef3cee847ac8239df0877105ab1f01a77d47477fdce1204
  • Provider: cbtc-network::12201b1741b63e2494e4214cf0bedc3d5a224da53b3bf4d76dba468f8e97eb15508f
  • Registrar: cbtc-network::12201b1741b63e2494e4214cf0bedc3d5a224da53b3bf4d76dba468f8e97eb15508f

Registry URL: https://api.utilities.digitalasset-staging.com

  • ID: CBTC
  • Operator: auth0_007c6643538f2eadd3e573dd05b9::12205bcc106efa0eaa7f18dc491e5c6f5fb9b0cc68dc110ae66f4ed6467475d7c78e
  • Provider: cbtc-network::12205af3b949a04776fc48cdcc05a060f6bda2e470632935f375d1049a8546a3b262
  • Registrar: cbtc-network::12205af3b949a04776fc48cdcc05a060f6bda2e470632935f375d1049a8546a3b262

Registry URL: https://api.utilities.digitalasset.com

Open the BitSafe faucet.

The faucet supports BitSafe assets on DevNet and TestNet. The link opens with DevNet and CBTC selected.

  1. Select the intended network.
  2. Select CBTC.
  3. Enter the recipient’s Canton party ID.
  4. Request test tokens.
  5. Accept the faucet transfer as the recipient.
  6. Check the recipient’s CBTC balance.

The recipient node must have the DA Utility Registry installed. Faucet tokens are not MainNet assets.

Test sending and receiving with the Transfer and receive CBTC guide. Support both pending offers and completed transfers. A completed transfer does not require acceptance.

DEXs and protocols use the same CBTC instrument ID and administrator listed above. The additional work depends on the application’s workflow.

Integration Additional work
Wallet Display balances and support sending and receiving tokens.
DEX or trading venue Connect asset transfers to the venue’s trade-settlement workflow.
Lending or other protocol Define how the application manages deposits, positions, and withdrawals.

For a trade that exchanges two assets, an ordinary transfer does not link the two legs. Canton Token Standard allocations support delivery-versus-payment settlement: both legs settle together or neither does. Confirm supported APIs and the required settlement permissions before using this workflow.

For lending, confirm the price source and collateral, borrowing, and liquidation rules before enabling the asset. Token support alone does not configure those rules.

See the Canton Token Standard documentation for allocation and application integration details.

CBTC-specific allocation examples are available in the existing integration reference.

Use approved asset artwork from the BitSafe brand kit. Contact BitSafe if the required artwork is unavailable.

For additional party fields or configuration questions, contact BitSafe.

Integrating one of our assets? Reach out to the team on Slack or to sales@bitsafe.finance to coordinate go-lives, marketing, and liquidity.