System and method for implementing a resolver service for decentralized identifiers
Methods, systems, and apparatus, including computer programs encoded on computer storage media, for implementing a resolver service. One of the methods includes: obtaining, from a blockchain, event data for a plurality of blockchain transactions associated with a plurality of decentralized identifiers (DIDs); storing the event data in a database; receiving a request for information associated with the event data, wherein the request comprises one or more account identifiers; identifying one or more DIDs respectively corresponding to the one or more account identifiers based on pre-stored mapping relationships between the one or more DIDs and the one or more account identifiers; and providing, from the database, event data for one or more blockchain transactions associated with the identified one or more DIDs.
1. A computer-implemented method for implementing a resolver service, comprising:
obtaining, from a blockchain, event data of a plurality of blockchain transactions associated with a plurality of decentralized identifiers (DIDs);
storing the event data in a database;
receiving a request for information associated with the event data, wherein the request comprises one or more account identifiers;
identifying one or more DIDs respectively corresponding to the one or more account identifiers based on pre-stored mapping relationships between the one or more DIDs and the one or more account identifiers; and
providing, from the database, event data of one or more blockchain transactions associated with the identified one or more DIDs.
2. The method of claim 1 , wherein the one or more blockchain transactions associated with the identified one or more DIDs comprise one or more blockchain transactions that update one or more DID documents respectively corresponding to the one or more DIDs.
3. The method of claim 1 , wherein the plurality of blockchain transactions associated with the plurality of DIDs comprise one or more blockchain transactions that update one or more verifiable claims (VCs) associated with one or more of the DIDs.
4. The method of claim 1 , wherein the obtaining event data comprises periodically accessing an up-to-date version of the blockchain.
5. The method of claim 1 , wherein the obtaining event data comprises:
obtaining a current height of the blockchain;
comparing the obtained current height of the blockchain with a maximum height in the blockchain that data currently stored in the database corresponds to; and
obtaining a plurality of blocks from the blockchain, wherein each of the obtained blocks corresponds to a height in the blockchain greater than the maximum height.
6. The method of claim 5 , wherein the obtaining event data further comprises:
searching, in the obtained blocks, for one or more blockchain transactions involving one or more blockchain contracts associated with DIDs or VCs; and
collecting one or more inputs and outputs associated with the one or more blockchain contracts.
7. The method of claim 1 , wherein:
the providing event data of one or more blockchain transactions associated with the identified one or more DIDs comprises sending the event data of the one or more blockchain transactions to an online agent configured to manage DIDs or VCs for a plurality of users.
8. A non-transitory computer-readable storage medium for implementing a resolver service, configured with instructions executable by one or more processors to cause the one or more processors to perform operations comprising:
obtaining, from a blockchain, event data of a plurality of blockchain transactions associated with a plurality of decentralized identifiers (DIDs);
storing the event data in a database;
receiving a request for information associated with the event data, wherein the request comprises one or more account identifiers;
identifying one or more DIDs respectively corresponding to the one or more account identifiers based on pre-stored mapping relationships between the one or more DIDs and the one or more account identifiers; and
providing, from the database, event data of one or more blockchain transactions associated with the identified one or more DIDs.
9. The non-transitory computer-readable storage medium of claim 8 , wherein the one or more blockchain transactions associated with the identified one or more DIDs comprise one or more blockchain transactions that update one or more DID documents respectively corresponding to the one or more DIDs.
10. The non-transitory computer-readable storage medium of claim 8 , wherein the plurality of blockchain transactions associated with the plurality of DIDs comprise one or more blockchain transactions for updating one or more verifiable claims (VCs) associated with one or more of the DIDs.
11. The non-transitory computer-readable storage medium of claim 8 , wherein the obtaining event data comprises periodically accessing an up-to-date version of the blockchain.
12. The non-transitory computer-readable storage medium of claim 8 , wherein the obtaining event data comprises:
obtaining a current height of the blockchain;
comparing the obtained current height of the blockchain with a maximum height in the blockchain that data currently stored in the database corresponds to; and
obtaining a plurality of blocks from the blockchain, wherein each of the obtained blocks corresponds to a height in the blockchain greater than the maximum height.
13. The non-transitory computer-readable storage medium of claim 12 , wherein the obtaining event data further comprises:
searching, in the obtained blocks, for one or more blockchain transactions involving one or more blockchain contracts associated with DIDs or VCs; and
collecting one or more inputs and outputs associated with the one or more blockchain contracts.
14. The non-transitory computer-readable storage medium of claim 8 , wherein:
the providing event data of one or more blockchain transactions associated with the identified one or more DIDs comprises sending the event data of the one or more blockchain transactions to an online agent configured to manage DIDs or VCs for a plurality of users.
15. A system for implementing a resolver service, comprising a processor and a non-transitory computer-readable storage medium storing instructions executable by the processor to cause the system to perform operations comprising:
obtaining, from a blockchain, event data of a plurality of blockchain transactions associated with a plurality of decentralized identifiers (DIDs);
storing the event data in a database;
receiving a request for information associated with the event data, wherein the request comprises one or more account identifiers;
identifying one or more DIDs respectively corresponding to the one or more account identifiers based on pre-stored mapping relationships between the one or more DIDs and the one or more account identifiers; and
providing, from the database, event data of one or more blockchain transactions associated with the identified one or more DIDs.
16. The system of claim 15 , wherein the one or more blockchain transactions associated with the identified one or more DIDs comprise one or more blockchain transactions that update one or more DID documents respectively corresponding to the one or more DIDs.
17. The system of claim 15 , wherein the plurality of blockchain transactions associated with the plurality of DIDs comprise one or more blockchain transactions for updating one or more verifiable claims (VCs) associated with one or more of the DIDs.
18. The system of claim 15 , wherein the obtaining event data comprises periodically accessing an up-to-date version of the blockchain.
19. The system of claim 15 , wherein the obtaining event data comprises:
obtaining a current height of the blockchain;
comparing the obtained current height of the blockchain with a maximum height in the blockchain that data currently stored in the database corresponds to; and
obtaining a plurality of blocks from the blockchain, wherein each of the obtained blocks corresponds to a height in the blockchain greater than the maximum height.
20. The system of claim 19 , wherein the obtaining event data further comprises:
searching, in the obtained blocks, for one or more blockchain transactions involving one or more blockchain contracts associated with DIDs or VCs; and
collecting one or more inputs and outputs associated with the one or more blockchain contracts.