Canton

Network specific features and requirements for Canton wallets.

1. Set up a Canton validator

IBM Digital Asset Haven supports the Canton network, including self hosted validators. The Canton Network requires a dedicated activation. Reach out to IBM support to enable it. IBM Digital Asset Haven provides two ways to work with the Canton Network.
Option 1: Use the IBM Digital Asset Haven shared validator
This is the fastest way to begin broadcasting transactions with Canton wallets.
  • Using APIs:

    Create a new validator and select the IBM Digital Asset Haven kind (or Shared when using the API). For more information, see Canton validator

  • Using Dashboard:

    Open Settings > Developers > Canton validators > New Validator and select to create a validator. Sign the action with your passkey to complete setup.

Option 2: Connect your own validator (Bring Your Own Validator)

If you operate your own validator, you can connect it to IBM Digital Asset Haven using the API or the Dashboard. Once connected, you can create secure wallets that use your validator. No additional configuration is required on the validator itself.Validator rewards are always paid into the validator’s native wallet. For increased security, consider configuring an automated sweep into a separate IBM Digital Asset Havensecured Canton wallet. To connect your validator, gather the following details:

  1. Validator URL:

    IBM Digital Asset Haven must reach your validator’s External Signing API, for example: $URL/api/validator/v0/admin/external-party/topology/generate

  2. Validator OAuth2 authentication parameters
    IBM Digital Asset Haven uses these values to authenticate to your validator. They should match your existing validator authentication configuration.Required parameters:
    • Domain: Your OAuth2 tenant domain
    • Token path: Token endpoint on your provider
    • Audience: Suggested value is https://canton.network.global
    • Client ID
    • Client Secret
  3. Ledger API URL

    IBM Digital Asset Haven requires access to the Ledger JSON API.

  4. Ledger OAuth2 authentication parameters

    These typically match the validator OAuth2 configuration.Once all information is collected, you can begin connecting the custom validator in IBM Digital Asset Haven. For more information, see Canton validator

Set up a Canton wallet

Create a Canton wallet

Create a Canton wallet from the Dashboard or using the Create Wallet endpoint: Create Wallet . The wallet initially contains a key but is not registered to a validator. Its address does not yet have a prefix and cannot be used for transactions.

Activate the wallet on a validator
Activate the wallet using the Activate Wallet endpoint and specify a validatorId.
  • Using API
    POST /wallets/{walletId}/activate
    {
      "validatorId": "cv-xxxxx-xxxxx-xxxxxxxxxxxxxx"
    }
  • Dashboard:

    After creating a Canton wallet, the dashboard prompts you to select a validator and activate it. Once activated, the wallet receives its full address prefix and can send and receive transactions.

Pre approve receiving assets

Canton supports two methods of transferring funds. Transfers can be performed through an offer that requires explicit acceptance or through automated transfers. IBM Digital Asset Haven does not yet support responding to transfer offers. This feature is coming soon.You must pre approve receiving Canton Coins so the wallet automatically accepts incoming transfers. Offers sent before approval automatically expire after 24 hours.Open your Canton wallet in the dashboard and select Approve Assets. Approve the assets you want the wallet to accept automatically.

Transfers

Use the Transfer Asset endpoint for Canton transfers.
  • Native Canton Coin: Use kind: Native
  • CIP 56 tokens: Use kind: Cip56 with offer: true
CIP 56 tokens and transfer offers

CIP 56 tokens require a transfer offer workflow. Direct transfers are not supported.The only exception is sending CIP 56 tokens to your own wallet. No offer is required.The recipient must accept the offer from the Dashboard or by using the Accept Offer endpoint.

Managing offers
Endpoint Description
list-offers List pending offers
get-offer Get offer details
accept-offer Accept an offer
reject-offer Reject an offer
Expired offers

Transfer offers expire after 24 hours by default. Expired offers do not automatically fail. Funds remain locked until the sender withdraws the offer or the recipient rejects it.