Documentation

In connection with the use of Circle’s xReserve Smart Contract, Digital Asset provides discretionary support to users with issues arising from certain Canton-related software components. Digital Asset does not provide support with respect to Circle’s xReserve Smart Contract or your use of USDCx on t

Investor1 offers token transfer to Investor2 Investor1 (as the holder of BOND) offers transfer of BOND to Investor2 (another holder of BOND). Actor | Utility Module | Investor1 | REGISTRY | Select HOLDINGS on the left navigation. The 10,000 BOND is there. Click TRANSFER. Input investor2’s pa

Token Details (MainNet) On Canton Network, the uniqueness of the token is the combination of the token’s Instrument Id and the party ID of the token’s admin (registrar). Below are these details for USDCx. Only the USDCx that contains these details is the official USDCx on the Canton Network. I

Applications (such as wallet providers and exchanges) can integrate and interact with the xReserve solution and/or USDCx via API. There are three options for supporting USDCx on the Canton Network: • Transfer & hold USDCx - Since USDCx is a token standard CIP-56 compliant asset, any wallet that sup

Preparing credentials for token transfer. Registrar offers credential of token holder to Investor2 Registrar (of BOND) offers a free credential to Investor2 (as a holder of BOND). Actor | Utility Module | Registrar | CREDENTIAL | Investor2 accepts credential offer Investor2 accepts the c

Issuer requests token issuance (minting) Issuer (as the issuer of BOND) requests issuance (minting) of 10,000 BOND. Actor | Utility Module | Issuer | REGISTRY | Registrar accepts and tokens are issued Registrar (as the registrar of BOND) accepts the mint request. Actor | Utility Module |

Credential Preparation for Token Issuance and Transfer Registrar specifying the requirement of the BOND token Here Registrar of BOND specifies the credential requirement, i.e. what credentials are needed in order to issue or hold the BOND tokens. Actor | Utility Module | Registrar | REGISTRY

This tutorial details the steps to redeem a tokenized instrument using the Credential and Registry utilities. Instrument The tokenized instrument redeemed is called BOND. Roles Roles in Tokenization Utility | Entity | Roles in Asset BOND | Provider (onboarded by DA) | Provider | Registra

0.3.0 UI • Sources the required disclosed contracts from the utility backend’s new API endpoint burn-mint-instruction/v0/burn-mint-factory. • The UI now requires the URL of the utility backend to be provided as an environment variable. This is included in the Helm chart and compose file config

This tutorial details the steps to transfer a tokenized instrument from Investor1 to Investor2 using the Credential and Registry utilities. Instrument The tokenized instrument transferred is called BOND. Roles Assumptions: • Investor1 is already onboarded. • Investor2 is not yet onboarde

As digital assets move through complex operational and regulatory lifecycles, issuers occasionally need the ability to immediately halt activity on an instrument—whether to respond to a security incident, a regulatory hold, or an internal operational review. Relying on off-chain coordination to stop

The end goal is to be able to sign into the DA Registry dApp UI using an external wallet such as Console and Send. Connect the DA Registry dApp UI to your validator using the wallet gateway. • Follow the instructions here • You will need to deploy a wallet-gateway instance and have the wallet-ga

1. Configure your Validator Node Ensure you are running the same splice version on your node as is run on the primary validator and other covalidating node(s), keeping up to date with the Canton Foundation schedule . Create / configure the validator node which you will use as your covalidating n

Troubleshooting FAQ Troubleshooting FAQ Operational Runbook Operational Runbook Troubleshooting FAQ Unable to authenticate with GitHub Verify: • GitHub App ID • Installation ID • Private key Secret • The application has been installed into the correct repository DARs are not synchron

This feature was introduced with version 0.13.1 of the Registry App; version 0.7.1 of the utility-registry-v0 (the block list check field), extended with sharding and UI support in version 0.14.0 of the Registry App; version 0.8.0 of utility-registry-v0. An instrument for which the blocklist

This page explains how to inspect the ledger to parse transaction history for a given party, in order to identify executed mints, burns, and transfers. CIP-112 transaction parsing guidelines CIP-112 introduces a dedicated Daml EventLog interface to record transaction events. This interface exp

For DA Registry components such as the Explicit Disclosure Backend, dApp UI or the Reward Automation we provide the 24/7 Status via a dedicated status page , embedded below. Please be aware that the DA Apps team performs weekly maintenance every Thursday from 09:00–10:00 ET / 15:00–16:0

Monitoring The Covalidation Service contains metrics/traces out of the box to support monitoring. This behavior is enabled by adding the following block to your configuration: monitoring: otel: endpointURL: <OTEL Monitoring URL> The endpointURL field is an OpenTelemetry (O

Integrating Proof of Transfer capability into a Canton Network Explorer gives users a seamless interface to verify transaction statuses natively, while preserving privacy. • Canton Network Explorer • Canton Network Wallet Integration Blueprint To provide a seamless customer journey, the Explor

USDCx Canton side infrastructure supports USDCx deposit/mint and withdrawal/burn on Canton, and we provide the 24/7 Status via a dedicated status page , embedded below. Please be aware that the DA Apps team performs weekly maintenance every Thursday from 09:00–10:00 ET / 15:00–16:00 Central E

This page provides indicative traffic cost estimates for all DA Registry actions, including the Token Standard v1 and v2 workflows. The USD amounts are costs due to traffic and exclude any reward offsets. Use the estimates to compare the relative traffic generated by each action and workflow variant

Onboarding (Primary Validator) The onboarding process consists of the following high-level steps. 1. Choose a Third Node Operator • Select a third-party node operator that will host parties on an additional covalidating node. 2. Configure the DAR Repository • Create and configure access to a

The Daml models for the Registry App are shipped as a bundle of DAR files. Supported versions We currently support the Daml models shipped with the 0.12, 0.13, and 0.14 releases, and include the DARs for those releases in the latest available bundle. For maximum compatibility, we recommen

Prerequisites Commercial Agreement Use of the DA Registry requires a commercial agreement with Digital Asset. The agreement governs access to DA Registry, licensing, support, and any applicable commercial terms. For licensing and pricing information, please contact Digital Asset . Set Up Canto

Operator Party The DA operator party is used • as a signatory on onboarding contracts (i.e. ProviderService) • as an observer on all other Registry contracts (e.g. InstrumentConfiguration, TransferPreapproval, …) The latter is required for DA to be able to run the Registry Operator backe

The DA Registry Workflows provide a structured, permissioned framework for managing digital assets throughout their lifecycle. Operating on the Canton Network Token Standard, these workflows automate compliance checks and coordinate multi-party actions seamlessly. Capabilities Overview The DA Re

Security is a fundamental part of how we operate. We recognise that firms using our Registry application entrust us with sensitive information and technology supporting the issuance, management and transfer of tokenised assets. We therefore take a structured, risk-based approach to security across o

Overview The DA Registry is the fastest way for asset issuers and tokenizers to issue, mobilize and monetize institutional-grade digital assets on Canton. If you are not familiar yet with the DA Registry, we recommend briefly reading the PRIMER first. Quickstart Issue compliant, interope

Overview Digital Asset actively monitors the suite of services that support the functionality of the Registry application on Canton Network. We maintain a comprehensive observability strategy that facilitates our 24/7 Global Support Team to: • Detect : Identify infrastructure anomalies and perfor

Steps to set up reward sharing for your featured party Use the following steps for each featured Registry party (provider or registrar) you control. 1 Determine the Digital Asset Accounting Party Identify the Digital Asset accounting party that should receive the contractual reward share for