DA Registry App v0.14 is live! This release introduces support for Canton Token Standard V2 (CIP-112), enabling Registry-issued assets to participate in the latest token standard workflows on Canton.
Token Standard V2 (CIP-112) Registry-issued assets can now participate in Token Standard V2 workflows, unlocking new capabilities for trading, settlement, custody, and application integrations: • Privacy-enhanced batch settlement: participants only see the settlement legs relevant to them, enabling complex multi-party transactions while preserving privacy. • Improved allocation and settlement flows: better support for off-chain execution venues and multi-party settlement workflows. • Delivery-vs-Mint and Delivery-vs-Burn: minting and burning can be incorporated into standardized settlement flows, enabling atomic settlement against asset issuance or redemption. • Accountable Holdings: enable holdings to be associated with accounts. The DA Registry App implementation currently supports "provider-less accounts" with custom IDs. • Committed Allocations for Prefunded Trading and Iterated Settlement: assets can be committed to an application before the exact transfer legs are known, supporting use cases such as trading, lending, and staking. • Standardized transaction history: the new `EventLog` interface provides a common way to determine holding and balance changes across Token Standard workflows. Integration Changes With this release, `ExecutedTransfer`, `ExecutedMint`, and `ExecutedBurn` contracts are no longer created. If your integration relies on these contracts to parse transaction history, you must update your integration before upgrading. The Transaction History Parsing Guide describes the supported parsing approaches and provides a migration path. `0.12` and `0.13` are still supported and allow you to use these contracts.
Deprecation and Supported Versions This version removes support for the `0.11` release line. All users must be running the Daml models shipped with the `0.12` release line at a minimum.
Rollout Timeline
Today — August 21st • v0.14 release cut • New versions available for upload • DA operator nodes upgraded on DevNet and TestNet • Deploy the new version to your DevNet and TestNet environments — you can begin testing v0.14 and CIP-112 workflows • Minimum DAR version: v0.11 DARs will be unvetted on the operator nodes. All users must be running v0.12 or later. Thursday — August 27th • DA operator node upgrade on MainNet • Deploy the new version to your MainNet • Minimum DAR version: v0.11 DARs will be unvetted on the operator node. All users must be running v0.12 or later.
