Daml
Role Architecture & Asset Model
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.
This role separation allows issuers, custodians, and tokenization platforms to operate dedicated registrar parties while securely leveraging a shared provider infrastructure. A single provider can support multiple registrars, and each registrar can administer one or more instruments.
Role Architecture
The platform utilizes two primary administrative roles to ensure infrastructure sharing while maintaining strict organizational boundaries.Provider
Operates the underlying DA Registry infrastructure. Providers are responsible for onboarding participants to the application and managing infrastructure-level access to DA Registry services.
Registrar
Creates and administers instruments on the DA Registry. Registrars handle the core asset lifecycle, including minting, burning, transfer controls, allowlists, and blocklists.
In token-standard terminology, the registrar acts as the definitive token administrator for a specific instrument.
Infrastructure Hierarchy
Asset Model
The DA Registry implements the asset model defined in the CIP-56 Canton Network Token Standard. This model splits the concept of an asset into two distinct layers: This structural separation allows a single instrument definition to be globally referenced across multiple unique holdings, keeping asset administration, compliance controls, and actual ownership records independent.Instrument to Holding Relationship
Was this page helpful?
YesNo
⌘I
