App / Wallet providers integration
App providers and Wallet providers wishing to transact Registry holdings as part of their application’s workflows must make sure that- all supported versions of the
utility-registry-app-v0DARs are installed on their node - the application is configured to source off-ledger data from the token standard endpoints
AllocationRequest standard to read allocation requests from other applications and create corresponding Allocations.
You can download the bundle containing the DAR files from the Releases page.
Instrument admin actions
Instrument admins who wish to enable token-standard transfers for the tokens they manage must ensure the following contracts have been created
Both contracts can be instantiated and archived using the dApp UI.
Support of Token Standard V2 (CIP-112) for a given instrument admin
While all supported versions of the Registry App implement the CIP-56 interfaces, support for CIP-112 has only been introduced starting with version 0.14 of the app. A given Registry instrument admin supports CIP-112 only if they have installed the 0.14 DARs. As an app or wallet provider, you can use the/registry/metadata/v1/info token metadata endpoint
in order to verify whether a given tokenizer supports the CIP-112 interfaces, or whether a fallback
to CIP-56 is needed.
Example response: CIP-112 supported
Example response: CIP-112 supported
Example response: CIP-112 not supported
Example response: CIP-112 not supported
If the instrument admin has not installed the 0.14 DARs, the response does not include the v2 interfaces:
Allocations across multiple admins
In V2, an allocation is scoped per account and admin: it covers the transfer leg sides of one account for the instruments of one admin (see CIP-112, 4.3.1). An allocation request whose legs involve instruments of several admins (for example, one instrument issued on the Registry App and another on an external registry) therefore requires one allocation per account and admin. Although these allocations could technically be created together, this is not supported out of the box:- The token standard has no built-in batch choice for this, so a generic wallet cannot support it.
- It would require combining choice contexts across different registry endpoints, and there is currently no global service to discover the off-ledger API endpoint of a third-party registry.
- Orchestrating allocations across registries is arguably the task of a trading app (or aggregator app).
Iterated settlement considerations
The Registry App supports iterated settlement throughAllocationV2. With iterated settlement, the executors specify
the transfer legs at settlement time, which gives them a lot of discretion. The safety of funds depends strongly on
the integrity of the executors. Only enable iterated settlement for executors you fully trust with the allocated
funds, lock only the funding amount strictly required, and review the
CIP-112 specification
beforehand.