> ## Documentation Index
> Fetch the complete documentation index at: https://docs.digitalasset.com/llms.txt
> Use this file to discover all available pages before exploring further.

# 0.14

## DARs

This release introduces the following DAR versions:

| Package                     | Version | Package Id                                                       |
| :-------------------------- | :------ | :--------------------------------------------------------------- |
| utility-registry-app-v0     | 0.9.0   | 86fc0823b42911edc70c054466a38e8ad85ab3d90674ef2cba3030485afdfb20 |
| utility-registry-v0         | 0.8.0   | f838b87dbcc296667d72fbb3759435be420eb4a3405a6e4c0a7bd9dfc7eb299c |
| utility-registry-holding-v0 | 0.3.0   | dd7d236452498ff9a8bb1aa9ae0c4e60a70ac9524bff7cdb1d6935feaa6b7243 |
| utility-credential-app-v0   | 0.4.3   | 87d6bfac3adf937cf5f603767f440a3b60416c2dfd9f82346455547972f5e236 |
| utility-credential-v0       | 0.1.2   | 044be226f82e81609111569fb7253421cdb86b2bf0ecab781f46a58003e69574 |

<CardGroup cols={2}>
  <Card title="Download 0.14 DAR Bundle" href="https://get.digitalasset.com/utility-dars/canton-network-utility-dars-0.14.1.tar.gz">
    DAR bundle archive (.tar.gz)
  </Card>

  <Card title="Download SHA-256 Checksum" href="https://get.digitalasset.com/utility-dars/canton-network-utility-dars-0.14.1.tar.gz.sha256">
    Checksum file
  </Card>
</CardGroup>

<Note>
  These DARs are compiled using Daml LF 2.3.

  If you are running PQS, please ensure you are at least on version `3.5.5` before uploading these DARs to your validator node.
  Previous versions of PQS are not compatible with Daml LF 2.3.
</Note>

## Features

### Support for Token Standard v2 ([CIP-112](https://github.com/canton-foundation/cips/blob/main/cip-0112/cip-0112.md))

The Token Standard v2 workflows are now supported in the Registry App.

Moreover, non-v2 workflows have been enhanced to emit events through the CIP-112 `EventLog`
interface.

### Support for account id selection on CIP-56 transfers.

Asset holders can specify a textual sender and receiver label (account id) when instructing a
transfer and creating an allocation. This identifier will be set on `Holding` contracts using the
textual `label` field.

### Removal of ExecutedTransfer, ExecutedMint, ExecutedBurn

`ExecutedTransfer`, `ExecutedMint`, and `ExecutedBurn` contracts are no longer created upon
execution of the corresponding workflows.

### Other Changes

A choice has been added to the `InstrumentConfiguration` to let the operator archive duplicate
contracts.

The `Holding_Transfer` choice on the `Holding` template has been disabled.

Self-allocations (where sender equals receiver) for CIP-56 can be created again, after being
disabled in `0.13`.

## 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.

## Integration Guide and Backwards Compatibility

### Tokenizers

Before consuming this release, tokenizers must ensure that they do not rely solely on
`ExecutedTransfer`, `ExecutedMint`, `ExecutedBurn` contracts for transaction history parsing.

If you currently rely on such contracts, the [Transaction History Parsing Guide](/registry/guides/tx-history-parsing)
describes the different parsing guidelines and illustrates a migration path.

### Third-Party Applications

This release is backwards-compatible.

Third-party applications that wish to use CIP-112 workflows must make sure that the target
instrument admin supports CIP-112. See [Support of Token Standard V2 (CIP-112) for a given
instrument admin](/registry/apis/token-standard#support-cip-112-instrument-admin) for details.

### Wallet providers

This release is backwards-compatible.

Wallet providers that wish to use CIP-112 workflows must make sure that the target
instrument admin supports CIP-112. See [Support of Token Standard V2 (CIP-112) for a given
instrument admin](/registry/apis/token-standard#support-cip-112-instrument-admin) for details.