0.14 of the Registry App. V1 wallets are unaware
of accounts, so they may select input holdings with different labels (account IDs). This page outlines the resulting
compatibility issue when the transaction runs on a Registry version before 0.14, and how V1 wallet providers can
avoid it.
This is an additional aspect to the compatibility rules
outlined in the CIP text.
Account selection
In CIP-112, transfers can be made from and to a specific holder account. The account identifier is represented as a textuallabel field on the Holding contract.
A holder can therefore have multiple Holding UTXOs with different labels for a given instrument, for example after
receiving holdings into different accounts. For instance:
If the holder now uses a V1 wallet to transfer 150 units, the input Holding UTXOs need to be selected carefully.
Registry versions before
0.14 expect input holdings to have consistent labels, failing with a Daml
interpretation error otherwise. The Registry version of the transaction is selected by
TAPS: if any
involved participant, e.g. the receiver, has only vetted an older version, the transaction runs on that version.
Recommended mitigation step
V1 wallet providers can circumvent this compatibility issue in two ways:Filter
Filter
Filter input Holding UTXOs to ensure the provided inputs have consistent labels.
Merge before transfer
Merge before transfer
Merge input Holding UTXOs to obtain an output Holding with a sufficiently large amount.