Skip to main content
This section aims to outline the supported integration modes for apps that wish to compose with the Registry App directly on the Daml level.

​
General guidance

We recommend that your Daml code only depends on Daml interface packages, rather than packages depending on concrete template implementations. This will ensure that the release cadence for your application is decoupled from the release cadence of the Registry App. Dependencies on concrete template implementations can be used only for code that runs as a one-off during app initialization.

​
CIP 56 for transfers and DvPs

The Registry App is fully Token Standard (CIP-56) compliant. You can use the Daml interfaces defined as part of CIP-56 in order to execute transfers and allocations from your Daml code. More details can be found in the Token Standard API section.

​
Custom mint / burn workflows

We offer an integration point for tokenizers that wish to implement custom mint and burn workflows using Daml.