Page 40 - Implementation of Secure Authentication Technologies for Digital Financial Services
P. 40

6.7.7   DID Resolution
            The DID specification requires each DLT to have a DID   DID as input and resolve it to a DID Document. The
            Method specification to describe how DID operations   universal resolvers are specifically designed to work
            are performed. The implication of having many DID   for decentralized identifiers and support DID resolu-
            Method specifications is that resolving a text string,   tion over many different types of DLT and networks
            the DID, to locate the trust root and the associated   [15].  The universal resolver approach solves the
            DID Document is complex. The DID resolution func-  problem of heterogeneous networks having different
            tion could become a major impediment to interoper-  method specifications for their own DID. Figure 25
            able DIDs. Work has begun on a universal DID resolv-  depicts the Universal Resolver concept [15].
            er architecture and toolset that can take any valid

            Figure 25 – Universal DID Resolver



                                 Ledger 1        Ledger 2          Ledger N      Ledger N+1






                                  Driver         Driver             Driver         Http get
                                DID:ledger1    DID:ledger2        DID:ledgerN



                                                     Universal Resolver



                                  Http get        Http get




                                   App             App



































           38    Implementation of Secure Authentication Technologies for Digital Financial Services
   35   36   37   38   39   40   41   42   43   44   45