Resolver
The Resolver page offers a simple interface resolve did:prism and did:indy based DIDs to their underlying DID-Documents. The page is available at https://analytics.blocktrust.io/resolver. In the background it quering the internal Analytics-Platform for the requested DID its metadata and references for prior versions.
The resolution result is presented in a graphical way, giving either Links or copy-paste buttons for certains values if available. Idenpentend data-sources which have not directly been consumed in the ingestion process for that DID are also linked:
For did:prism identifiers you can use the link in the top right of each document to directly get the underlying Cardano transaction, through which that specific DID has been created, updated or deactivated. The encoded operation can be found in the metadata-section of the linked Block-Explorer page. Details for interpreting the metadata can be found in the DID-PRISM specification. For did:prism networks a Resolver-API is currently also available within the OpenPrismNode
For did:indy identifiers the link in the top right references an independently hosted instance of IndyScan:
For Sovrin Networks: https://indyscan.io/
For IDunion Networks: https://idunion.esatus.com
For Indicio Networks: https://indyscan.indiciotech.io
For BC Gov Networks: http://test.bcovrin.vonx.io
For CANdy Networks: https://candyscan.idlab.org/
The Resolver page is also available by using query parameters to directly resolve a specific DID e.g.
https://statistics.blocktrust.dev/resolve?method=prism&network=preprod&identifier=64d59a62aa659b31da14cb3d63926d66a084859628b81838f709ea6f604a9204
Using the toggle-button in the graphical interface lets the user switch between the raw JSON representation of the DID-Document and the graphical representation.
Note that the results inside the Metadata and Did-Resolution-Metadata section might slightly very with other resolution-results from other providers, as they are not completely standardized. Depending on the underlying did-method and network each provider might add additional metadata to the DID-Document, depending on what is available based on the individual infrastructure setup.
The Blocktrust Resolution Metadata section is purely informational to determine when the ingestion / resolution of that specific DID-Document initially occurred and which internal version of the resolver was used. It is not directly part of the DID-Resolution specification. In case of further processing of the Resolution-Result, this section can be omitted.