This feature has been introduced with version
0.13 of the Registry App.An instrument for which the blocklist check is enabled is not compatible with Daml models introduced in previous releases.Instantiate the blocklist
A blocklist is managed at the instrument admin (i.e. registrar) level, and applies to all instruments managed by that party for which the blocklist check is enabled.Enable blocklist verification
You can enable blocklist verification on any instrument by modifying the correspondingInstrumentConfiguration contract and setting the checkBlocklist template field to Some True.
Please make sure an empty blocklist is instantiated before enabling the blocklist check on an instrument, otherwise all transfers, mints, and burns will fail.
Also note that enabling the blocklist check on an instrument makes it incompatible with Daml models introduced before release 0.13.
Manage the blocklist
The blocklist is available for parties that have a registrar service. Click on Blocklist in the left navigation sidebar to view the blocklist. If no blocklist has been created click on Create blocklist. Parties can be added and removed from the blocklist.Cost considerations
Using the blocklist feature requires additional contracts to be disclosed as part of theChoiceContext for transfer, minting, and burning transactions.
The blocklist is sharded across different party prefixes, so that the cost of these transactions is bounded, rather than linearly increasing with the number of parties in the blocklist.