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: