CN111095327B

CN111095327B - System and method for verifying verifiable claims

Info

Publication number: CN111095327B
Application number: CN201980004141.1A
Authority: CN
Inventors: 杨仁慧; 刘佳伟; 陈远; 林渝淇
Original assignee: Advanced New Technologies Co Ltd
Current assignee: Advanced New Technologies Co Ltd; Advantageous New Technologies Co Ltd
Priority date: 2019-07-02
Filing date: 2019-07-02
Publication date: 2023-11-17
Anticipated expiration: 2039-07-02
Also published as: EP3688633A2; SG11202003792QA; CN111095327A; TWI748387B; US11277268B2; US20200127845A1; US10938569B2; US20210144011A1; EP3688633A4; TW202103084A; WO2019179535A3; WO2019179535A2

Abstract

Methods, systems, and apparatus, including computer programs encoded on a computer storage medium, for validating a verifiable claim. One of the methods comprises: receiving a request from a first entity to verify a verifiable statement (VC) comprising a digital signature; obtaining a public key associated with a second entity based on the VC; determining that the digital signature was created based on a private key associated with the public key; the VC is authenticated based on the determination.

Description

System and method for verifying verifiable claims

Technical Field

The present application relates generally to methods and apparatus for managing decentralised identifications and verifiable assertions based on blockchain technology.

Background

Conventional identity management systems are based on a centralized authority, such as a corporate directory service, a certification authority, or a domain name registrar. Each centralization authority can act as a root of trust to provide trust for its endorsed identity. For such systems, the data associated with the identity is typically stored in a centralized database, if not in a conventional information storage medium. The identity maintenance of each person or entity is under the control of a centralised authority. In view of its nature, conventional identity management systems can take on security risks suffered by each centralized authority and provide an inefficient mechanism to collect identities or credentials provided by different centralized authorities. In such systems, individual entities or identity owners are often not free to choose the root of trust nor control their own identity or credentials. Authentication and verification of their identity has proven to be generally inefficient.

Blockchain technology provides the opportunity to build a trustworthy decentralized system that does not require trust of every member of the system. Blockchains provide data storage in a decentralized manner by storing data in a series of data blocks that have a precedence relationship to each other. The blockchain is maintained and updated by a network of blockchain nodes, which are also responsible for validating data based on a consensus scheme. The stored data may include a number of data types, such as financial transactions between parties, historical access information, and the like.

Many blockchains (e.g., ethernet blockchains) have been able to implement blockchain contracts (also referred to as smart contracts) that are executed by blockchain transactions. A blockchain transaction is a signed message that is initiated by an externally owned account (e.g., a blockchain account), transmitted by the blockchain network, and recorded in the blockchain. Blockchain contracts may be written to implement various functions, such as adding data to blockchain accounts, altering data in blockchains, and the like. Thus, the blockchain may be maintained and updated by performing blockchain transactions.

Blockchain technology provides a way to manage the root of trust without the need for a centralized authority. Identity management systems based on blockchain construction typically present substantial technical hurdles to the average user by requiring participation in the blockchain consensus scheme or the ability to store, create and execute blockchain transactions and contracts. The identity holder may be required to hold important identity credentials, e.g. encryption keys, which when destroyed may risk losing the identity. Furthermore, such identity management systems have proven to be generally inefficient and user-unfriendly for business entities that need to manage a large number of user identities. The mapping between identities managed by such identity management systems and accounts or service IDs maintained by business entities is often difficult to maintain. Finally, such identity management systems typically require frequent access to and interaction with the blockchain network, which can be expensive and resource consuming.

Disclosure of Invention

Various embodiments herein include, but are not limited to, systems, methods, and non-transitory computer-readable media for validating a claim.

According to some embodiments, a computer-implemented method for verifying a verifiable claim includes: receiving a request from a first entity to verify a verifiable statement (VC) comprising a digital signature; obtaining a public key associated with a second entity based on the VC; the digital signature is created based on a private key determination associated with the public key; the VC is authenticated based on the determination.

In some embodiments, obtaining the public key associated with the second entity comprises: the second entity is identified based on the identification in the VC.

In some embodiments, the identification is a de-centralized identification (DID) and the obtaining the public key associated with the second entity comprises: sending a blockchain transaction to a blockchain link of a blockchain that includes information associated with the DID, wherein the blockchain transaction is used to retrieve a DID document corresponding to the DID; obtaining the DID document from the blockchain; and retrieving a public key from the DID document. In some embodiments, the blockchain transaction invokes a blockchain contract for managing the relationship between the DID and the DID document.

In some embodiments, the method further comprises obtaining a state of the VC; and determining that the state of the VC is valid. In some embodiments, obtaining the state of the VC comprises: the state is obtained from a blockchain that stores information associated with a plurality of VCs.

In some embodiments, determining that the state of the VC is valid comprises: obtaining a first hash value associated with the VC and the state of the VC; determining a second hash value by applying a hash function to the VC; and authenticating the state of the VC by comparing the first hash value with the second hash value.

In some embodiments, obtaining a first hash value associated with the VC and the state of the VC comprises: a blockchain transaction is sent to a blockchain node of the blockchain for retrieving the first hash value and the state, the blockchain transaction including a DID associated with a principal of the VC.

In some embodiments, the method further comprises: retrieving, from the first entity, an account identification associated with a principal of the VC; obtaining a DID associated with the main body of the VC based on a pre-stored mapping relation between the account identifier and the DID to obtain a DID document associated with the DID; obtaining information associated with a service endpoint for managing VCs from the DID document; and obtaining the VC from the service endpoint.

In some embodiments, the method further comprises: and sending a message confirming that the VC is verified to the first entity.

In some embodiments, validating the VC comprises: obtaining the release date of the VC from the VC; and verifying the obtained release date based on a comparison between the obtained release date and a current date.

In some embodiments, validating the VC comprises: obtaining an expiration date of the VC from the VC; and verifying that the VC has not expired based on the expiration date and the current date.

According to other embodiments, a system for validating a claim includes one or more processors; and one or more computer-readable memories coupled to the one or more processors and having instructions stored thereon, the instructions being executable by the one or more processors to perform the method of any of the preceding embodiments.

According to other embodiments, a non-transitory computer-readable storage medium is configured with instructions executable by one or more processors to cause the one or more processors to perform the method of any of the preceding embodiments.

According to other embodiments, an apparatus for verifying a verifiable claim comprises a plurality of modules for performing the method of any of the foregoing embodiments.

According to other embodiments, a system for verifying a verifiable claim includes one or more processors and one or more computer-readable memories coupled to the one or more processors and having instructions stored thereon, the instructions being executable by the one or more processors to perform operations comprising: receiving a request from a first entity to verify a verifiable statement (VC) comprising a digital signature; obtaining a public key associated with a second entity based on the VC; determining that the digital signature was created based on a private key associated with the public key; the VC is authenticated based on the determination.

According to other embodiments, a non-transitory computer-readable storage medium is configured with instructions executable by one or more processors to cause the one or more processors to perform operations comprising: receiving a request from a first entity to verify a verifiable statement (VC) comprising a digital signature; obtaining a public key associated with a second entity based on the VC; determining that the digital signature was created based on a private key associated with the public key; the VC is authenticated based on the determination.

According to other embodiments, an apparatus for verifying a verifiable claim comprises: a receiving module for receiving a request from a first entity to verify a verifiable statement (VC) comprising a digital signature; an obtaining module for obtaining a public key associated with a second entity based on the VC; a determination module for determining that the digital signature was created based on a private key associated with the public key; and a verification module for verifying the VC based on the determination.

Embodiments disclosed herein have one or more technical effects. In some embodiments, the online platform provides online services, such as proxy services and resolver services, for blockchain-based off-center avatar management, and allows users to access such online services through an API interface. This allows for the use of programming languages or protocols other than those required by the blockchain to control operations related to the decentralized avatar management (e.g., creation and authentication of the decentralized identity, issuance and verification of the verifiable claims). According to some embodiments, an online platform provides a key management system for creating and securely maintaining a user's encryption keys in a secure environment. This reduces the security risk of independently creating and storing important identity credentials around the user. In other embodiments, the online platform provides an entity with an interface and automated software solution that manages identities on behalf of a plurality of other entities. The online platform also includes storing mapping information between the decentralized identity and the enterprise account or service ID. This facilitates the creation of a large number of de-centralized identifications or verifiable assertions and efficient cross-referencing of individual persons or entities to different identities using simplified control operations. In other embodiments, the online platform aggregates and performs certain transactions that would otherwise be performed by the blockchain system for off-center avatar management. This reduces the cost and resource consumption of performing the transaction.

These and other features of the systems, methods, and non-transitory computer readable media disclosed herein, as well as the methods of operation and functions of the related structural elements and the combination of parts and economies of manufacture, will become more apparent upon consideration of the following description and the appended claims with reference to the accompanying drawings, all of which form a part of this specification, wherein like reference numerals designate corresponding parts in the various figures. It is to be expressly understood, however, that the drawings are for the purpose of illustration and description only and are not intended as a definition of the limits.

Drawings

FIG. 1 illustrates a network environment associated with a blockchain in accordance with some embodiments.

FIG. 2 illustrates a framework for implementing blockchain transactions in accordance with some embodiments.

FIG. 3 illustrates a network environment associated with a system for managing decentralised identification and verifiable claims, in accordance with some embodiments.

FIG. 4 illustrates an architecture associated with a blockchain-based system for managing decentralised identification and verifiable declarations in accordance with some embodiments.

FIG. 5 illustrates a network environment associated with a system for implementing examples of various functions associated with decentralised identification and verifiable claims, in accordance with some embodiments.

FIG. 6 illustrates a method for creating a decentralised identity according to some embodiments.

Fig. 7 illustrates a method for authenticating a de-centralized identity using a DID authentication service, in accordance with some embodiments.

FIG. 8 illustrates a method of authenticating a decentralised identity using an identity management application in accordance with some embodiments.

FIG. 9 illustrates a method for issuing a verifiable claim, in accordance with some embodiments.

FIG. 10 illustrates a method for verifying verifiable claims, according to some embodiments.

FIG. 11 illustrates a method for creating a de-centralized identity using a proxy service, in accordance with some embodiments.

Fig. 12 illustrates a method for using proxy service authentication to de-center an identification, in accordance with some embodiments.

FIG. 13 illustrates a method for issuing verifiable claims using proxy services, in accordance with some embodiments.

FIG. 14 illustrates a method for verifying verifiable claims using a proxy service, in accordance with some embodiments.

FIG. 15 illustrates a flowchart of a method for creating a decentralised identity according to some embodiments.

FIG. 16 illustrates a flow diagram of a method for issuing a verifiable claim, in accordance with some embodiments.

FIG. 17 illustrates a flow chart of a method for verifying a verifiable claim, in accordance with some embodiments.

FIG. 18 illustrates a block diagram of a computer system for creating a decentralised identity, in accordance with some embodiments.

FIG. 19 illustrates a block diagram of a computer system for issuing verifiable claims, in accordance with some embodiments.

FIG. 20 illustrates a block diagram of a computer system for verifying a verifiable claim, in accordance with some embodiments.

FIG. 21 illustrates a block diagram of a computer system in which any of the embodiments described herein may be implemented.

Detailed Description

Embodiments described herein provide methods, systems, and apparatus associated with an ecosystem for off-center avatar management that can provide an entity with a unique and verifiable identity. The de-centralized identification (DID) of an entity may allow the entity to gain complete control over its identity and information associated with the identity. Verifiable Claims (VCs) may allow authorization, endorsements, and acknowledgements between different entities. In a business environment, a service or product provider may use its customer's DID and VC to identify and authenticate the customer and provide the service or product accordingly.

In some embodiments, the DID may be a unique identification indicating a mapping relationship between the real entity and the presentity. The DID may include URL scheme identification, identification for the DID method, and DID method specific identification. Each DID may point to a corresponding DID document. The DID document may include descriptive text about the DID and a preset format (e.g., JSON-LD) of the owner of the DID. The DID may be used as a Uniform Resource Identifier (URI) for locating the DID document. The DID document may include various attributes such as context, DID topic, public key, authentication, authorization, and delegation, service endpoint, creation, update, attestation, extensibility, other suitable attributes, or any combination thereof. The DID document may define or point to a resource defining a plurality of operations that may be performed with respect to the DID.

In some embodiments, the VC may provide verifiable online information about the quality, characteristics, relationships, and other related information of the entity. VC may contain descriptive text in a pre-set format (e.g., JSON-LD) describing one or more claims about DID (e.g., age of DID owner, educational background of DID owner), and endorsements of the claims by the entity. The VC may include various attributes such as context, identity, type, credential topic, publisher, release date, proof, expiration date, status, representation, other suitable attributes, or any combination thereof. The VC may specify the type of its declaration (claim), which may indicate the structure of the declaration. This may prompt the VC publisher and VC verifier to automatically process.

The owners of DID may participate in the identity management system in different roles. For example, an individual may desire to use a service provided by a business entity that needs to prove that the individual has exceeded 18 years old. The individual may be the owner of the DID and may request a VC issued by a government agency that provides for citizen age verification. The business entity may verify the VC to ensure that the individual meets age requirements. In this case, the person may be the DID owner and VC holder; the government entity may be a VC publisher and the business entity may be a VC verifier. As another example, a user may publish a VC to a first enterprise to allow the first enterprise to use user data stored by a second enterprise. In this case, the user may act as a VC publisher; the first enterprise may act as a DID owner and VC holder; the second enterprise may act as a VC verifier.

Some embodiments integrate various components, such as blockchain networks, cloud applications, proxy services, parser services, user applications, application Programming Interface (API) services, key Management Systems (KMSs), and other suitable components to implement functions such as creating and authenticating DID and publishing and validating VC. In some embodiments, an online platform integrating one or more of these components may facilitate a business entity to smoothly create DID and publish VCs for its users. The merchant may interact with the online platform through one or more API interfaces and trust the online platform with a plurality of encryption keys. The online platform may provide proxy services that perform various operations related to DID and VC on behalf of business entities and/or users thereof. Alternatively, the online platform may provide an SDK that may be integrated into the business entity's application to directly perform the operations related to DID and VC.

FIG. 1 illustrates a network environment associated with a blockchain in accordance with some embodiments. As shown, in environment 100, a client 111 may be coupled to a server side 118, and the server side 118 and node B may be coupled to a blockchain system 112 through various communication networks. Similarly, the server side 118 may optionally be coupled to more blockchain systems similar to the blockchain system 112, such as the blockchain system 113, the blockchain system 114, and the like. Each blockchain system may maintain one or more blockchains.

In some embodiments, client 111 may include one or more servers (e.g., node C) and one or more other computing devices (e.g., node A1, node A2, node A3). Node A1, node A2, and node A3 may be coupled to node C. In some embodiments, node C may be implemented by an entity (e.g., website, mobile phone application, organization, company, enterprise) having various local accounts (local accounts assessed from nodes A1, A2, node A3). For example, a mobile phone application may have millions of end-users (end-users) accessing the application's servers from corresponding user accounts. The server of the application may store millions of user accounts accordingly. The components of client 111 and their arrangement may have many other configurations.

In some embodiments, the node B may comprise a light node. The light node may not be able to download the complete blockchain, but may only download the blockhead to verify the authenticity of the blockchain transaction. The light nodes may be served by and effectively rely on full nodes (e.g., blockchain nodes in blockchain system 112) to access more functionality of the blockchain. By installing appropriate software, a lightweight node can be implemented in an electronic device such as a laptop, mobile phone, or the like.

In some embodiments, there may be more clients similar to client 111 coupled to server 118. The server side 118 may provide blockchain services (BaaS) and is referred to as BaaS cloud. In one embodiment, baaS is a cloud service model in which clients or developers outsource behind-the-scenes aspects of Web or mobile applications. BaaS may provide pre-written software for activities such as user authentication, database management, and remote updating that occur on the blockchain. The BaaS cloud may be implemented in a server, a server cluster, or other device. In one embodiment, the BaaS cloud provides enterprise-level platform services based on blockchain technology. The service can help the client to construct a safe and stable blockchain environment and easily manage the deployment, operation, maintenance and development of blockchains. Based on the rich security policies and multi-tenant isolation of the cloud, baaS clouds may use chip encryption techniques to provide advanced security protection. Based on the high reliability data storage, this service can provide an end-to-end high availability service that can be quickly extended without interruption. The BaaS cloud may provide local support for standard blockchain applications and data.

In some embodiments, the blockchain system 112 may include a plurality of blockchain nodes (e.g., blockchain node 1, blockchain node 2, blockchain node 3, blockchain node 4, blockchain node i, etc.) that maintain one or more blockchains (e.g., public blockchain, private blockchain, federated blockchain). Other blockchain systems (e.g., blockchain system 113, blockchain system 114) may include similar arrangements of blockchain nodes that maintain other blockchains. Each blockchain node may be found in one or more blockchain systems. The blockchain nodes of each blockchain system may maintain one or more blockchains. The blockchain nodes may include full nodes. The full node may download each blockchain and blockchain transaction and check them against the blockchain consensus rules. The blockchain nodes may form a network (e.g., a point-to-point network) in which one blockchain node communicates with another blockchain node. The order and number of blockchain nodes shown is merely an example for illustration. The blockchain node may be implemented in a server, computer, or the like. For example, each blockchain node may be implemented in a server or a cluster of servers. The server cluster may employ load balancing. Each blockchain node may correspond to one or more physical hardware devices or virtual devices coupled together via various types of communication methods, such as TCP/IP. Depending on the classification, blockchain nodes may also be referred to as full nodes, geth nodes, consensus nodes, and the like.

In environment 100, each node and device may be installed with appropriate software (e.g., application programming interfaces) and/or hardware (e.g., wired, wireless connections) to access other devices of environment 100. In general, nodes and devices may be capable of communicating with each other over one or more wired or wireless networks (e.g., the internet) over which data may be communicated. Each of the nodes and devices may include one or more processors and one or more memories coupled to the one or more processors. The memory may be non-transitory and computer-readable and configured with instructions executable by one or more processors to cause the one or more processors to perform the operations described herein. The instructions may be stored in memory or downloaded over a communication network without being stored in memory. Although the nodes and devices are shown as separate components in this figure, it should be understood that these nodes and devices may be implemented as a single device or as multiple devices coupled together. For example, node B may optionally be integrated into blockchain node 2.

Devices such as node A1, node A2, node A3, node B, and node C may be installed with appropriate blockchain software to create blockchain accounts and initiate, forward, or access blockchain transactions. The term "blockchain transaction" may refer to a task unit that is executed in a blockchain system and recorded in the blockchain. For example, node A1 may access the blockchain by communicating with node C, server side 118, and blockchain node 1, and node B may access the blockchain by communicating with blockchain node 2. In some embodiments, node A1 may submit a blockchain account creation request to node C. Node C may forward the request and other similar requests to server side 118. Server side 118 may create a blockchain account accordingly.

In some embodiments, after receiving a blockchain transaction request for an unacknowledged blockchain transaction, the recipient blockchain node may perform some preliminary verification of the blockchain transaction. For example, blockchain node 1 may perform a preliminary verification after receiving a blockchain transaction from node C. Once validated, the blockchain transaction may be stored in a pool database of the recipient blockchain node (e.g., blockchain node 1), which may also forward the blockchain transaction to one or more other blockchain nodes (e.g., blockchain node 3, blockchain node 4). Because each blockchain node may include memory or be coupled to memory, the pool database may be stored separately in the blockchain node's memory. The pool database may store a plurality of blockchain transactions submitted by one or more client devices. After receiving the blockchain transaction, one or more other blockchain nodes may repeat the processing by the recipient blockchain node.

Each blockchain node may select some blockchain transactions from the pool according to its preferences and form them into new blocks that are proposed to the blockchain. The blockchain nodes can solve complex mathematical problems by devoting computational effort, thereby "mining" the proposed new block. If the blockchain transaction involves a blockchain contract, the blockchain node may execute the blockchain contract locally in the corresponding Virtual Machine (VM). To process a blockchain contract, each blockchain node of the blockchain network may run a corresponding virtual machine and execute the same instructions in the blockchain contract. Virtual machines are software simulations of computer systems that are based on a computer architecture and that provide the functionality of a physical computer. Virtual machines in a blockchain environment may be understood as systems designed to function as the running environment for blockchain contracts.

A particular blockchain node that successfully excavates a new block of the proposed blockchain transaction according to consensus rules may package the new block into its local copy of the blockchain and multicast the result to other blockchain nodes. The particular blockchain node may be the blockchain node that successfully completes the validation first, has obtained validation privileges, has been selected based on another consensus rule, or the like. The other blockchain nodes may then locally execute blockchain transactions in the new block in the same order of execution as the particular blockchain node, verify the execution results from each other (e.g., by performing hash computations), and synchronize their local copies of the blockchain with the copies of the particular blockchain node. By updating the local copy of the blockchain, other blockchain nodes may similarly write such information in the blockchain transaction to the corresponding local memory. Thus, blockchain contracts may be deployed on blockchains. If at some point the validation fails, the blockchain transaction is rejected.

The deployed blockchain contracts may have an address from which the deployed contracts may be accessed. The blockchain node may invoke the deployed blockchain contract by entering certain parameters into the blockchain contract. In one embodiment, node C or node B may request to invoke a deployed blockchain contract to perform various operations. For example, data stored in a deployed blockchain contract may be retrieved. For another example, data may be added to a deployed blockchain contract. For yet another example, a financial transaction specified in the deployed blockchain contract may be performed. Nonetheless, other types of blockchain systems and associated consensus rules may be applied to the disclosed blockchain systems.

FIG. 2 illustrates a framework for implementing blockchain transactions in accordance with some embodiments. In some embodiments, client 111 may send information (e.g., a request with related information for creating a blockchain account) to server side 118 for server side 118 to create the blockchain account. To this end, server side 118 may generate encryption keys, compile the request with other account creation requests, and/or perform other operations. The server side 118 may then send a blockchain transaction (e.g., blockchain transaction a) including the compiled account creation request to one or more of the blockchain nodes for execution.

In some embodiments, the node B may construct and send the signed blockchain transaction to one or more blockchain nodes for execution. In one embodiment, the node B may construct a blockchain transaction B. Blockchain transaction B may include blockchain contract B for deploying or invoking the deployed blockchain contract. For example, blockchain transaction B may include creating a blockchain account or invoking a blockchain contract of a deployed blockchain contract a. Blockchain contract B may be programmed in source code at the client application 221. For example, a user or machine may program blockchain contract B. The node B may compile the source code using a corresponding compiler that converts the source code into bytecodes. The blockchain transaction B may include information such as a random number (e.g., a transaction serial number), from (e.g., a blockchain address of the node B or another blockchain address), to (e.g., null in the case of a deployed blockchain contract), transaction fees, value (e.g., transaction amount), signature (e.g., a signature of the node B), data (e.g., a message to a contract account), and so forth. The node B may send the blockchain transaction B to one or more blockchain nodes for execution through a Remote Procedure Call (RPC) interface 223. An RPC is a protocol that a first program (e.g., a client application) can use to request services from a second program located in another computer (e.g., a blockchain node) on the network without understanding the details of the network. When the first program causes a process to execute in a different address space, it then appears as if it were a normal (local) process call, without the programmer explicitly encoding the details of the remote interaction.

In some embodiments, upon receiving a blockchain transaction (e.g., blockchain transaction a or B), the recipient blockchain may verify whether the blockchain transaction is valid. For example, signatures and other formats may be verified. If the verification is successful, the recipient blockchain node may broadcast the received blockchain transaction (e.g., blockchain transaction A or B) to a blockchain network that includes various other blockchain nodes. Some blockchain nodes may participate in the mining process of blockchain transactions. Blockchain transactions may be picked by a particular node for consensus verification to be packaged into new blocks. If the blockchain transaction involves a blockchain contract, the particular node may create a contract account of the blockchain contract that is associated with the contract account address. If the blockchain transaction involves invoking a deployed blockchain contract, then the particular node may trigger its local virtual machine to execute the received blockchain transaction, thus invoking the deployed blockchain contract from its local copy of the blockchain and updating the account status in the blockchain. If a particular node successfully digs out a new block, the particular node may broadcast the new block to other blockchain nodes. Other blockchain nodes may verify that the new block is excavated by the particular blockchain point. If consensus is reached, blockchain transaction B is packaged separately into local copies of blockchains maintained by blockchain nodes. The blockchain node may similarly trigger its local virtual machine to execute blockchain transaction B, invoking blockchain contract a deployed on the local copy of the blockchain and making a corresponding update.

Upon receiving a new block, other blockchain nodes may perform verification. If consensus is effectively reached for the new blocks, the new blocks are individually packaged into local copies of the blockchain maintained by the blockchain nodes. The blockchain nodes may similarly trigger their local virtual machines (e.g., local virtual machine 1, local virtual machine i, local virtual machine 2) to perform blockchain transactions in the new block, thereby invoking local copies of the blockchain (e.g., local blockchain copy 1, local blockchain copy i, local blockchain copy 2) and making corresponding updates. The hardware machines of each blockchain node may access one or more virtual machines, which may be part of or coupled to the corresponding blockchain node. Each time a corresponding local virtual machine may be triggered to perform a blockchain transaction. Also, all other blockchain transactions in the new block will be performed. The light nodes may also be synchronized with the updated blockchain.

FIG. 3 illustrates a network environment associated with a system for managing decentralised identification and verifiable claims, in accordance with some embodiments. In some embodiments, the client system 310 may correspond to an entity. The entity may be a business entity that provides one or more products or services to a plurality of users. The entity may also be a single user, a group of users, an organization, other suitable entity, or any combination thereof. Client system 310 may include a plurality of computer systems, data stores, cloud services, mobile applications, other suitable components, or any combination thereof. Client system 310 may include a server 311 and a database 313. Database 313 may store data associated with multiple user accounts of users of the entity. An entity corresponding to customer premise system 310 may desire to create and manage DID and VC for itself and its users. It may include one or more Software Development Kits (SDKs) 312 for managing the creation and authentication of DID or the release and verification of VC.

In some embodiments, to implement the functionality associated with the DID and VC, the client system 310 may interface with the server system 320. In some embodiments, the server side system 320 as shown in fig. 3 may be identical to, form part of, or include one or more components of the server side 118 as shown in fig. 1 and 2. The server system 320 may include one or more proxy services 321, one or more resolvers 322, one or more key management systems 323, one or more clouds 324, other suitable components, or any combination thereof. Proxy service 321 may provide various services or applications related to the DID or VC and maintain a database that maps account information or other business data from user end system 310 to the DID, VC, or other information or data stored on one or more blockchains. Proxy service 321 may provide one or more Application Programming Interfaces (APIs) that client system 310 may use to directly submit requests related to DID or VC. Proxy service 321 may manage communications between client system 310 and resolver 322 and cloud 324.

In some embodiments, proxy service 321 may be coupled to a Key Management System (KMS) 323.KMS 323 may generate, distribute, and manage encryption keys for devices and applications. They may range from secure generation of keys to secure exchange of keys to secure key processing and storage security aspects. The functions of KMS 323 may include key generation, distribution and replacement, and key injection, storage and management. KMS 323 may include or be coupled to a Trusted Execution Environment (TEE). The TEE may be an isolated area on the device's main processor that is separate from the main operating system. The TEE may provide an isolated execution environment that provides security features such as isolated execution, the integrity of applications executing using the TEE, and the confidentiality of its assets. It can ensure that internally loaded code and data are protected in terms of confidentiality and integrity. In some embodiments, KMS 323 may generate one or more encryption key pairs in the TEE. The TEE may encrypt the private key before outputting the encryption key pair. The private key may be encrypted based on various methods or standards such as Data Encryption Standard (DES), tripleDES, RSA, advanced Encryption Standard (AES), twist, etc. KMS 323 may store an encrypted private key associated with the public key. To use the private key, KMS 323 may feed the encrypted private key to the TEE for decryption and processing.

In some embodiments, proxy service 321 may be coupled to parser 322, and parser 322 may include a software application to manage interactions between proxy and blockchain 330 (e.g., correspondence between DID and DID documents) in transactions related to DID or VC. The parser 322 may be part of or coupled to one or more cloud-based services. The one or more cloud-based services may be associated with a blockchain as a service (BaaS) cloud or other suitable cloud service. Cloud 324 may build a platform that provides various interfaces for one or more blockchains 330. It may receive input from an external application and facilitate creation and execution of operations based on the input, such as blockchain transaction deployment, blockchain contract creation and execution, blockchain account creation. The cloud 324 may also obtain information and data from one or more blockchains 330 and feed the information and data to one or more other systems using the cloud 324. In some embodiments, proxy service 321 may be directly coupled to cloud 324 to use its services. In some embodiments, one or more of proxy service 321, parser 322, and KMS 323 may be integrated as part of cloud 324 or part of another suitable online platform.

In some embodiments, the parser 322 and the cloud 324 may be coupled to the blockchain 330. The blockchain 330 may include one or more blockchain contracts 331. The one or more blockchain contracts 331 can be configured to be executed by virtual machines associated with the blockchain 330 to perform one or more operations associated with DID and VC. The operations may include creating a new DID, storing a DID document, updating a DID document, identifying a DID document based on a DID, storing information associated with a VC, retrieving information associated with a VC, other suitable operations, or any combination thereof. The parser 322 and cloud 324 may be configured to deploy one or more transactions on the blockchain 330 that invoke one or more blockchain contracts 331. The transaction may trigger one or more operations related to the DID and VC.

FIG. 4 illustrates an architecture associated with a blockchain-based system for managing decentralised identification and verifiable declarations in accordance with some embodiments. In some embodiments, the system may include three main components: one or more proxy services 321, one or more resolvers 322, and one or more blockchain contracts 331. The one or more proxy services 321 may be configured to process requests received from users relating to DID and VC. The one or more proxy services 321 may manage the mapping between account information on the client system 310 and the DID of the account owner. Proxy service 321 may include DID proxy service API 410 for receiving a request related to a DID from client system 310. Depending on the nature of the request, it may be fed to a user agent 411 for performing operations such as creating and authenticating DID, or to a publisher agent 412 for performing operations such as publishing VC. A request from a party desiring to authenticate a VC may be fed to the verifier agent 413. The one or more proxy services 321 may also provide a verifiable claims store 414 for storing one or more VCs. The proxy service 321 may also use one or more memories 415 and one or more databases 416. Proxy service 321 may be coupled to KMS 323 and cloud 324. Proxy service 321 may be coupled to parser 322.

In some embodiments, one or more agents of proxy service 321 may send one or more requests to DID parser API 420 associated with parser 322. The parser 322 may be configured to handle interactions between the proxy service 321 and the blockchain 330. The parser 322 may perform operations such as obtaining data from the blockchain 330, adding data to the blockchain 330, creating a blockchain contract 331, deploying transactions to the blockchain 330 to invoke the blockchain contract 331, other suitable operations, or any combination thereof. The parser 322 may include a DID parser 421 and a VC parser 422, the DID parser 421 being configured to manage DID and DID documents stored on the blockchain 330, the VC parser 422 being configured to manage VCs of DID created based on the blockchain 330. Parser 322 may also include a listener 424 for obtaining data from blockchain 331. Listener 424 can store the obtained data to database 423. This data may be used by DID parser 421 and VC parser 422. DID parser 421, VC parser 422, and listener 424 may be coupled to cloud 324 for interacting with blockchain 330.

In some embodiments, the blockchain 330 may include one or more blockchain contracts (331 a, 331b, 331 c) for managing DID and DID documents, and one or more contracts (331 d, 331e, 331 f) for managing VCs. The contract may be executed by one or more virtual machines associated with blockchain 330 to perform operations such as creating a DID, storing a DID document, updating a DID document, storing information associated with a VC, other suitable operations, or any combination thereof.

FIG. 5 illustrates a network environment associated with a system for implementing examples of various functions associated with decentralised identification and verifiable claims, in accordance with some embodiments. Components of the network environment may be categorized into three layers 510, 520, and 530. In some embodiments, the bottom or core layer 510 may include one or more blockchains 330, and the blockchains 330 may include one or more blockchain contracts (331 g, 331h, 331 i) that may be executed to perform operations related to DID and VC. The blockchain 330 may store a plurality of DID and a plurality of DID documents corresponding to the plurality of DID. The blockchain contracts (331 g, 331h, 331 i) may be configured to manage mappings between DID and DID documents and creation and modification of DID documents. The blockchain 330 may be accessible to one or more resolvers (322 a, 322 b) for DID and VC related operations. The parser (322 a, 322 b) may be configured to provide a service to an external system, for example, searching a DID document or data contained in the DID document, based on the input DID. One or more method libraries 511 may also be available to external systems to interact with the blockchain 330.

In some embodiments, middle or enhancement layer 520 may include one or more user agents 411, one or more publisher agents 412, or one or more verifier agents 413. In some embodiments, the blockchain 330 may include a federated blockchain that is directly accessible or not directly accessible to users that are not consensus nodes of the federated blockchain. The user agent 411 may provide an interface for a general user to interact with the blockchain. In some embodiments, the user agent 411 may be configured to create one or more DID, authenticate one or more DID, interact with one or more verifiable data registries 521 or one or more DID centers (DID hub) 522, send notifications to the owners of DID, perform other suitable functions, or any combination thereof. Here, the DID center 522 may include a system in which the DID owner stores therein sensitive data of the DID owner. The owner may grant some other entity (e.g., the institution that issued the verifiable claim) access to the data stored in DID center 522. Verifiable data registry 521 may include a VC repository for storing and managing VCs issued to DID owners. Publisher agent 412 may include one or more APIs (e.g., REST APIs) or SDKs. Publisher agent 412 may be configured to publish one or more verifiable claims, withdraw one or more verifiable claims, examine and verify existing verifiable claims, publish templates for verifiable claims, maintain templates for verifiable claims, perform other suitable operations, or any combination thereof. Verifier agent 413 may include one or more APIs (e.g., REST APIs) or SDKs and be configured to verify the verifiable claim or perform one or more other suitable operations. In some embodiments, layer 520 may also include one or more code libraries (e.g., DID resolution library 523, DID authentication library 524) that may be employed and may be used to interact with DID resolver 322 or directly with blockchain 330. The code library may be packaged into one or more SDKs and may be used to perform functions such as DID authentication, interaction with the blockchain 330, or interfacing with the blockchain contract 331. Publisher agent 412 and verifier agent 413 may be used by key participants in the network environment associated with DID and VC, such as entities capable of performing authentication of your customers (KYC) or endorsing users, or entities that publish or verify verifiable claims (e.g., government agencies, banks, financial service providers). The key participants may provide third party services that may be integrated through connections with the publisher agent 412, the verifier agent 413, or other suitable components of the network environment.

In some embodiments, upper or extension layer 530 may include one or more external services or applications related to DID and VC. The services or applications may include one or more publisher applications 531, one or more verifier applications 532, an identity management application 533, a service application 534, one or more other suitable services or applications, or any combination thereof. The publisher application 531 may correspond to an entity (e.g., government agency, bank, credit agency) that publishes a verifiable statement signed or endorsed by the entity for the user. The publisher application 531 may operate on the client system 310. The publisher application 531 may include a publisher verifiable claim manager service that may allow publishers to manage published VCs, maintain their state (e.g., validity), or perform other suitable operations. Publisher application 531 may interact with layers 510 and 520 by interfacing or interfacing with publisher agent 412 or one or more code libraries 523 and 524. The verifier application 532 may correspond to an entity (e.g., service provider, credit issuer) that needs to verify a verifiable claim to determine information (e.g., identity, age, credit score) of a user. The verifier application 532 may operate on the client system 310. Verifier application 532 may interact with layers 510 and 520 by interfacing or interfacing with verifier agent 413 or one or more code libraries 523 and 524. The identity management application 533 may be installed on a client device or terminal associated with the user. The user may be a DID owner, which may be a person, business, organization, application, or any other suitable entity. The identity management application 533 may allow a user to manage an encryption key pair associated with a DID, original data, or VC to receive notification from the user agent 411, authenticate the DID, grant access to the data, use the VC, perform other suitable operations, or any combination thereof. Identity management application 533 may interact with layers 510 and 520 by interfacing or interfacing with user agent 411. The service application 534 may also be coupled to the user agent 411 and configured to manage functionality related to the DID or VC of one or more users or accounts.

Fig. 6-10 illustrate exemplary operations associated with DID or VC performed by one or more client systems 310, one or more resolvers 322, one or more clouds 324, or one or more blockchains 330. In some embodiments, client system 310 may manage one or more DID or one or more VCs by interfacing with DID parser 322 and blockchain 330 storing DID and DID documents. The client system 310 may use one or more SDKs 312 to manage DID that are compatible with the method associated with the DID. The SDK 312 may be integrated with one or more applications used by the client system 310. The client system 310 may also interface with one or more service endpoints for storing verifiable claims, one or more service endpoints for storing state information of verifiable claims, one or more service endpoints for authenticating DID, other suitable systems, or any combination thereof.

FIG. 6 illustrates a method for creating a decentralised identity according to some embodiments. The operations of the methods presented below are intended to be illustrative. Depending on the implementation, the method may include additional, fewer, or alternative steps performed in various orders or in parallel. The method may begin at step 602, where the server 311 of the client system 310 may obtain an identity of a user who will obtain a DID. The client system 310 may also generate or retrieve an encryption key pair that includes a public key and a private key for creating the DID. The server may call the function of the SDK 312 to create a new DID in step 604. Here, at least the public key of the encryption key pair may be entered or otherwise made available to the SDK 312. At step 606, the client system 310 may send a request to the parser 322 to create a new DID using the SDK 312. At step 608, the parser 322 may send a request to the blockchain 330 to create a new blockchain account. Here, the request may be sent directly to one or more blockchain nodes of blockchain 330 in the form of one or more blockchain transactions, or to cloud 324 or other suitable interface system associated with blockchain 330. In response to the request from the resolver 322, the resolver 322 may obtain an indication from the cloud 324 that a new blockchain account has been created, step 610. The blockchain account may be associated with an address on the blockchain 330. The information obtained by parser 322 may include information associated with the newly created blockchain address. It may include the newly created DID or at least enough information to compose the DID. At step 612, the parser 322 may send a message back to the SDK 312 associated with the client system 310. The message may include information associated with the newly created DID.

In some embodiments, DID documents may be created and stored on blockchain 330. In step 614, the client system may use the SDK 312 to generate a DID document and add the public key and authentication information associated with the newly created DID to the DID document. At step 616, the client system 310 may use the SDK 312 to add information associated with one or more service endpoints (e.g., information associated with an authenticated service endpoint, information associated with a verifiable claim repository) to the DID document. The authentication service endpoint and verifiable claim repository may be provided as part of a system that includes the parser 322, or may be provided by a third party system. The client system may then use the SDK 312 to generate one or more blockchain transactions for storing the DID document to the blockchain 330 at step 618. The client system 310 may also use the SDK 312 to generate a hash value for the blockchain transaction and use a private key associated with the DID to generate a digital signature for the transaction. At step 620, the SDK 312 may send the DID document and the blockchain transaction to the DID parser 322 for transmission to the blockchain system. At step 622, the did parser may send one or more transactions to the blockchain system (e.g., one or more blockchain nodes, cloud 324). One or more transactions may invoke a blockchain contract 331 for managing DID and DID documents on the blockchain 330. In step 624, the parser 322 may obtain information from the blockchain 330 indicating that the DID document has been successfully stored. In step 626, the parser 322 may forward the acknowledgement to the SKD 312. The sdk 312 may transmit information associated with the created DID and the DID document to the server 311 of the client system 310 in step 628, and then the server 311 may transmit a notification confirming that the DID was successfully created to the user in step 630.

Fig. 7 illustrates a method for authenticating a de-centralized identity using a DID authentication service, in accordance with some embodiments. The operations of the methods presented below are intended to be illustrative. Depending on the implementation, the method may include additional, fewer, or alternative steps performed in various orders or in parallel. In some embodiments, a user owning a DID may use a DID authentication service provided by a business entity to enable authentication of his DID ownership. The owner may trust the public-private key pair corresponding to the DID to the business entity for storage. The owner may provide the network location (e.g., identified by the URL) of the DID authentication service as the service endpoint of the DID authentication. The location identification of the DID authentication service may be included in the "service" field of the DID document associated with the DID.

In some embodiments, the verifier 532 (e.g., a service provider that needs to verify customer information) may use the SDK 312 to initiate the DID authentication process. At step 702, verifier 532 may obtain the DID provided by the owner of the claim. At step 704, the verifier 532 may invoke the SDK 312 to create the DID authentication challenge. The verifier 532 may input the DID to be authenticated and the network address (e.g., URL) to which the response to the challenge is to be sent to the SDK 312. In step 706, the sdk 312 may send a query to the parser 322 for the DID document associated with the DID to be authenticated. At step 708, the parser 322 may formulate a blockchain transaction that invokes the blockchain contract 331 for managing DID and send the blockchain transaction to one or more blockchain nodes associated with the blockchain 330 for execution. As a result, the parser 322 may obtain a DID document corresponding to the DID in step 710 and forward it to the SDK 312 in step 712. At step 714, the verifier 532 may create a DID authentication challenge based on the obtained DID document using the SDK 312. In some embodiments, the DID authentication challenge may include ciphertext created by encrypting the original text using a public key associated with the DID recorded in the DID document. The challenge may also include a network address to which the response is to be sent. At step 716, the verifier 532 may obtain information associated with the authentication service endpoint of the DID from the DID document. At step 718, the verifier 532 may send a challenge to the DID authentication service associated with the DID using the SDK 312.

In some embodiments, after obtaining the DID authentication challenge from verifier 532, the DID authentication service may obtain consent to such an authentication request from the owner at step 720. If the owner provides consent or permission for identity authentication, then the DID authentication service may invoke its SDK 312 version to create a response to the DID authentication challenge at step 722. In some embodiments, the response to the DID authentication challenge may include plaintext, which is the result of decrypting ciphertext in the challenge using a private key associated with the DID. The sdk 312 may return a response to the DID authentication service in step 724, and the DID authentication service may then send the response to the network address provided by the verifier 432 in step 726. After receiving the response to the DID authentication challenge, the verifier 532 may invoke its SDK 312 to check the response, step 728. In step 730, the SDK 312 can determine whether the response proves that the user providing the DID is the owner of the DID. In some embodiments, the SDK 312 may examine the response by comparing the decrypted text in the response to the original text used to create the DID authentication challenge. If the response is determined to be correct, the SDK 312 can return a message to the verifier 532 indicating that the DID is a valid proof of the user identity in step 732. At step 734, verifier 532 may notify the user of the validity of the DID.

FIG. 8 illustrates a method of authenticating a decentralised identity using an identity management application in accordance with some embodiments. The operations of the methods presented below are intended to be illustrative. Depending on the implementation, the method may include additional, fewer, or alternative steps performed in various orders or in parallel. In some embodiments, the user may manage the DID using a terminal, which may include an identity management application or another suitable application. The application may include a version of the SDK 312. In this example, the user may need a service from a service provider (i.e., verifier) that needs to verify that the user owns a particular DID in order to provide his service. The user may send a service request to the verifier. The service request may be in the form of an HTTP request.

At step 802, a user may invoke an identity management application to provide authentication information for a service request. The user may provide the original service request as input to the SDK 312 included in the identity management application. The sdk 312 may sign the content of the original service request using a private key in an encryption key pair associated with the DID at step 804. The SDK 312 may be used to add the DID and digital signature of the original service request to create a signed service request. In the case where the original service request is an HTTP request, the SDK 312 may add the DID and the digital signature to the header of the HTTP request. The sdk 312 may send the signed service request to the verifier 532 at step 806.

In some embodiments, at step 808, the verifier 532 may invoke its version of the SDK 312 to authenticate the DID included in the signed service request. The sdk 312 may obtain the DID and digital signature included in the signed service request at step 810. In the case where the signed service request is an HTTP request, the DID and the digital signature may be obtained from the header of the HTTP request. At step 812, the sdk 312 may send a query to the parser 322 for the DID document associated with the DID to be authenticated. At step 814, the parser 322 may formulate a transaction that invokes the blockchain contract 331 for managing DID and send the transaction to one or more blockchain nodes associated with the blockchain 330 for execution. As a result, the parser 322 may obtain a DID document corresponding to the DID in step 816 and forward it to the SDK 312 in step 818. At step 820, the SDK 312 associated with the verifier 532 may examine the signed service request based on the obtained DID document to determine if it came from the owner of the DID. In some embodiments, the SDK 312 may sign the content of the service request using a public key obtained from the DID document and check the resulting signature against the digital signature included in the signed service request to determine whether the public key is associated with the digitally signed key in the service request used to create the signature. If so, the SDK 312 can determine that the service request from the user is valid. The sdk 312 may then send the service request to the verifier 532 for processing at step 822. At step 824, verifier 532 may process the service request and provide the appropriate service to the user. The verifier 532 may then send a response to the user to confirm completion of the requested service at step 826.

FIG. 9 illustrates a method for issuing a verifiable claim, in accordance with some embodiments. The operations of the methods presented below are intended to be illustrative. Depending on the implementation, the method may include additional, fewer, or alternative steps performed in various orders or in parallel. In some embodiments, publisher 531 may publish VCs to users. VC may be used as a proof of certain facts or features of the user endorsed by the publisher 531.

In step 902, the publisher 531 may obtain a DID associated with the user and a proof of the fact to be included in the VC. Here, the proof of fact to be included in the VC may be based on material submitted by the user to the publisher 531, information or data obtained by the publisher 531 from a third party system, principal verification of the fact, other suitable sources of proof, or any combination thereof. After obtaining the DID and the proof, the publisher 531 may call the SDK 312 associated with the creation of the VC to initiate a process for creating the VC in step 904. The message from the publisher 531 may include a statement or statement about the user's proven facts. SDK 312 may use the encryption key pair associated with issuer 531 to create a VC document that includes the claims. In some embodiments, the VC may include a digital signature created based on a private key associated with the issuer 531. In step 908, the sdk 312 may update the local storage state of the VC.

At step 910, the sdk 312 may send a query to the parser 322 for DID documents associated with the DID to which the VC was issued. At step 912, the parser 322 may formulate a transaction that invokes the blockchain contract 331 for managing DID and send the transaction to one or more blockchain nodes associated with the blockchain 330 for execution. As a result, the parser 322 may obtain a DID document corresponding to the DID at step 914 and forward it to the SDK 312 at step 916. At step 918, the sdk 312 may identify a VC service endpoint associated with the DID of the user for storing VCs. The VC service endpoint may correspond to VC repository 414 used by a user or owner of the DID. The publisher may then send the VC to VC repository 414 for storage using SDK 312 at step 920. The VC may also include information associated with a VC state service endpoint that may store and provide state information for the VC. In some embodiments, this information may include a network address (e.g., URL) of a publishing agent service used by publisher 531 to save the state of the VC. VC state service endpoints may or may not be associated with VC repository 414. SDK 312 may provide the current state of the newly generated VC to the VC state service endpoint for storage. The state of a VC may be stored on a blockchain.

FIG. 10 illustrates a method for verifying verifiable claims, according to some embodiments. The operations of the methods presented below are intended to be illustrative. Depending on the implementation, the method may include additional, fewer, or alternative steps performed in various orders or in parallel. In some embodiments, a user may provide a VC to another party (e.g., verifier 532) to document the facts stated in the VC. The VC may be provided after verifier 532 has verified that the user is the owner of the DID associated with the VC.

At step 1002, verifier 532 may invoke SDK 312, which includes a code library associated with VC verification, to verify the VC. SDK 312 may identify information associated with the VC state service endpoint for the VC from the VC (e.g., in the "credential state" field). The VC state service endpoint may be associated with a publisher 531. At step 1004, the sdk 312 may send a query to the publisher 531 for the status of the VC. In response, the publisher 531 may invoke the SDK 312 to obtain the state of the VC at step 1006. The SDK 531 may obtain the state of VC. As an example, at step 1008, the sdk 312 may determine that the VC has a valid state and may return information to the publisher 531. The publisher may then return valid state information to the SDK 312 associated with the verifier 532 at step 1010.

Verifier 532 may obtain an identification associated with publisher 531 of the VC. For example, the identification may be the DID of the publisher 531. At step 1012, the sdk 312 may send a query to the parser 322 for a public key associated with the DID of the issuer 531 of the VC. In step 1014, the parser 322 may formulate a transaction invoking the blockchain contract 331 for managing the DID and send the transaction to one or more blockchain nodes associated with the blockchain 330 for execution. As a result, the parser 322 may obtain the public key corresponding to the DID at step 1016 and forward it to the SDK 312 associated with the verifier 532 at step 1018. At step 1020, the SDK 312 associated with the verifier 532 may verify the VC based on the digital signature included therein and the public key associated with the issuer 531 of the VC. In step 1022, if the VC is authenticated, the SDK 312 may send an acknowledgement to the verifier 532.

Fig. 11-14 illustrate exemplary operations associated with DID or VC performed by one or more client systems 310, one or more proxies 321, one or more resolvers 322, one or more clouds 324, one or more blockchains 330, one or more KMSs, or other suitable systems, applications, services. In some embodiments, client system 310 may manage one or more DID or VC by interacting with an online platform that integrates one or more of the above components via one or more API interfaces (e.g., REST API). The user system 310 may trust confidential information, such as an encryption key pair, to the online platform for secure storage.

FIG. 11 illustrates a method for creating a de-centralized identity using a proxy service, in accordance with some embodiments. The operations of the methods presented below are intended to be illustrative. Depending on the implementation, the method may include additional, fewer, or alternative steps performed in various orders or in parallel. In some embodiments, a client system 310 associated with an entity may use one or more proxy services 321 to create one or more DID for one or more users of the entity and associate the DID with an internal account or identity (e.g., service ID) maintained by the entity. To create a DID for its user, the entity may have been authenticated by the online platform as a trusted entity and may have committed to providing real information. In some embodiments, the entity may have issued a VC by a bootstrap (bootstrap) issuer DID to prove that the entity has been authenticated by an authoritative entity. An entity may need to authenticate the identity of its user. The client system 310 may use one or more KMSs 323 and the secure environment (e.g., TEE) they provide to manage encryption keys associated with the created DID and map the encryption keys to internal accounts or identifications maintained by the entity. By means of the proxy service 321, the client system 310 can use the service associated with the DID without keeping a record of the DID. Instead, it may simply provide its internal account information or identification information for identifying the DID via one or more interfaces associated with proxy service 321.

In some embodiments, an online platform for managing DID may receive a request to create a DID. The request may be from a first entity on behalf of a second entity for creating a DID for the second entity. In the example shown in fig. 11, an entity (e.g., a first entity) may create a DID for a user (e.g., a second entity) that may have an account with a business entity. In some embodiments, the entity may authenticate the identity of the user before creating the DID for the user. For example, at step 1102 of fig. 11, the server 311 of the client system 310 associated with the entity may perform authentication or otherwise obtain the user's authentication information. The entity may have previously verified the identity of the user and may maintain such information in a database. In step 1102, the server 311 may retrieve such information. Then, in step 1104, the server 311 may send a request for creating a DID to the proxy service API 410 associated with the user agent 411, the user agent 411 being associated with the online platform. The request may include an account identification corresponding to the user. The request may take the form of an API message. In step 1106, the proxy service API 410 may send a request to the user agent 411 to create a DID.

At step 1108, the user agent 411 may examine the request for the desired information. In some embodiments, to create a user's DID, an entity may be required to have its own existing DID. The user agent 411 may examine the request to determine that the sender of the request has an existing DID and to determine the DID associated with the sender. In some embodiments, it may be desirable for the entity to provide proof of identity authentication for the user. The proof of identity authentication may include proof of true person authentication, proof of real name authentication, other suitable proof of authentication, or any combination thereof. For example, the certification of the real name certification may be based on an official identification of the user (e.g., a government issued ID). An exemplary proof may be, for example, a number created by applying a hash function (e.g., SHA-256) to a combination of ID type, ID number, and user number. Such attestation may ensure unique correspondence with a particular user while maintaining sensitive information kept secret by the user. The user agent 411 may determine whether the request includes proof of identity authentication and if so, accept the request. If the request does not include proof of identity, the user agent 411 may reject the request or may send a request for proof of identity to the entity. The user agent 411 may obtain proof of identity based on a received request, which may directly include the proof or information associated with the method used to obtain the proof. If the request includes the required information, the user agent 411 may create a key alias (key alias) for the user that corresponds to a proof of identity authentication of the user, step 1110.

In some embodiments, the user agent 411 may obtain a public key of an encryption key pair in response to receiving the request. The public key may later be used as a basis for creating the DID. In some embodiments, user agent 411 may obtain a public key from KMS 323. In step 1112, user agent 411 may send a request to KMS 323 for generating and storing an encryption key pair. KMS 323 may generate an encryption key pair. In some embodiments, KMS 323 may cause an encryption key pair to be generated in a TEE associated with KMS 323. After key pair generation, KMS 323 may obtain the public key and the encrypted private key from the TEE. In step 1114, kms 323 may send the public key to user agent 411.

In some embodiments, the online platform may obtain the DID based on the public key. In step 1116, the user agent 411 may send a request to the parser 322 to create a new DID. The request may include a public key. In response, parser 322 may generate one or more blockchain transactions for creating a DID based on the public key and adding the DID document associated with the DID to the blockchain. Optionally, the DID parser may send a request to the cloud 324 to generate such a transaction. For example, in step 1118, the parser 322 may send a request to the blockchain 330 to create a new blockchain account. Here, the request may be sent directly to one or more blockchain nodes of blockchain 330 in the form of one or more blockchain transactions, or to cloud 324 or other suitable interface system associated with blockchain 330. The blockchain transaction may invoke one or more blockchain contracts configured to manage DID. In response to the request from the resolver 322, the did resolver may obtain an indication of a successful creation of a new blockchain account from the blockchain 330 or the cloud 324, step 1120. The blockchain account may be associated with an address on the blockchain 330. The information obtained by the parser 322 may include information associated with the newly created blockchain address. It may directly include the newly created DID or at least enough information to compose the DID. At step 1122, the parser 322 may send a message back to the user agent 411. The message may include information associated with the newly created DID.

In some embodiments, DID documents may be created and stored in blockchain 330. In step 1124, the user agent 411 may generate a DID document and add the public key associated with the newly created DID and authentication information to the DID document. In step 1126, the user agent 411 may add information associated with one or more service endpoints (e.g., information associated with an authentication service endpoint, information associated with a verifiable claim repository) to the DID document. Authentication service endpoint and verifiable claims store 414 may be provided as part of an online platform. The DID document may include: one or more public keys associated with the obtained DID, authentication information associated with the obtained DID, authorization information associated with the obtained DID, delegation information associated with the obtained DID, one or more services associated with the obtained DID, one or more service endpoints associated with the obtained DID, the creator's DID of the obtained DID, other suitable information, or any combination thereof. In some embodiments, the DID document may include a "creator" field containing identification information (e.g., DID) representing the entity that sent the request for creating the DID on behalf of the user. The "creator" field may be used as a record of an entity authenticating the identity of the owner of the DID or endorsing the owner of the DID. Then, in step 1128, the user agent 411 may generate one or more blockchain transactions for storing the DID document to the blockchain 330. The user agent 411 may also generate one or more hash values for the blockchain transaction.

In some embodiments, for one or more blockchain transactions to be performed by one or more nodes of blockchain 330, they need to be signed using a private key associated with the DID. The user agent 411 may obtain such a digital signature from the KMS 323. In step 1130, the user agent 411 may send a request to the KMS 323 to sign the blockchain transaction using the private key of the encryption key pair associated with the DID. The request may include a hash value of the transaction and a public key associated with the DID. KMS 323 may create a digital signature of the transaction. In some embodiments, the digital signature may be generated in a TEE associated with KMS 323. KMS 323 may identify an encrypted private key associated with the public key and feed the encrypted private key to the TEE. The encrypted private key may be decrypted in the TEE and used to generate a digital signature of the transaction. The digital signature may then be fed back to KMS 323. In step 1132, the user agent 411 may receive a signed version of the blockchain transaction from the KMS.

In step 1134, the user agent 411 may send the DID document along with the signed blockchain transaction to the parser 322 for transmission to the blockchain system. At step 1136, the parser 322 may send the one or more transactions to the blockchain system (e.g., one or more blockchain nodes, cloud 324). The transaction may invoke a blockchain contract 331 for managing DID and DID documents on the blockchain 330. In step 1138, the parser 322 may obtain information from the blockchain 330 indicating that the DID document has been successfully stored. In step 1140, the parser 322 may forward the acknowledgement to the user agent 411.

After the DID and its corresponding DID document have been created, the user agent 411 may update the database 416 to store the mapping relationship between: the DID, the user's account identification, the user's proof of identity authentication, the user's service ID, the public key associated with the DID, the key alias associated with the user or proof of identity authentication, other suitable information, or any combination thereof. In some embodiments, the mapping relationship may be stored in encrypted form. To store the mapping, the user agent 411 may calculate a hash value for a combination of the DID and one or more of the other identifying information. In some embodiments, such hash values may be stored as part of the DID document. The stored mapping may allow the user agent 411 to identify the DID based on information received from the client system 310. In some embodiments, the user agent 411 may receive a request associated with the obtained DID, where the request includes an account identification, and then identify the obtained DID based on a mapping relationship between the account identification and the obtained DID. In other embodiments, the user agent 411 may receive a request for proof of identity, where the request includes a DID, and then locate the proof of identity based on a mapping between the proof of identity and the DID. In some embodiments, the user agent 411 may store a recovery key for recovering a private key corresponding to the DID associated with the identification information of the user. In this way, the user agent 411 may allow the user to control the DID using the recovery key. Then, the user agent 411 may transmit information associated with the DID to the server 311 in step 1144, and the server 311 may transmit a notification to the user to notify the user of successful creation of the DID in step 1146.

Fig. 12 illustrates a method for using proxy service authentication to de-center an identification, in accordance with some embodiments. The operations of the methods presented below are intended to be illustrative. Depending on the implementation, the method may include additional, fewer, or alternative steps performed in various orders or in parallel. In some embodiments, one party (e.g., a verifier) may desire to authenticate that the other party (e.g., the purported owner of the DID) is the true owner of the DID. The authentication process may be facilitated by a proxy service 321 that is available to both parties.

In some embodiments, at step 1202, verifier 532 may obtain the DID provided by the purported owner. At step 1204, verifier 532 may send a request to proxy service API 410 to create the DID authentication challenge. The request may include the DID to be authenticated and the network address (e.g., URL) to which the response to the challenge is to be sent. The network address may be accessible to verifier 532. At step 1206, the request may be forwarded from the proxy service API 410 to a verifier agent 413 configured to perform operations related to authentication of the DID. At step 1208, the verifier agent 413 may send a query to the parser 322 for the DID document associated with the DID to be authenticated. At step 1210, the parser 322 may formulate a transaction that invokes the blockchain contract 331 for managing DID and send the transaction to one or more blockchain nodes associated with the blockchain 330 for execution. As a result, the parser 322 may obtain a DID document corresponding to the DID in step 1212 and forward it to the verifier agent 413 in step 1214. At step 1216, the verifier agent 413 may create a DID authentication challenge based on the obtained DID document. In some embodiments, the DID authentication challenge may include ciphertext created by encrypting the original text using a public key associated with the DID recorded in the DID document. The challenge may also include a network address associated with the verifier to which the response is to be sent. In step 1218, the verifier agent 413 may obtain information associated with the authentication service endpoint of the DID from the DID document. At step 1220, verifier agent 413 may store an identification of the challenge in memory using a key-value structure (key-value structure), the identification of the challenge being related to information associated with the challenge. For example, verifier agent 413 may store a challenge ID associated with the challenge associated with the DID to be authenticated, plaintext for creating ciphertext, and a network address for sending a response to the challenge. At step 1222, verifier agent 413 may send the challenge to the DID authentication service associated with the DID based on the information from the DID document.

In some embodiments, after obtaining the DID authentication challenge from verifier agent 413, the DID authentication service may obtain consent to the response to such challenge from the owner of the DID at step 1224. In step 1226, if the owner provides consent or permission for identity authentication, the DID authentication service may send a request for a response to the DID authentication challenge to the proxy service API 410 associated with the user agent 411. In step 1228, the proxy service API 410 may call the corresponding function of the user agent 411 to create a response to the challenge. The response to the challenge may require that the plaintext used to create the ciphertext contained in the challenge be recovered using a private key associated with the DID to be authenticated. In step 1230, the user agent 411 may send the ciphertext from the challenge to the KMS 323 for decryption along with the identification information associated with the ID, as identified by the KMS 323. KMS 323 may store a plurality of public-private key pairs associated with identification information of an account or a DID corresponding to the key pair. Based on the identification information received from the user agent 411, the KMS 323 can identify a public-private key pair associated with the DID. In some embodiments, KMS 323 may store a public key and an encrypted version of the private key. It may send the encrypted private key to the TEE associated with KMS 323 for decryption. The ciphertext in the TEE may then be decrypted using the private key. In step 1232, the user agent 411 may obtain decrypted plaintext from the KMS 323.

In step 1234, the user agent 411 may generate a response to the challenge using plaintext and send the response back to the DID authentication service. The response may include the challenge identity contained in the original challenge. In step 1236, the did authentication service may send a response to the network address provided by verifier 532. The verifier 532 may then forward the response to the verifier agent 413 for examination, step 1238. At step 1240, verifier agent 413 may first compare the challenge identification in the response to one or more challenge identifications stored in memory 415 to identify information associated with the challenge corresponding to the response. The verifier agent 413 may then determine whether the purported owner of the DID is the actual owner at step 1242. In some embodiments, the verifier agent may determine whether the plaintext contained in the response is the same as the plaintext used to create the ciphertext in the challenge. If so, the verifier agent 413 may determine that the authentication was successful. At step 1244, the verifier agent 413 may send a confirmation message to the verifier, which may forward the confirmation message to the owner of the DID at step 1246.

FIG. 13 illustrates a method for issuing verifiable claims using proxy services, in accordance with some embodiments. The operations of the methods presented below are intended to be illustrative. Depending on the implementation, the method may include additional, fewer, or alternative steps performed in various orders or in parallel. In some embodiments, a first entity (e.g., a publisher) may desire to publish a VC for a second entity (e.g., a user) to prove facts about the second entity. The process of publishing VCs may be facilitated by proxy services 321 available to the entity.

In some embodiments, at step 1302, proxy service API 410 may receive a request from publisher 531 to create an unsigned VC for a DID associated with the user. Proxy service API 410 may call publisher agent 412 to perform operations to generate a new VC at step 1304. In step 1306, publisher agent 412 may create a VC based on the request received from publisher 531. The VC may include the message contained in the request. In some embodiments, the VC may include an encrypted version of the message for confidentiality reasons. The message may include a statement or statement about the user, or other suitable information or data that may be transmitted to a party having access to the VC. In some embodiments, the VC may include claims corresponding to identity authentication (e.g., real name authentication, true person authentication) of the user. The request may include the user's DID. Publisher agent 412 may directly create VCs based on DID. Optionally, the request may include an account identification associated with the user (e.g., a user account with the entity that issued the VC). In this case, the publisher agent 412 may obtain the account identification associated with the user from the request and identify the DID based on the mapping relationship between the pre-stored account identification and the DID. Publisher agent 412 may then create an unsigned VC based on the identified DID. Publisher agent 412 may also calculate a hash value of the content of the unsigned VC.

In some embodiments, the publisher agent 412 may obtain a digital signature associated with the publisher in response to receiving the request. In some embodiments, the digital signature may be obtained from KMS 323. At step 1308, the publisher agent 412 may determine a key alias associated with the publisher 531. At step 1310, publisher agent 412 may send a request to KMS 323 for a digital signature for a VC associated with publisher 531. The request may include a key alias that may be used to identify an encryption key associated with the issuer 531. The request may also include the hash value of the unsigned VC created by publisher agent 412. KMS 323 may store a plurality of public-private key pairs associated with a key alias of an entity or user. Based on the key alias received from publisher agent 412, KMS 323 can identify a public key-private key pair associated with publisher 531. In some embodiments, KMS 323 may store a public key and an encrypted version of the private key. It may send the encrypted private key to the TEE associated with KMS 323 for decryption. The private key may then be used to create a digital signature of the publisher for the VC. The digital signature may be created by encrypting the hash value of the unsigned VC using the private key. At step 1312, the digital signature may be sent back to the publisher agent 412. Publisher agent 412 may then combine the unsigned VCs with the digital signature to form signed VCs at step 1314. In this way, a signed VC is generated based on the request and digital signature received from the publisher 531.

In some embodiments, publisher agent 412 may upload the VC to a service endpoint associated with the DID of the user or the holder of the VC. Publisher agent 412 may identify a service endpoint based on the DID document associated with the DID. At step 1316, publisher agent 412 may send a query to parser 322 for a DID document associated with the DID to which the VC was published. At step 1318, the parser 322 may formulate a transaction that invokes the blockchain contract 331 for managing DID and send the transaction to one or more blockchain nodes associated with the blockchain 330 for execution. The transaction may include information associated with the DID and may be used to retrieve a DID document corresponding to the DID. As a result, the parser 322 may obtain a DID document corresponding to the DID in step 1320 and forward it to the SDK 312 in step 1322. Based on the DID document, publisher agent 412 may obtain information (e.g., network address) associated with the service endpoint (e.g., VC repository 414) of the DID from the DID document. At step 1324, publisher agent 412 may upload the VC to the service endpoint.

In some embodiments, publisher agent 412 may store the state of the VC. The state of the VC may be stored in the blockchain 330. In some embodiments, a service endpoint associated with the publisher 531 of a VC may use the blockchain 330. At step 1326, publisher agent 412 may send the state of the VC (e.g., valid, invalid) and the hash value of the VC to parser 322 for storage in blockchain 330. At step 1328, parser 322 may generate and send a blockchain transaction to add information associated with the VC to the blockchain node of blockchain 330 associated with the service endpoint. The information may include the state of the VC and the hash value. In some embodiments, the blockchain transaction may invoke a blockchain contract 331 for managing VCs. After sending the transaction to the blockchain node, parser 322 may determine that the hash value and state of the VC have been successfully stored at step 1330, and may send an acknowledgement to publisher agent 412 at step 1332. In some embodiments, the state of the VC may also be stored locally. At step 1334, publisher agent 412 may store the VCs and their states in database 416. Publisher agent 412 may receive the successfully stored acknowledgements at step 1336, send the acknowledgements to proxy service API 410 at step 1338, and then proxy service API 410 may send an acknowledgement to publisher 531 indicating that the VC has been successfully created at step 1340. The acknowledgement sent to the publisher may include the VC that has been created.

In some embodiments, the VC may be provided to a user or holder of the VC. At step 1342, publisher agent 412 may send the VC and/or the state of the VC to a proxy service API 410 associated with user agent 411 of the holder of the VC. At step 1344, proxy service API 410 may call user agent 411 to upload the VC. Here, user agent 411 may act as a service endpoint for the DID of the VC holder. The user agent 411 may be implemented on the same physical system as the publisher agent 412. At step 1346, user agent 411 may save the VC to database 416. After successful preservation of the VC, database 416 may return a successful acknowledgement to user agent 411 at step 1348. The user agent 411 may send an acknowledgement to the proxy service API 410 at step 1350 and the proxy service API 410 may forward the acknowledgement to the publisher agent 412 at step 1352.

FIG. 14 illustrates a method for verifying verifiable claims using a proxy service, in accordance with some embodiments. The operations of the methods presented below are intended to be illustrative. Depending on the implementation, the method may include additional, fewer, or alternative steps performed in various orders or in parallel. In some embodiments, the holder of the VC (or the principal of the VC) may expose to a first entity (e.g., a verifier) a VC published by a second entity (e.g., a publisher of the VC). The verifier may verify the VC by means of proxy service 321.

In some embodiments, at step 1402, proxy service API 410 may receive a request from verifier 532 to verify the VC. The VC may include a digital signature associated with a publisher of the VC. Proxy service API 410 may call a function of verifier agent 413 to verify the VC at step 1404. In some embodiments, verifier 532 may have obtained the VC directly from the holder of the VC. Alternatively, verifier 532 may only receive the account identification associated with the principal of the VC. Verifier 532 may obtain VC by: obtaining a DID associated with a body of the VC based on a mapping relationship between the pre-stored account identification and the DID, obtaining a DID document associated with the DID, obtaining information associated with a service endpoint for managing the VC from the DID document, and obtaining the VC from the service endpoint.

In some embodiments, verifier agent 413 may verify the state of the VC. Verifier agent 413 may obtain and verify the status using steps 1406a, 1408a, 1410a, and 1412a or steps 1406b, 1408b, 1410b, and 1412 b. In some embodiments, verifier agent 413 may obtain the state of the VC from a blockchain storing information associated with the plurality of VCs. At step 1406a, verifier agent 413 may send a query to parser 322 for the state of the VC. The query may include an identification of the VC. At step 1408a, parser 322 may create a blockchain transaction for retrieving the hash value and the state of the VC and send it to one or more blockchain nodes associated with blockchain 330. The blockchain transaction may include the DID of the principal of the VC and may invoke a blockchain contract 331 for managing the VC. At step 1410a, parser 322 may obtain the state of the VC and the hash value associated with the VC from blockchain 330. The parser 322 may then send the hash value and state to the verifier agent 413 for verification, step 1412 a. Verifier agent 413 may calculate the hash value by applying a hash function to the VC provided by the holder. Verifier agent 413 may authenticate the state of the received VC by comparing the hash value received from blockchain 330 to the calculated hash value. If they are the same, verifier agent 413 may determine that the received state does correspond to a VC. If the status indicates that the VC is valid, the verifier agent 413 may complete the verification step.

In some embodiments, verifier agent 413 may obtain the state of the VC from the service endpoint associated with the VC. In some embodiments, the service endpoint may correspond to a publisher agent 412 associated with a publisher. At step 1406b, verifier agent 413 may send a query to publisher agent 412 for the state of the VC. Publisher agent 412 may query database 416 for the state of the VC at step 1408b and obtain the state of the VC and the corresponding hash value at step 1410 b. At step 1412b, the publisher agent 412 may send the hash value and state to the verifier agent 413. Verifier agent 413 may authenticate the state and verify that the VC is valid in the manner described above.

In some embodiments, verifier agent 413 may determine that the VC was published by a publisher identified to the VC. Verifier agent 413 may obtain a public key associated with the publisher based on the VC. Verifier agent 413 may identify the publisher based on the identification in the VC. In some embodiments, the identification may include the DID of the publisher. The public key may be obtained from the blockchain 330 based on the publisher's DID. At step 1414, the verifier agent 413 may send a request to the resolver 322 for a public key associated with the publisher. The request may include the DID of the publisher. At step 1416, the parser 322 may create a blockchain transaction that invokes the blockchain contract 331 for retrieving public keys or DID documents based on the DID and send the blockchain transaction to the blockchain node of the blockchain 330. The parser 322 may obtain the public key (e.g., by retrieving from the DID document) at step 1418 and forward the public key to the verifier agent 413 at step 1420. Then, at step 1422, verifier agent 413 may verify the VC using the public key by determining that the digital signature was created based on the private key associated with the public key. In some embodiments, verifier agent 413 may verify one or more other facts about the VC. For example, verifier agent 413 may obtain the release date of the VC from the VC and verify the obtained release date based on a comparison between the obtained release date and the current date. As another example, verifier agent 413 may obtain the expiration date of the VC from the VC and verify that the VC has not expired based on the expiration date and the current date. If the verification of the VC is successful, the verifier agent may send an acknowledgement to the proxy service API 410 at step 1424. Proxy service API 410 may send a message to verifier 532 confirming that the VC is verified, step 1426.

FIG. 15 illustrates a flowchart of a method for creating a decentralised identity according to some embodiments. The method 1500 may be performed by an apparatus, device, or system for DID creation. The method 1500 may be performed by one or more components of the environments or systems shown in fig. 1-5, such as: one or more components of proxy service 321, one or more components of parser 322, or one or more components of cloud 324. Depending on the implementation, method 1500 may include additional, fewer, or alternative steps performed in various orders or in parallel.

Block 1510 includes receiving a request to obtain a de-centralized identification (DID), wherein the request includes an account identification. In some embodiments, receiving a request to obtain a DID includes receiving the request from a first entity on behalf of a second entity to create the DID for the second entity, wherein the account identification corresponds to the second entity. In some embodiments, the method further includes determining an existing DID associated with the first entity based on the request. In some embodiments, the method further comprises determining that the request includes proof of real-name authentication of the second entity. In some embodiments, the request includes an Application Programming Interface (API) message.

Block 1520 includes obtaining a public key of an encryption key pair in response to receiving the request. In some embodiments, obtaining the public key of the encryption key pair comprises: a request is sent to a Key Management System (KMS) to generate and store an encryption key pair and a public key of the encryption key pair is received from the KMS.

Block 1530 includes obtaining the DID based on the public key. In some embodiments, obtaining the DID includes generating a blockchain transaction for creating a blockchain account, wherein the obtained DID includes a blockchain address associated with the blockchain account. In some embodiments, obtaining the DID includes generating one or more blockchain transactions for creating the DID based on the public key and adding a DID document associated with the DID to the blockchain. In some embodiments, one or more blockchain transactions invoke one or more blockchain contracts associated with the blockchain. In some embodiments, obtaining the DID includes sending a request to the KMS to sign the blockchain transaction using a private key in an encryption key pair, and receiving a signed version of the blockchain transaction from the KMS, wherein the signed version of the blockchain transaction is generated in a Trusted Execution Environment (TEE).

In some embodiments, the DID document includes: one or more public keys associated with the obtained DID, authentication information associated with the obtained DID, authorization information associated with the obtained DID, delegation information associated with the obtained DID, one or more services associated with the obtained DID, one or more service endpoints associated with the obtained DID, and the DID of the creator of the obtained DID. In some embodiments, the DID document includes a mapping relationship between account identification and the obtained DID. In some embodiments, the mapping in the DID document is encrypted.

Block 1540 includes storing a mapping relationship between the account identification and the obtained DID. In some embodiments, the method further comprises: receiving a request associated with the obtained DID, wherein the request includes an account identification; and identifying the obtained DID based on a mapping relationship between the account identification and the obtained DID. In some embodiments, the method further comprises storing a recovery key associated with the obtained DID.

FIG. 16 illustrates a flow diagram of a method for issuing a verifiable claim, in accordance with some embodiments. Method 1600 may be performed by a device, apparatus, or system for VC distribution. Method 1600 may be performed by one or more components of the environments or systems shown in fig. 1-5, such as: one or more components of proxy service 321, one or more components of parser 322, or one or more components of cloud 324. Depending on the implementation, method 1600 may include additional, fewer, or alternative steps performed in various orders or in parallel.

Block 1610 includes receiving a request from a first entity to create a verifiable statement (VC) for a de-centralized identification (DID) associated with a second entity. In some embodiments, receiving a request to create a DID VC associated with the second entity comprises: an account identification associated with the second entity is obtained from the request and the DID is identified based on a pre-stored mapping between the account identification and the DID.

Block 1620 includes obtaining a digital signature associated with the first entity in response to receiving the request. In some embodiments, obtaining the digital signature associated with the first entity comprises: based on the received request, determining a key alias associated with the first entity, sending a request to a Key Management System (KMS) for a digital signature associated with the first entity, the request including the key alias, and receiving the digital signature from the KMS. In some embodiments, obtaining the digital signature associated with the first entity comprises: obtaining a message from the received request; creating an unsigned VC based at least in part on the message; determining a hash value of the unsigned VC; a request for a digital signature is sent to a Key Management System (KMS), the request including a hash value, and the digital signature is received from the KMS.

Block 1630 includes generating a VC based on the received request and the obtained digital signature. In some embodiments, generating the VC includes generating the VC based on an encrypted message included in the received request. In some embodiments, the generated VC includes a claim corresponding to the real-name authentication of the second entity.

In some embodiments, the method further comprises uploading the VC to a service endpoint associated with the DID. In some embodiments, uploading the VC to the service endpoint associated with the DID comprises: transmitting a blockchain transaction to a blockchain node to add to the blockchain, wherein the blockchain transaction includes information associated with the DID and is used to retrieve a DID document corresponding to the DID; obtaining a DID document from the blockchain; and determining a service endpoint associated with the DID based on the DID document. In some embodiments, the service endpoint is associated with a blockchain. In some embodiments, uploading the VC to the service endpoint includes sending a blockchain transaction to a blockchain node of a blockchain associated with the service endpoint to add information associated with the VC to the blockchain associated with the service endpoint. In some embodiments, the blockchain transaction invokes a blockchain contract for managing VCs.

In some embodiments, the method further comprises storing the generated VC and the state associated with the generated VC. In some embodiments, the method further includes sending, via an Application Programming Interface (API), the generated VC and the state associated with the generated VC to an online agent accessible to the second entity for storage. In some embodiments, the method further comprises sending a success message to the first entity, the success message comprising the generated VC.

FIG. 17 illustrates a flow chart of a method for verifying a verifiable claim, in accordance with some embodiments. Method 1700 may be performed by an apparatus, device, or system for VC authentication. Method 1700 may be performed by one or more components of the environments or systems shown in fig. 1-5, such as: one or more components of proxy service 321, one or more components of parser 322, or one or more components of cloud 324. Depending on the implementation, the method 1700 may include additional, fewer, or alternative steps performed in various orders or in parallel.

Block 1710 includes receiving a request from a first entity to verify a verifiable statement (VC) comprising a digital signature. Block 1720 includes obtaining a public key associated with the second entity based on the VC. In some embodiments, obtaining the public key associated with the second entity includes identifying the second entity based on the identification in the VC. In some embodiments, the identification in the VC is a de-centralized identification (DID); obtaining a public key associated with the second entity includes: sending a blockchain transaction including information associated with the DID to a blockchain link of the blockchain, wherein the blockchain transaction is used to retrieve a DID document corresponding to the DID; the DID document is obtained from the blockchain and the public key is retrieved from the DID document. In some embodiments, the blockchain transaction invokes a blockchain contract for managing the relationship between the DID and the DID document.

Block 1730 includes determining that the digital signature was created based on a private key associated with the public key. Block 1740 includes validating the VC based on the determination. In some embodiments, validating the VC comprises: the release date of the VC is obtained from the VC, and the obtained release date is verified based on a comparison between the obtained release date and the current date. In some embodiments, validating the VC comprises: an expiration date of the VC is obtained from the VC, and it is verified that the VC has not expired based on the expiration date and the current date.

In some embodiments, the method further comprises obtaining a state of the VC and determining that the state of the VC is valid. In some embodiments, obtaining the state of the VCs includes obtaining the state from a blockchain storing information associated with the plurality of VCs. In some embodiments, determining that the state of the VC is valid comprises: obtaining a first hash value associated with the VC and a state of the VC; determining a second hash value by applying a hash function to the VC; and authenticating the state of the VC by comparing the first hash value and the second hash value. In some embodiments, obtaining the first hash value associated with the VC and the state of the VC comprises: transmitting a blockchain transaction to a blockchain link of the blockchain for retrieving a first hash value and a state, the blockchain transaction comprising: DID associated with the bulk of VC.

In some embodiments, the method further comprises: receiving an account identification associated with a principal of the VC from a first entity; obtaining a DID document associated with the DID based on a mapping relation between the pre-stored account identifier and the DID; obtaining information related to a service endpoint for managing VCs from the DID document; and obtaining the VC from the service endpoint. In some embodiments, the method further comprises sending a message to the first entity confirming that the VC is authenticated.

FIG. 18 illustrates a block diagram of a computer system for creating a decentralised identity, in accordance with some embodiments. System 1800 may be an example of an implementation of one or more components of server system 320 in fig. 3 or one or more other components shown in fig. 1-5. The method 1500 may be implemented by the computer system 1800. Computer system 1800 may include one or more processors and one or more non-transitory computer-readable storage media (e.g., one or more memories) coupled to the one or more processors and configured with instructions executable by the one or more processors to cause a system or device (e.g., a processor) to perform the above-described methods, such as method 1500. The computer system 1800 may include various units/modules corresponding to the instructions (e.g., software instructions). In some embodiments, computer system 1800 may refer to a means for creating a DID. The apparatus may include: a receiving module 1810 for receiving a request to obtain a de-centralized identification (DID), wherein the request includes an account identification; and a first obtaining module 1820 for obtaining a public key of the encryption key pair in response to receiving the request; a second obtaining module 1830 for obtaining the DID based on the public key; and a storage module 1840 for storing a mapping relationship between the account identifier and the obtained DID.

FIG. 19 illustrates a block diagram of a computer system for issuing verifiable claims, in accordance with some embodiments. System 1900 may be an example of an implementation of one or more components of server system 320 in FIG. 3 or one or more other components shown in FIGS. 1-5. Method 1600 may be implemented by computer system 1900. Computer system 1900 may include one or more processors and one or more non-transitory computer-readable storage media (e.g., one or more memories) coupled to the one or more processors and configured with instructions executable by the one or more processors to cause the system or device (e.g., processor) to perform the above-described methods, such as method 1600. Computer system 1900 may include various units/modules corresponding to instructions (e.g., software instructions). In some embodiments, computer system 1900 may refer to a means for publishing a VC. The apparatus may include: a receiving module 1910 for receiving a request from a first entity to create a verifiable statement (VC) for a de-centralized identification (DID) associated with a second entity; an obtaining module 1920 for obtaining a digital signature associated with the first entity in response to receiving the request; and a generation module 1930 for generating a VC based on the received request and the obtained digital signature.

FIG. 20 illustrates a block diagram of a computer system for verifying a verifiable claim, in accordance with some embodiments. The system 2000 may be an example of an implementation of one or more components of the server system 320 in fig. 3 or one or more other components shown in fig. 1-5. Method 1700 may be implemented by computer system 2000. The computer system 2000 may include one or more processors and one or more non-transitory computer-readable storage media (e.g., one or more memories) coupled to the one or more processors and configured with instructions executable by the one or more processors to cause the system or device (e.g., processor) to perform the above-described methods, such as method 1700. The computer system 2000 may include various units/modules corresponding to instructions (e.g., software instructions). In some embodiments, computer system 2000 may refer to a means for authenticating a VC. The apparatus may include: a receiving module 2010 for receiving a request from a first entity to verify a verifiable statement (VC) comprising a digital signature; an obtaining module 2020 for obtaining a public key associated with the second entity based on the VC; a determining module 2030 for determining that the digital signature was created based on a private key associated with the public key; and a verification module 2040 for verifying the VC based on the determination.

The techniques described herein are implemented by one or more special purpose computing devices. The special purpose computing device may be a desktop computer system, a server computer system, a portable computer system, a handheld device, a network device, or any other device or combination of devices that contain hardwired and/or program logic to implement the techniques. The special purpose computing device may be implemented as a personal computer, laptop computer, cellular telephone, camera phone, smart phone, personal digital assistant, media player, navigation device, email device, game console, tablet computer, wearable device, or a combination thereof. Computing devices are typically controlled and coordinated by operating system software. Conventional operating systems control and schedule computer processes for execution, perform memory management, provide file systems, networks, I/O services, and provide user interface functions, such as a graphical user interface ("GUI"), and the like. The various systems, apparatuses, storage media, modules, and units described herein may be implemented in a special purpose computing device or one or more computing chips of one or more special purpose computing devices. In some embodiments, the instructions described herein may be implemented in a virtual machine on a special purpose computing device. The instructions, when executed, can cause a special purpose computing device to perform the various methods described herein. The virtual machine may include software, hardware, or a combination thereof.

FIG. 21 illustrates a block diagram of a computer system in which any of the embodiments described herein may be implemented. The system 2100 may be implemented in any of the environments or components of the systems shown in fig. 1-5. The software applications or services shown in fig. 1-5 may be implemented and operated on the system 2100. One or more of the example methods illustrated in fig. 6-17 may be performed by one or more embodiments of the computer system 2100.

Computer system 2100 may include a bus 2102 or other communication mechanism for communicating information, one or more hardware processors 2104 coupled with bus 2102 for processing information. The hardware processor 2104 may be, for example, one or more general purpose microprocessors.

Computer system 2100 may also include a main memory 2106, such as Random Access Memory (RAM), cache memory, and/or other dynamic storage device, coupled to bus 2102 for storing information and instructions that may be executed by processor 2104. Main memory 2106 also may be used for storing temporary variables or other intermediate information during execution of instructions to be executed by processor 2104. When stored in a storage medium accessible to the processor 2104, the instructions present the computer system 2100 as a special-purpose machine customized to perform the operations specified in the instructions. The computer system 2100 may also include a Read Only Memory (ROM) 2108 or other static storage device coupled to the bus 2102 for storing static information and instructions for the processor 2104. A storage device 2110, such as a magnetic disk, optical disk, or USB thumb drive (flash drive), may be provided and coupled to bus 2102 for storing information and instructions.

The computer system 2100 may implement the techniques described herein using custom hardwired logic, one or more ASICs or FPGAs, firmware, and/or program logic in conjunction with the computer system to make the computer system 2100 a special purpose machine, or to program the computer system 700 as a special purpose machine. According to one embodiment, the operations, methods, and processes described herein are performed by computer system 2100 in response to processor 2104 executing one or more sequences of one or more instructions contained in main memory 2106. Such instructions may be read into main memory 2106 from another storage medium, such as storage device 2110. Execution of the sequences of instructions contained in main memory 2106 may cause processor 2104 to perform the process steps described herein. In alternative embodiments, hard-wired circuitry may be used in place of or in combination with software instructions.

Main memory 2106, ROM 2108 and/or storage 2110 can include non-transitory storage media. The term "non-transitory medium" and similar terms used herein refer to media that store data and/or instructions that cause a machine to operate in a specific manner, excluding transitory signals. Such non-transitory media may include non-volatile media and/or volatile media. Non-volatile media includes, for example, optical or magnetic disks, such as storage device 2110. Volatile media includes dynamic memory, such as main memory 2106. Conventional forms of non-transitory media include, for example, a floppy disk, a flexible disk, hard disk, solid state drive, magnetic tape, or any other magnetic data storage medium, a CD-ROM, any other optical data storage medium, any physical medium with patterns of holes, a RAM, a PROM, and EPROM, a FLASH-EPROM, an NVRAM, any other memory chip or cartridge, and network versions thereof.

The computer system 2100 may also include a network interface 2118 coupled to the bus 2102. The network interface 2118 may provide a two-way data communication coupling to one or more network links that connect to one or more local networks. For example, network interface 2118 may be an Integrated Services Digital Network (ISDN) card, a cable modem, a satellite modem, or a modem to provide a data communication connection to a corresponding type of telephone line. As another example, the network interface 2118 may be a Local Area Network (LAN) card to provide a data communication connection to a compatible LAN (or WAN component to communicate with a WAN). Wireless links may also be implemented. In any such implementation, network interface 2118 may transmit and receive electrical, electromagnetic, or optical signals that carry digital data streams representing various types of information.

The computer system 2100 can send messages and receive data, including program code, through the network(s), network link and network interface 2118. In the Internet example, a server might transmit a requested code for an application program through the Internet, ISP, local network and network interface 2118.

The received code may be executed by processor 2104 as it is received, and/or stored in storage device 2110, or other non-volatile storage for later execution.

Each of the processes, methods, and algorithms described in the preceding sections may be embodied in and fully or partially automatically implemented by code modules executed by one or more computer systems or computer processors including computer hardware. The processes and algorithms may be partially or wholly implemented in dedicated circuitry.

The various features and processes described above may be used independently of each other or may be combined in various ways. All possible combinations and subcombinations are intended to fall within the scope herein. In addition, certain methods or processing blocks may be omitted in some embodiments. Nor is the method and processes described herein limited to any particular order, and blocks or states associated therewith may be performed in other orders as appropriate. For example, the described blocks or states may be performed in an order different than specifically disclosed, or multiple blocks or states may be combined in a single block or state. Examples of blocks or states may be performed serially, in parallel, or in some other manner. Blocks or states may be added to or removed from the disclosed embodiments. Examples of the systems and components described herein may be configured differently than described. For example, elements may be added, removed, or rearranged as compared to the disclosed embodiments.

Various operations of the methods described herein may be performed, at least in part, by one or more processors that are temporarily configured (e.g., via software) or permanently configured to perform the relevant operations. Whether temporarily configured or permanently configured, such a processor may constitute a processor-implemented engine for performing one or more of the operations or functions described herein.

Similarly, the methods described herein may be implemented, at least in part, by a processor, with the particular processor being an example of hardware. For example, at least some operations of the method may be performed by one or more processors or processor-implemented engines. In addition, the one or more processors may also be operable to support performance of related operations in a "cloud computing" environment, or as "software as a service" (SaaS) operations. For example, at least some of the operations may be performed by a set of computers (as examples of machines including processors), which may be accessed via a network (e.g., the internet) via one or more suitable interfaces (e.g., application Programming Interfaces (APIs)).

The performance of certain operations may be distributed among processors, not only residing in a single machine, but also deployed across multiple machines. In some embodiments, the processor or processor-implemented engine may be located in a single geographic location (e.g., within a home environment, an office environment, or a server farm). In other embodiments, the processor or processor-implemented engine may be distributed across multiple geographic locations.

Herein, multiple instances may implement a component, operation, or structure described as a single instance. Although individual operations of one or more methods are illustrated and described as separate operations, one or more of the separate operations may be performed concurrently and nothing requires that the operations be performed in the order illustrated. Structures and functions presented as separate components in a configuration may be implemented as a combined structure or component. Similarly, structures and functions presented as a single component may be implemented as separate components. These and other variations, modifications, additions, and improvements may fall within the scope of the subject matter herein.

Although an overview of the subject matter has been described with reference to particular embodiments, various modifications and changes may be made to these embodiments without departing from the broader scope of the embodiments herein. The detailed description is not to be taken in a limiting sense, and the scope of various embodiments is defined only by the appended claims, along with the full range of equivalents to which such claims are entitled. Furthermore, relative terms (such as "first," "second," "third," etc.) as used herein do not denote any order, height, or importance, but rather are used to distinguish one element from another. Furthermore, the terms "a," "an," and "a plurality" herein do not denote a limitation of quantity, but rather denote the presence of at least one of the referenced item.

Claims

1. A computer-implemented method for verifying a verifiable claim, comprising:

receiving a request from a first entity to verify a verifiable claim VC comprising a digital signature;

obtaining a public key associated with a second entity based on the VC;

determining that the digital signature is created based on a private key associated with the public key, the public key and the private key associated with the public key being generated by a key management system; the key management system comprises a trusted execution environment; the trusted execution environment is an isolation region on a main processor of the device that is separate from a main operating system; and

obtaining a state from a blockchain storing information associated with a plurality of VCs; and

obtaining a first hash value associated with the VC and the state of the VC;

determining a second hash value by applying a hash function to the VC; and

authenticating the state of the VC by comparing the first hash value with the second hash value;

based on the determining that the digital signature is created based on a private key associated with the public key and determining that the state of the VC is valid, the VC is verified.

2. The method of claim 1, wherein the obtaining the public key associated with the second entity comprises:

The second entity is identified based on the identification in the VC.

3. The method of claim 2, wherein the identification is a de-centralized identification DID and the obtaining the public key associated with the second entity comprises:

sending a blockchain transaction to a blockchain link of a blockchain that includes information associated with the DID, wherein the blockchain transaction is used to retrieve a DID document corresponding to the DID;

obtaining the DID document from the blockchain; and

and retrieving the public key from the DID document.

4. The method of claim 3, wherein the blockchain transaction invokes a blockchain contract for managing a relationship between DID and DID documents.

5. The method of claim 1, wherein the obtaining the first hash value associated with the VC and the state of the VC comprises:

a blockchain transaction is sent to a blockchain node of the blockchain for retrieving the first hash value and the state, the blockchain transaction including a DID associated with a principal of the VC.

6. The method of claim 5, further comprising:

retrieving, from the first entity, an account identification associated with the principal of the VC;

Obtaining a DID associated with the principal of the VC based on a mapping relationship between the pre-stored account identification and the DID;

obtaining a DID document associated with the DID;

obtaining information associated with a service endpoint for managing VCs from the DID document; and

the VC is obtained from the service endpoint.

7. The method of claim 1, further comprising:

and sending a message confirming that the VC is verified to the first entity.

8. The method of claim 1, wherein the validating the VC comprises:

obtaining the release date of the VC from the VC; and

the obtained release date is verified based on a comparison between the obtained release date and a current date.

9. The method of claim 1, wherein the validating the VC comprises:

obtaining an expiration date of the VC from the VC; and

verifying that the VC has not expired based on the expiration date and current date.

10. A system for verifying a verifiable claim, comprising:

one or more processors; and

one or more computer-readable memories coupled to the one or more processors and having instructions stored thereon, the instructions being executable by the one or more processors to perform the method of any of claims 1-9.

11. A non-transitory computer-readable storage medium configured with instructions executable by one or more processors to cause the one or more processors to perform the method of any of claims 1-9.

12. An apparatus for verifying a verifiable claim comprising a plurality of modules for performing the method of any one of claims 1-9.