Documentation

Overview The Proof of Transfer service is a specialized core feature designed to verify the definitive outcome of asset transfers on the Canton Network for assets issued through the DA Registry. The service processes two specific cryptographic elements, an UpdateID and a structured Transfer Obj

Security Philosophy Our top priority is to systematically mitigate and reduce potential risks through a multi-layered security approach: • In-Depth External Audits • Collaborating with leading security researchers to identify potential vulnerabilities, logical edge-case errors, and structural in

These pages describe how to technically stand up and then use the xReserve solution in order to move USDC to and from the Canton Network. Conversely, a withdrawal (burn) request for a USDCx token on the Canton Network will result in the release of USDC on the destination L1 chain to the user’s spec

This page walks through the main xReserve user workflows. Onboarding One-time setup that authorizes a specific Party ID to use xReserve. Offboarding Reverse onboarding and deactivate the Party ID for future xReserve activity. Mint / Deposit Send USDC on an L1 chain and mint the equivalent a

cURL cURL curl --request POST \ --url http://localhost:8080/api/token-standard/v0/registrars/{registrarParty}/registry/allocations/v2/{allocationId}/choice-contexts/cancel \ --header 'Content-Type: application/json' \ --data ' { "meta": {}, "excludeDebugFields": false } ' im

cURL cURL curl --request POST \ --url http://localhost:8080/api/token-standard/v0/registrars/{registrarParty}/registry/allocations/v2/{allocationId}/choice-contexts/withdraw \ --header 'Content-Type: application/json' \ --data ' { "meta": {}, "excludeDebugFields": false } '

cURL cURL curl --request POST \ --url http://localhost:8080/api/token-standard/v0/registrars/{registrarParty}/registry/allocation/v2/settlement-factory \ --header 'Content-Type: application/json' \ --data ' { "choiceArguments": {}, "excludeDebugFields": false } ' import requ

cURL cURL curl --request POST \ --url http://localhost:8080/api/token-standard/v0/registrars/{registrarParty}/registry/allocation-instruction/v2/allocation-factory \ --header 'Content-Type: application/json' \ --data ' { "choiceArguments": {}, "excludeDebugFields": false } '

cURL cURL curl --request POST \ --url http://localhost:8080/api/token-standard/v0/registrars/{registrarParty}/registry/transfer-instruction/v2/{transferInstructionId}/choice-contexts/withdraw \ --header 'Content-Type: application/json' \ --data ' { "meta": {}, "excludeDebugFields": f

cURL cURL curl --request POST \ --url http://localhost:8080/api/token-standard/v0/registrars/{registrarParty}/registry/transfer-instruction/v2/{transferInstructionId}/choice-contexts/reject \ --header 'Content-Type: application/json' \ --data ' { "meta": {}, "excludeDebugFields": fal

cURL cURL curl --request POST \ --url http://localhost:8080/api/token-standard/v0/registrars/{registrarParty}/registry/transfer-instruction/v2/{transferInstructionId}/choice-contexts/accept \ --header 'Content-Type: application/json' \ --data ' { "meta": {}, "excludeDebugFields": fal

cURL cURL curl --request POST \ --url http://localhost:8080/api/token-standard/v0/registrars/{registrarParty}/registry/transfer-instruction/v2/transfer-factory \ --header 'Content-Type: application/json' \ --data ' { "choiceArguments": {}, "excludeDebugFields": false } ' imp

Overview The Covalidation Service (CVS) is a managed infrastructure solution for the Canton Network that eliminates single points of failure for wallets and applications. By multi-hosting parties and distributing validation responsibilities across a redundant, high-availability network, CVS helps

Configure a Featured Party Under CIP-104 , app rewards are attributed to featured parties based on the network traffic generated by application workflows. For Registry transactions, such as mints, transfers, burns, and other asset lifecycle operations, rewards are earned by the featured party ass

Registry App versions are numbered using an X.Y format. X represents the major version, and Y represents the minor version. Each minor release adopts a new set of Daml models. These are compatible upgrades of the models released in the previous minor release. The major version is incremented

Welcome to the DA Registry FAQ. If you cannot find the answer you are looking for here, please reach out to your Digital Asset support representative . General & Platform Who can use the DA Registry? The DA Registry is designed for organizations that want to operate a tokenization platform. Th

The DA Registry Asset Recovery is a service and operational feature offered to Asset Issuers and their Holders . It allows for the secure “recovery” of asset holdings from a lost or inactive node to a new node for the same partyID. This service ensures that DA Registry instruments remain accessibl

Whether you want to explore our enterprise solutions or require technical assistance with an active deployment, the Digital Asset team is here to help guide you. General & Sales Inquiries Connect with a specialist to explore our products, services, or to receive a comprehensive overview of the Ca

Before an asset can be minted, the Registrar must create an Instrument Configuration. The Instrument Configuration defines the asset and the rules that apply to it. Purpose The Instrument Configuration defines: • The instrument identifier. • Optional external identifiers, such as ISIN or CUSI

The Registry App uses credential-based allowlists to control which parties are permitted to perform specific actions for an asset. This enables issuers to enforce KYC, AML, regulatory, or business-specific requirements while keeping the rules fully configurable for each instrument. Common use case

The DA Registry is built around a clear separation of concerns, dividing infrastructure management from asset lifecycle management, and asset definitions from individual ownership records. Role Architecture The platform utilizes two primary administrative roles to ensure infrastructure sharing w

The DA Registry is the institutional-grade platform designed specifically for asset issuers and tokenization platforms building on Canton. It provides the foundational operational infrastructure required to bring assets on-chain while rigorously maintaining the governance, control, and privacy bench

As digital assets integrate deeper into global financial systems, relying solely on manual operational processes is no longer sufficient. Modern regulatory frameworks expect compliance controls to be technically enforceable and protocol-native rather than operational afterthoughts. The Registry App

Many digital assets require issuers to stringently control who can participate throughout the asset lifecycle. Whether onboarding investors to a tokenized fund, restricting ownership of regulated securities, or authorizing specific counterparties to mint and redeem stablecoins, issuers need adaptive

cURL cURL curl --request POST \ --url https://api.utilities.digitalasset.com/api/utilities/v0/registry/transfer/v0/proof \ --header 'Content-Type: application/json' \ --data ' { "updateId": "<string>", "transfer": { "sender": "<string>", "receiver": "<string>", "amount":

cURL cURL curl --request POST \ --url https://api.utilities.digitalasset.com/api/utilities/v0/registry/burn-mint-instruction/v0/burn-mint-factory \ --header 'Content-Type: application/json' \ --data ' { "instrumentId": { "admin": "<string>", "id": "<string>" }, "inputHoldin

cURL cURL curl --request POST \ --url https://api.utilities.digitalasset.com/api/utilities/v0/registry/burn/v0/request/{burnRequestId}/choice-contexts/cancel import requests url = "https://api.utilities.digitalasset.com/api/utilities/v0/registry/burn/v0/request/{burnRequestId}/choi

cURL cURL curl --request POST \ --url https://api.utilities.digitalasset.com/api/utilities/v0/registry/burn/v0/request/{burnRequestId}/choice-contexts/reject import requests url = "https://api.utilities.digitalasset.com/api/utilities/v0/registry/burn/v0/request/{burnRequestId}/choi

cURL cURL curl --request POST \ --url https://api.utilities.digitalasset.com/api/utilities/v0/registry/burn/v0/request/{burnRequestId}/choice-contexts/accept import requests url = "https://api.utilities.digitalasset.com/api/utilities/v0/registry/burn/v0/request/{burnRequestId}/choi

cURL cURL curl --request POST \ --url https://api.utilities.digitalasset.com/api/utilities/v0/registry/burn/v0/offer/{burnOfferId}/choice-contexts/cancel import requests url = "https://api.utilities.digitalasset.com/api/utilities/v0/registry/burn/v0/offer/{burnOfferId}/choice-conte