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

## DARS

This release introduces the following DAR versions

| Package                     | Version | Package Id                                                       |
| :-------------------------- | :------ | :--------------------------------------------------------------- |
| utility-registry-app-v0     | 0.8.2   | 2293eb12e82ceaeb3ff7f8fe3346dece8578e1e9fd7d46624aeb7bb07fa31eda |
| utility-registry-v0         | 0.7.1   | 1f80e086e9ce218cf93fdeed80943793e902ac35c521733d7373a5ba58813150 |
| utility-registry-holding-v0 | 0.2.2   | 71fbaea211f07a65666892748498bd4a0d7462a9d75bbb215ba9fbdbba78efa7 |
| utility-credential-app-v0   | 0.4.2   | 3f0341b825b1e2cc94b3b216303e5497f0adf2bae0f1dc6e16e19d7aa955a6d6 |
| utility-credential-v0       | 0.1.1   | 418370044b5c6cd76ec78b73b8553c592328dec0afb6defbd2fdc5909e024033 |

<CardGroup cols={2}>
  <Card title="Download 0.13 DAR Bundle" href="https://get.digitalasset.com/utility-dars/canton-network-utility-dars-0.13.0.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.13.0.tar.gz.sha256">
    Checksum file
  </Card>
</CardGroup>

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

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

## Features

### Blocklist

A party with the `Registrar` role can now define a blocklist of parties that are not allowed to transfer / mint / burn instruments for which the blocklist check is enabled.

The `InstrumentConfiguration` contract has been extended with a `checkBlocklist` field, which can be set to `True` to enable the blocklist check for that instrument.

More details can be found in the [Blocklist Guide](/registry/guides/blocklist).

### UI changes

Transfer history display in the UI no longer relies on `ExecutedTransfer` contracts, but reads the ledger's transaction trees directly.

Paginated query endpoints introduced in Canton 3.5 are used in order to improve the responsiveness of the UI.

The Collateral tile is no longer shown, as the app has been decommissioned following a series of successful pilot trades.

The UI no longer displays the user's Canton Coin balance, as this can be retrieved from dedicated wallets.

The UI no longer offers the ability to create paid credentials.

### Disclosure endpoints for Mint / Burn workflows

An optional `extraArgs` argument has been added to the `BurnRequest_Cancel`, `MintRequest_Cancel`, `BurnOffer_Cancel`, and `MintOffer_Cancel` choices.

Corresponding operator backend endpoints serve the execution context for these choices. This is currently always empty, but will be used in future releases
to allow for more flexible mint / burn workflows.

### Batch archival of `Executed*` Contracts

A choice was added to the `RegistrarService` to allow for more cost-efficient batched archival of executed mint/burn contracts.

### Changes to the `DvpLegAllocation` ensure clause

The `DvpLegAllocation` ensure clause was strengthened to enforce `sender /= receiver` and `amount > 0.0`. These conditions were already validated at execution time, but checking them in the ensure clause surfaces failures earlier.

The temporal ordering check was also relaxed from `requestedAt < allocateBefore < settleBefore` to `requestedAt <= allocateBefore <= settleBefore`.

### Other Changes

Splice dependencies were upgraded to `splice-amulet-0.1.20`.

Daml models are now compiled using LF 2.3.

## Deprecation and Supported Versions

This version removes support for the `0.10` release line. All users must be
running the Daml models shipped with the `0.11` release line at a minimum.

## Integration Guide and Backwards Compatibility

### Tokenizers

Tokenizers that integrate with the Burn / Mint workflows over their API should adapt their integration to

* source the execution context for the `BurnRequest_Cancel`, `MintRequest_Cancel`, `BurnOffer_Cancel`, and `MintOffer_Cancel` choices
  from the corresponding backend endpoints
* populate the new `extraArgs` field with the result from the previous step

In order to ensure backwards compatibility with users running earlier Daml models, we recommend setting `extraArgs` to `None` if an empty choice context is returned.

### Third-Party Applications

The execution context for transfers and allocations might include the blocklist, should the instrument admin
enable the blocklist check for the instrument. No action is required by third-party applications, unless custom logic
is used to produce the execution context.

### Wallet Providers

The execution context for transfers and allocations might include the blocklist, should the instrument admin
enable the blocklist check for the instrument. No action is required by wallet providers, unless custom logic
is used to produce the execution context.