Purpose of the Address Resolver Document
To use the DARP protocol in a supported application a user must register a DID Document that includes a service endpoint that DARP compliant applications (wallets, dApps, browsers, etc) can use to access an Address Resolver Document (ARD) which stores resolution information for a given Address Name. An example of how the Address Resolver Document may be structured is as follows:
While Decentralised Address Name Registrars will likely host users Address Resolver Documents as part of their service, the user is free to store it anywhere they want (e.g. IPFS, a Cardano SPO, a private server, Google Drive) as long as the endpoint registered in the DID Document is accessible.
Consideration is also being given from providing a mechanism to include multiple ARD endpoints in the DID Document. This will allow a user to store their ARD in distributed locations for redundancy purposes (i.e. if a hosting location becomes unavailable).
Last updated
Was this helpful?