PKI-based authentication of blockchain addresses

Verifying blockchain address and identity information through the public key infrastructure verification module solves the address verification problem in blockchain technology, reduces transaction complexity and error risks, and promotes the widespread adoption of blockchain technology.

CN118901221APending Publication Date: 2024-11-05PAYPAL INC
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN202380026754.1
Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Priority Date
2022-03-11
Filing Date
2023-03-08
Publication Date
2024-11-05

AI Technical Summary

Technical Problem

Existing blockchain technology lacks a method to directly verify blockchain addresses, especially for unskilled users or new users, which can easily lead to irreversible transaction errors, which may lead to incorrect transfer of digital assets to unanticipated accounts, especially when interacting with malicious websites. It is even more dangerous.

Method used

Using the certificate and signature mechanism in the public key infrastructure (PKI), the user's certificate and signature messages are verified through the verification module, and the corresponding relationship between blockchain address and identity information is established, providing a simpler and more robust address verification method. .

Benefits of technology

It effectively reduces errors and deceptive transactions in blockchain transactions, reduces the complexity of user operations, and allows even novice users to conduct transactions safely, enhancing trust and widespread adoption of blockchain technology.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN118901221A_ABST
    Figure CN118901221A_ABST
Patent Text Reader

Abstract

Techniques related to determining identity information of a user associated with a blockchain address are disclosed. An application of a first user may receive information indicating a blockchain address of a second user. The information includes or may be used to retrieve a certificate of the second user, the certificate being signed by a private key of a certificate authorizer (CA) and including identity information of the second user. The application of the first user may validate the certificate using the public key of the CA. The application of the first user may then cause the identity information of the second user to be included in a user interface presented to the first user. This information allows the first user to have more information about the user before starting an irreversible blockchain transaction with the second user.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] The present disclosure relates generally to blockchain and, more particularly, to authentication of destination addresses on a blockchain. Background Art

[0002] "Blockchain" refers to technology that facilitates the process of recording and sharing information. In particular, blockchain stores data in a way that makes it very difficult for malicious users to corrupt it. Blockchain is often used to store information for any number of applications, including financial transactions, protecting personal data, supply chain monitoring, and more.

[0003] As the name implies, a blockchain stores its information in a series of blocks or "blocks". Each block can include a hash of itself, time-stamped transactions, and the hash of the previous block. The hash of the previous block links the blocks together, which enables the blockchain to be created. The use of the hash of the previous block prevents the block from being altered or inserted between two blocks.

[0004] Blockchain is an implementation of distributed ledger technology in which multiple independent computer systems (or nodes) each have their own copy of the ledger that stores blockchain transactions. Each copy is considered a "peer" of the other copies. When a blockchain transaction causes a change to one copy of the ledger, the blockchain operates to cause the same change to occur in the other copies of the ledger.

[0005] Accounts on the blockchain are based on establishing a blockchain public-private key pair for the account holder. The blockchain key, which should only be known to the account holder, is used to sign transactions. Since the signature on the transaction can be verified using the account holder's blockchain public key, this action indicates to the rest of the blockchain system that the account holder has the authority to initiate transactions involving the corresponding account. Another account in a transaction can be specified using an address, which is typically a shorter version of the other account's blockchain public key. BRIEF DESCRIPTION OF THE DRAWINGS

[0006] Figure 1 is a block diagram of one embodiment of a system for authenticating a blockchain address.

[0007] Figure 2A is an example showing how to use signed messages and certificates to establish a correspondence between a blockchain address and the identity information of the entity that owns the blockchain address.

[0008] Figure 2B A registry-based embodiment for determining identity information corresponding to a blockchain address is shown.

[0009] Figure 3 is a block diagram illustrating one embodiment of a process for registering a blockchain address in a registry on a blockchain.

[0010] Figure 4A is a block diagram illustrating an example of a system for registering an address and a tag as a pair in a registry on a blockchain, according to some embodiments.

[0011] Figure 4B are examples illustrating different types of signed messages for storage in a blockchain registry in accordance with some embodiments.

[0012] Figure 4C is a diagram illustrating different examples of certificate information stored in a blockchain registry according to some embodiments.

[0013] Figure 4D is a schematic diagram showing one embodiment of a blockchain registry that reuses certificate information for multiple addresses.

[0014] Figure 5A is a block diagram of a verification module for verifying entity information associated with a blockchain transaction.

[0015] Figure 5B An example user interface providing a first user with identity information of a second user associated with a blockchain address is depicted.

[0016] Fig. 6A is a flow chart of an embodiment of a method for verifying identity information of a blockchain user.

[0017] Figure 6B is a flow chart of one embodiment of a method for registering a blockchain address in a blockchain registry.

[0018] Figure 6C is a flow chart of one embodiment of a method for performing a blockchain address lookup in a blockchain registry. DETAILED DESCRIPTION

[0019] Currently, common blockchain interactions can result from a first user interacting with a second user via a website. The first user may wish to conduct a transaction with the second user. The second user can then provide the first user with the second user's blockchain address. The address can be a long string in hexadecimal, for example, "0x0eb81892540747ec60f1389ec734a2c06b898ec8" (where "0x" indicates that the value is in hexadecimal). In some cases, the second user may need to copy the string from one application (e.g., a browser) to another application (e.g., a digital wallet application) for interacting with the blockchain. The first user can then use the address to initiate a blockchain transaction with the second user.

[0020] This paradigm is not without its drawbacks. Once executed, blockchain transactions are irreversible. That is, there is no mechanism by which a particular user can unilaterally undo a blockchain transaction. Of course, if a first user conducts a first blockchain transaction with a second user, the two users can agree to execute a second blockchain transaction that is the opposite of the first blockchain transaction. But these are two separate transactions, and the second transaction is dependent on the willingness and ability of both parties to undo the previous first transaction.

[0021] This general irreversibility of transactions can be problematic. Thus, if a particular user makes an error when copying a blockchain address into an application (e.g., by changing a number), the resulting transaction may result in a digital asset being irrevocably transferred to an unintended account. Further, consider a scenario in which a user is interacting with a compromised website that is unknown to the user. This may lead the user to believe that the interaction is with entity X, when in fact the interaction is with a different (malicious) entity Y. Thus, when a user receives a blockchain address from malicious entity Y, the user may initiate a blockchain transaction to that address without realizing that the address is for entity Y and not the intended entity X.

[0022] The inventors have recognized that the current state of blockchain technology does not provide a direct means for verifying a recipient's blockchain address, particularly for unskilled users or users who are new to blockchain. Advanced blockchain users may be able to use previous blockchain transactions to determine information such as the frequency of transfers to a particular blockchain address. However, this approach is impractical for users who are not familiar with blockchain.

[0023] The current state of blockchain technology is that transactions occur on a blockchain address to blockchain address level. As mentioned above, this approach is well suited for early technology adopters. However, the inventors have recognized that if blockchain is to be more widely adopted, innovations are needed that simplify blockchain interactions for a more general audience. The present invention is directed to such innovations.

[0024] In particular, the present disclosure sets forth techniques for providing simpler and more robust verification of destination blockchain addresses. The disclosed approach relies on a public key infrastructure (PKI), which refers to the hardware, software, and associated policies and procedures that facilitate the creation, management, use, storage, and revocation of digital certificates and public keys. In other words, PKI is a catch-all term for everything used today to establish and manage public keys. Public keys are not only part of the encryption process, but also help authenticate the identities of communicating parties of a device. The present disclosure sets forth various embodiments in which PKI concepts are used to authenticate the identities of blockchain users.

[0025] Figure 1One embodiment of a system 100 for authenticating a blockchain address is shown. As shown, the system 100 includes a blockchain 110 and a user application 120. As described above, a blockchain is a type of distributed ledger system for recording and sharing information. As shown by the dotted lines connecting the blockchain 110 and the applications 120A-B, the blockchain 110 can be accessed by various types of applications.

[0026] The blockchain 110 may be any suitable type of blockchain, including a public or private blockchain, either of which may be permissioned, permissionless, hybrid, etc. The blockchain 110 may also be a consortium or federated blockchain. The blockchain 110 may be used for any number of applications, including asset transfer, monitoring supply chains, digital IDs, digital voting, compliance, copyright / royalty protection, medical record keeping, managing legal documents such as wills, managing Internet of Things (IoT) devices, and tracking real items such as food, prescription drugs, hazardous materials, etc.

[0027] On the other hand, application 120 is any type of application that user S (indicated by reference numeral 102S, associated with application 120B) and user T (indicated by reference numeral 102T, associated with application 120A) use to communicate with each other. For example, application 120B may constitute a web server for user S that sends communication 115 to application 120A, and application 120A may constitute a web browser for user T. In another embodiment, applications 120A-B may also constitute an email program. Application 120 may also be an application that allows interaction with blockchain 110. Thus, application 120 may be a web browser, a block explorer application (an application that can show details of past blockchain transactions), a digital wallet, or any other suitable type of blockchain interface. It should be noted that in a particular scenario, applications 120A and 120B do not need to be the same type of application.

[0028] As shown, user T's application 120A receives communication 115 from user S's application 120B, where communication 115 includes information indicating the blockchain address of user S. Figure 2B As described, the communication 115 may include a blockchain address, which the application of user T then uses to retrieve from the blockchain registry 1) the certificate information of user S and 2) the message signed by user S. In short, the communication between user S and user T includes or can be used to retrieve the certificate information of user S and the message signed by user S.

[0029] As used herein, "certificate information" of user S refers to a certificate of user S issued by a certificate authority or information that can be used to access the certificate. The certificate may include identity information of user S (e.g., name, website, address of user S) and be signed by a certificate authority (CA). The certificate may also include a public key of user S for obtaining S's certificate. On the other hand, a signed message may indicate that user S is the owner of a specific blockchain address and may also include the public key of user S. It should be noted that the public key (and the corresponding private key) included in the certificate and the signed message is different from the public key-private key pair used to interact with blockchain 110. The former public key-private key pair may be referred to as a "PKI key pair", while the latter public key-private key pair may be referred to as a "blockchain key pair".

[0030] The authentication module 125 may be a part of the application 120A or different from the application 120A, such as Figure 1 As shown by the dotted lines in FIG. 1 . Submodules 125A-B are respectively used to verify the signed message and certificate of user S. Submodule 125A can use the public key of user S (included in the certificate) to verify that the signed message is in fact signed by user S. Similarly, submodule 125B can use the public key of the CA that signed the certificate to verify the signature on the certificate.

[0031] Thus, the verification module 125 can confirm that user S's certificate (which may include S's identity information) is authentic and that anyone who controls user S's identity recognizes S's claim that he is the owner of a particular address on the blockchain. Furthermore, if both the certificate and the signed message include user S's public key, this establishes a link between the certificate's identity information and the blockchain address of the signed message. (In other words, if user S's certificate identifies that identity information K is bound to a particular public key, and user S's signed message identifies that blockchain address X is bound to the same public key, this links identity information K to blockchain address X.)

[0032] Once both the certificate of user S and the signed message are verified by module 125, user S's identity information 128 may be provided to user T. Identity information 128 (which may include user S's name, website, etc.) may be provided, for example, via a user interface generated for user T by verification module 125. In one implementation, user S's long blockchain address may be replaced in the user interface by, for example, user S's name. This action allows user T to confirm user S's identity before conducting a blockchain transaction.

[0033] This approach will advantageously reduce erroneous or fraudulent transactions on the blockchain, particularly since such transactions cannot be unilaterally reversible. This approach also does not require blockchain users to have advanced knowledge to conduct transactions. On the contrary, even novice blockchain users can utilize the authentication technology. Therefore, it is believed that this approach will therefore promote the wider adoption of blockchain technology. The technology also advantageously relies on a pre-existing public key infrastructure for establishing trust relationships. In fact, most browsers and operating systems have been set up to evaluate the validity of certificates issued by CAs.

[0034] Figure 2A It is shown how, in one embodiment, a blockchain address is connected to corresponding identity information using a certificate of user S and a message signed by user S. Example 200 shows the relationship between a signed message 250 and a certificate 240. The signed message 250 is signed by S's private key, which is part of a key pair including a public key 242 and is used by S to obtain the certificate 240. Therefore, the signature of the signed message 250 can be verified using the public key 242. On the other hand, the certificate 240 is signed by the private key of the certificate authority; the signature can be verified by the corresponding certificate authority public key.

[0035] In the described example, the signed message 250 includes the public key 242 of user S and an indication of ownership of blockchain address X. For example, the signed message 250 may include an assertion that "user S owns blockchain address X". The signed message 250 may also include the public key 242 of user S. Thus, the signed message 250 may establish a correspondence between S's public key 242 and S's proof of ownership of blockchain address X.

[0036] As shown, the certificate 240 also includes a public key 242 and additionally includes the identity information 128 of the user S. As will be described, the identity information 128 can be verified by the certificate authority during the issuance of the certificate 240. Therefore, the certificate 240 can establish a correspondence between S's public key 242 and S's identity information 128. (It should be noted that in some embodiments, the identity information 128 can also be present in the signed message 250.)

[0037] Therefore, the signed message 250 links the ownership of S's blockchain address X to the public key 242, and the certificate 240 links S's identity information 128 to the public key 242. Since the public key 242 exists in both the signed message 250 and the certificate 240, these two pieces of information can be used to establish a correspondence between the blockchain address X and the identity information 128. In other words, if the verification module 125 can verify the signatures of both the signed message 250 and the certificate 240, it can be determined that the blockchain address X corresponds to the identity information 128. Therefore, in addition to the blockchain address X, or instead of the blockchain address X, the identity information 128 can be provided to the user T.

[0038] In other embodiments, different types of information may be used by the verification module 125 to determine the identity information 128 of the blockchain address X.

[0039] Figure 2B is a method for blockchain address authentication (which belongs to Figure 1 10. As shown, computer system 260 includes registry 255. In one embodiment, registry 255 may be implemented as part of blockchain 110 (e.g., as a smart contract). For a given blockchain address, registry 255 stores registration information 258, which may include signed messages and certificate information. As shown, registry 255 stores registration information 258 for blockchain address X (as shown by reference numeral 254). As will be seen in reference to Figure 3 As described, the registration information 258 has previously been written to the registry 255 by the user S using the registration application programming interface (API) of the registry 255 .

[0040] When the application 120A or the verification module 125 receives the blockchain address X, the lookup API of the registry 255 may be called. As shown, the application 120A or the verification module 125 may pass the blockchain address X to the registry 255 as part of the certificate lookup 266. The registry 255 then returns a certificate lookup response 268, which in one implementation may return the registration information 258, such as the signed message 250 and the certificate 240. If the blockchain address X is not stored in the registry 255, then in some embodiments, the certificate lookup response may return an "error / null" indication.

[0041] As previously mentioned, applications 120A-B may be any application associated with user T and user S, respectively. For example, application 120B may be code executed on a website of user S, while application 120A is a browser. Verification module 125 may be a part of application 120A or a separate application, such as Figure 2B As shown in the module 125 represented by the dotted line.

[0042] It should be noted that in some embodiments, more than one certificate may be provided as part of the certificate information within the registration information 258. For example, certificate 240 may be an end-user certificate issued by a leaf certificate authority. The leaf certificate authority has a leaf private key and a leaf public key (e.g., CA public key 246). The leaf certificate authority may thus have a certificate issued by an intermediate certificate authority. The leaf certificate may include a leaf public key and be signed using the private key of the intermediate certificate authority. In addition, the intermediate certificate authority may have a certificate issued by a root certificate authority. In this case, the intermediate certificate may include an intermediate public key and be signed using the private key of the root certificate authority. Therefore, the certificate information within the registration information 258 may include a certificate chain, and the certificate verification module 125B may store multiple CA public keys to verify each certificate in the chain.

[0043] In some embodiments, as part of the certificate lookup response 268 , the application 120A / verification module 125 may receive the signed message 250 and S's certificate 240 or information that can be used to retrieve S's certificate 240 .

[0044] As described above, the signed message 250 may establish a correspondence between S's public key 242 and S's blockchain address X. The signed message 250 includes a signature 252 made by S's private key; the signature 252 may be verified by the signature verification module 125A using S's public key 242. Similarly, the certificate 240 may establish a correspondence between S's public key 242 and S's identity information 128. The certificate 240 includes a signature 244 made by the private key of the certificate authority. The certificate verification module 125B may verify the CA signature 244 using (one or more) CA public keys 246. Therefore, if the signature verification module 125A and the certificate verification module 125B verify the signed message 250 and the certificate 240, respectively, the identity information 128 may be provided to the user T instead of or in addition to the blockchain address X.

[0045] Figure 2B The method has a simple interface between user S and user T, because only the blockchain address needs to be passed between user S and user T to authenticate blockchain address X. As already described, in some embodiments, the registry 255 can be implemented with two APIs: a registration API and a certificate lookup API. Figure 3 One embodiment of a registration process is described.

[0046] Figure 3 is a block diagram 300 illustrating the steps involved in one embodiment of a registration process for a particular blockchain address X. A registry 255, a user S (denoted by reference numeral 102S), and a certificate authority 330 are depicted.

[0047] As described above, the inventors propose to utilize PKI resources to authenticate blockchain addresses. The first step in the process is for user S to obtain a certificate from a certificate authority 330. Certificate authorities such as 330 have their own public key-private key pairs, which they use to sign certificates. In order to obtain a certificate, user S submits a certificate signing request (CSR) 335 to the certificate authority 330. The CSR 335 may include a certificate that includes S's public key 242 and user S's identity information 128. After verifying the CSR 335, the certificate authority 330 will sign the certificate in the CSR 335 with its private key and return the signed certificate to user S as the certificate 240.

[0048] Once user S has obtained the certificate 240, user S may proceed to register one or more addresses with the blockchain 110. Registration may be performed by using a registration request 310 made via a registration API of the registry 255. In general, the registration request 310 includes the address to be registered and registration information 258, which will be stored in a location within the registry 255 corresponding to the address being registered. However, before the registration information 258 is stored in the registry 255, ownership verification 320 is performed to ensure that the request 310 is from an entity that owns the address for which registration is being attempted. One means of performing ownership verification 320 is by verifying a signature of the registration request 310 or a signature included within the registration request 310. The blockchain 110 stores S's blockchain public key associated with S's blockchain account. Therefore, if some or all of the request 310 is signed using S's blockchain private key, the registry 255 may verify the signature using S's blockchain public key. (Again, S's blockchain public and private keys are typically different from the public and private keys used to obtain certificate 240.) For example, S's blockchain private key can be used to sign the entire request 310. The signature can be verified using S's blockchain public key as part of ownership verification 320. (It should be noted that registering an address does not prove that the address actually belongs to the entity written in the registration information. Instead, registering an address only proves that the registering entity controls the address in question.) Once S's ownership is verified, registration information 258 is stored in registry 255. For example, registration information 258 may include signed message 250 and certificate information such as certificate 240. Subsequently, the registration information 258 may be stored as described in reference to the registration information 255. Figure 2B Retrieve registration information as described.

[0049] In some embodiments, verification of the contents of the registration information 258 is not performed by the registration table 255. Figure 5AAs described, for example, verification module 125 can perform such a check. However, in other embodiments, the check can be performed by registry 255. Thus, registry 255 can verify that signed message 250 is directed to the same address being registered. Thus, if address X is being registered and signed message 250 asserts that "S owns address Y", a registration error may result. Similarly, registry 255 can determine whether the entity identified in signed message 250 matches the entity identified in certificate 240.

[0050] In general, using the disclosed techniques, if the application indicates that address X belongs to party S, then the indication is true unless one of the following caveats is true: (1) the PKI system is compromised, (2) S is compromised, or (3) the owner of X is compromised. Consider the case where the certificate is registered by party P but not by S. If P is able to create a valid certificate associating X with S, then this means that condition (1) or (2) has occurred. Similarly, if P is able to register address X, this means that condition (3) has occurred.

[0051] Reference now FIG. 4A to FIG. 4D Various implementations of the registry table 255 are described.

[0052] Some blockchains support (or require) "memos" or "tags". For example, some blockchains may use centralized addresses, and a separate memo / tag field is used to specify the transaction recipient. Alternatively, the memo / tag field may be used for the recipient to be able to identify the sender. In either case, the registry 255 may allow the registration request 310 to include not only the address, but also a separate tag. (In addition to the blockchain address, the term "tag" is used to describe an additional field. In some implementations, this field can be used to identify the sender or recipient. The term "tag" is intended to encompass the term "memo" or any other equivalent term.)

[0053] Figure 4A An embodiment is shown in which the registry 255 supports tags. Thus, the registration request 310 may contain not only an address, but also a second optional component. This allows an application to register a particular blockchain address multiple times with different identifying information. For example, an "omni-wallet" may use a single blockchain address X, but use different tags for each user (e.g., M1, M2) to manage their deposits.

[0054] The registry 255 verifies the registration request of the form <address, tag> described above and registers the information in the registration request (address, tag, registration information) in a specific registry record. Once the information is stored in the registry 255, the requesting entity can request a certificate lookup 266 by providing <address, tag> to the registry 255. In one embodiment, the registry 255 first checks whether the combination <address, tag> is registered, and if not, checks whether only the address is registered. If any combination is found to be registered, the stored registration information is returned to the requesting entity.

[0055] Figure 4B Different examples of signed messages that can be stored as registration information in the registry 255 are described. In various embodiments, these signed messages can be formatted (e.g., using javascript object notation (JSON), etc.) or unformatted. Signed message 250A is signed with signature 252, which is made by S's private key. Herein, message 450A includes information 422 indicating that address X belongs to S and S's public key 242. However, signed message 450B can include additional information, particularly S's name 424 and S's website 426. Many different types of additional information can be included in a signed message, for example, the recipient's storage address.

[0056] Figure 4C It is shown that the certificate in the registry 255 can be replaced with a uniform resource locator (URL) protected using Hypertext Transfer Protocol Security (HTTPS). In example 440A, the registration information includes a signed message and a certificate (or certificate chain). In example 440B, the registration information includes a signed message and a URL.

[0057] Then, in example 440B, the user has registered a mapping of address 'X' to a URL (e.g., addr X = URL U) in registry 255. An application wishing to verify address X will call the certificate lookup API of registry 255 as previously described. The stored URL (e.g., https: / / www.foo.com) will be returned as part of response 268 and will therefore be available to the application. The application can then extract the URL using HTTPS. The website hosting the URL will respond with a certificate issued and signed by the CA that includes S's public key. The browser can verify the CA's signature using its public key. The identity information in the certificate can then be provided to user T as described above.

[0058] When a URL is protected by HTTPS, in some embodiments, extraction of the URL can return all the details included in the message given the address (e.g., a JSON formatted message including the details "Company: foo, Address: X, and Purpose: Payment for a Book"). In such embodiments, when the HTTPS certificate is verified as part of the URL extraction, appropriate security is still present.

[0059] Using this approach, certificates can be updated without modifying the information stored in the registry 255. URLs can also be much shorter than certificates (thus saving space). However, in this approach, a network server needs to be established to host the content of any URL stored in the registry 255.

[0060] In some cases, storing the on-chain information in the registry 255 may be expensive. Figure 4D An embodiment of a registry 255 is depicted in which certificate information can be reused for several addresses. As shown in example 460, the registry 255 includes address 254A, which stores registration information including a signed message and a certificate. As explained, the signed message can specify that "account X belongs to S" includes S's public key and is signed by S's private key. At the same time, the certificate in address 254A can include S's public key and S's identity information.

[0061] Assume that S wishes to register a different address Y on the blockchain. The inventors have recognized that the same certificate information in 254A need not be stored in address 254B (the registry location for address Y). Therefore, the registration information in 254B may include a reference (e.g., a link) to address 254A or a certificate within address 254A. This method prevents users from having to store two copies of their certificate information in registry 255. This method is also applicable to users who register the same address to multiple tags. Therefore, the combination <address, M2> may include a reference to a certificate stored in a previously stored combination <address, M1>, such as Figure 4A shown.

[0062] Figure 5A 1 is a block diagram of one embodiment of a verification module 125 for verifying information associated with a participant in a blockchain transaction. As shown, the verification module 125 may include a message verification submodule 510, a certificate verification submodule 520, and an identity information submodule 530. As described, the module 125 may be part of an application that receives blockchain address information from another entity, or it may be part of a separate application. Figure 1 In the context of, for example, the authentication module can be part of application 120A or different from application 120A.

[0063] As shown, verification module 125 receives signed message 250 and certificate 240. (Alternatively, module 125 may receive other certificate information, such as a URL that can be used to extract the certificate.) The certificate may be directly obtained from registry 255 (e.g., Figure 2B Receive this information.

[0064] In the depicted embodiment, the verification module 125 performs two separate verification tasks, which can be performed simultaneously or in any order. In various embodiments, the message verification submodule 510 can be executed to receive the signed message 250. The submodule 510 verifies the signature on the message using the user's public key (which can be included in the message itself). The results of the signature check can then be sent to the identity information submodule 530, potentially along with any identity information included in the signed message 250.

[0065] In some embodiments, the message verification submodule 510 may also be executed to check the content of the signed message 250. Assume that in response to a registry lookup for address X, the resulting signed message 250 states "S owns address Y" or "R owns address Y." In such an instance, the submodule 510 may fail authentication for blockchain address X, and the corresponding message is presented to user T. In other words, the submodule 510 may check to ensure that the content of the signed message 250 corresponds to the address for which the registry lookup was performed.

[0066] On the other hand, the certificate verification submodule 520 can be executed to receive the certificate 240 or information that can be used to retrieve the certificate 240. As discussed, the certificate 240 has been issued by a CA and signed by the CA's private key. Therefore, the submodule 520 can verify the signature on the certificate using the stored CA public key 246. The submodule 520 can then send the result of the signature verification along with any identity information in the certificate 240 to the identity information submodule 530.

[0067] As described above, the identity verification submodule 530 may be executed to receive the signature verification results and identity information from submodules 510 and 520. If either verification check fails, the submodule 530 may provide failure information of the result to the user T. In some embodiments, the submodule 530 may further check that the entity asserted as the owner of the blockchain address in the signed message 250 matches the entity identified in the certificate 240. For example, if the signed message 250 states "R owns address X" and the certificate 240 identifies S, the submodule 530 may fail the authentication procedure. On the other hand, if the checks performed by the submodules 510 and 520 and any further checks performed by the submodule 530 pass (e.g., determining whether the entity identified in the signed message 250 matches the entity identified in the certificate 240), the submodule 530 may determine what identity information will be presented to the user T. For example, in some cases, the identity information may be in both the signed message 250 and the certificate 240. Submodule 530 may decide what information to present to user T, and may also perform other checks, such as determining the risk associated with a particular entity.

[0068] Reference now Figure 5B An example user interface that may be provided to a user T is described.

[0069] This disclosure describes various techniques for authenticating blockchain addresses. One motivation for these embodiments is to provide blockchain users with more visibility into the parties with whom they transact. Figure 5B Depicted are two examples of user interfaces that may be generated using identity information obtained using the approach described above.

[0070] User interface 570A is an example interface provided to a first user (e.g., user T) in response to a requested transaction with a second user (e.g., user S in the above figures). At this point, the first user takes steps to initiate a transaction with the second user, for example, by copying the second user's blockchain address to the first user's digital wallet in order to perform the transaction. Without the technology of the present disclosure, there is no easily callable mechanism for the first user to authenticate the second user's blockchain address. However, by applying the teachings of the present disclosure, the first user's application can use the blockchain address to determine the identity information of the second user.

[0071] At the point where user interface 570A is to be displayed, identity information 128 corresponding to the blockchain address of the second user is obtained. The identity information includes, for example, the name of the entity (Acme, Inc.) and the address and website of the entity. The identity information is displayed to the first user along with a final prompt to initiate a blockchain transaction. In this way, the first user can be given additional information in addition to the blockchain address before commencing an irreversible transaction. Example 570A also shows that additional types of information can also be given to the user, such as the number of blockchain transactions involving the address and the most recent blockchain transactions.

[0072] User interface 570B is similar to user interface 570A. However, in 570B, the blockchain address shown in 570A has been replaced with the name of the entity associated with the address. Interface 570B also shows that additional types of information stored by the application may also be provided to the first user, for example, a "risk score" for the transaction may be provided based on the information available to the application of the first user. For example, interface 570B indicates that transactions with Acme, Inc. are considered "safe."

[0073] As described above, the technology of the present disclosure can be applied to many different types of blockchain transactions. In addition to transactions involving cryptocurrencies, blockchain transactions can also involve other types of digital assets, such as non-fungible tokens (NFTs). The authenticity of a given NFT can be verified by applying the methods described herein to the address of the NFT creator. The NFT creator (e.g., Disney) can then use the disclosed method to sign the address that created its NFT to assure users that the NFT was created by it. When verifying the relevant signatures, applications that help interface with the NFT can show the user an indication of the NFT creator by displaying the NFT creator's identity information.

[0074] Fig. 6A 6 is a flow chart of one embodiment of a method 600 for verifying identity information of a user. The method 600 begins at 605, where an application of a first user receives a communication from a second user. The communication indicates an association between an address on a blockchain and the second user. The communication may include only a blockchain address (e.g., Figure 2B As described, the certificate information may include a certificate, a URL that can be used to retrieve the certificate, etc.

[0075] At 610, the certificate of the second user and the signed message are verified (e.g., by, for example, a verification module included in an application of the first user). The certificate including the public key of the second user may be verified using a public key of a certificate authority (CA). The signed message indicating an association between an address on the blockchain and the second user is verified using the public key of the second user as part of a key pair used to establish an account on the blockchain.

[0076] Finally, in 615, after verifying the certificate and the signed message, the identity information of the second user is provided to the first user. This information may be included in the certificate, for example. In some cases, the identity information may be provided to the first user in place of the blockchain address. In other implementations, both the identity information and the blockchain address may be presented to the user. In some embodiments, the identity information may be presented to the first user along with a risk score associated with the second user.

[0077] Reference above Figure 2B An example of utilizing a blockchain registry is described. In various embodiments, such a blockchain registry may utilize two APIs: one for an owner of a blockchain address to register an address with the registry, and another for an entity to perform a lookup of a blockchain address in the registry. Reference is now made to Figure 6B and Figure 6C Describes example methods that utilize these APIs.

[0078] Figure 6B is a flow chart of one embodiment of a method 630 for registering a blockchain address in a blockchain registry. Thus, the method 630 may be similar to the method 630 described above with reference to Figure 2B More specifically, when the registration API is called by an entity with an account (and thus an address) on blockchain 110, method 630 can be practiced by a software module within the registration table. In some embodiments, method 630 can be performed by blockchain 110 as part of a smart contract.

[0079] Method 630 begins at 635, where the server computer system receives a registration request for a blockchain address from a registration entity. As used herein, a "registration entity" refers to any party that invokes a registration process. In general, a registration request may include any type of information, particularly information that will subsequently allow another party to verify the identity of the registration entity. For example, a registration request may include certificate information and a signed message.

[0080] At 640, the system verifies the registration request. The purpose of 640 is to ensure that the registration request is made by the entity that owns the blockchain address being registered. Verification includes the system authenticating the ownership information of the registering entity. Generally speaking, proving ownership of a blockchain address is performed using a private key associated with the address. Therefore, verifying the registration request can be performed by verifying the signature in the registration request with a public key corresponding to the private key. In some embodiments, the registration request can constitute a package with multiple components, where the package is signed using the private key of the registering entity. In other embodiments, only a portion of the information in the registration request may be signed.

[0081] In 645, the server computer system stores the registration information included in the registration request in a first record of the blockchain registry in response to the registration request being verified. The registered information can be retrieved from the registry later and can be used to verify the certificate of the registering entity, and to verify the signed message using the public key of the registering entity; and to determine the identity information of the registering entity. The registered information may include certificate information and the signed message. As described above, the certificate information may include the certificate itself or a URL that can be extracted to retrieve the certificate. The certificate is signed by a certificate authority (CA) using its private key, and can therefore be verified using the CA public key.

[0082] Many modifications and additions to method 630 are contemplated and possible. For example, the server computer system may receive a certificate lookup from a requesting entity that may specify a blockchain address. The system may then return registration information stored in a registry in response to the certificate lookup. In some embodiments, the registration request may specify a tag in addition to the blockchain address, and in such instances, the certificate lookup may specify the tag. Thus, the server computer system may return registration information in response to determining that the blockchain address is registered in the registry in conjunction with the tag.

[0083] In some embodiments, verifying the registration request may include verifying the signature of the registration request using the blockchain public key of the registration entity (the signature is made using the blockchain private key of the registration entity). The registration information may include a certificate of the registration entity, the certificate including the public key of the registration entity. The registration information may also include a signed message specifying the name and website of the registration entity. In some embodiments, the registration information may include a URL. When extracted using the HTTPS protocol, the URL returns a certificate containing the public key of the registration entity.

[0084] In some examples, the server computer system may receive a second registration request. The registration request may specify a second blockchain address of the registering entity and may include a second signed message signed by the registering entity. The server computer system may verify the second registration request and may store the second signed message in a second record in the registry. The information stored in the second record may not include any certificates, but may include references to one or more certificates stored in the first record, thereby saving space in the registry.

[0085] Figure 6C is a flow diagram of one embodiment of a method 660 for calling an application programming interface (API) of a blockchain registry in order to retrieve information associated with a blockchain address.

[0086] Method 660 begins at 665, where an application executing on a computer system detects a request made by a first user to perform a blockchain transaction. The request includes information specifying a blockchain address of a second user on a blockchain. In some embodiments, the application may be a block explorer application.

[0087] In 670, the application calls an application programming interface (API) of the registry of the blockchain. In such an embodiment, the call includes passing the address received from the second user as a parameter of the API. Unlike the registration process that can only be performed by the owner of a specific blockchain address, method 660 can be performed by any entity.

[0088] In response to the information returned from the registry, the application identifies the registered information stored in the registry in a location corresponding to the address passed to the API in 675. The registered information may constitute any information stored in a registry location. For example, the registered information may include certificates and signed messages.

[0089] Next, in 680, the application verifies the registered information. This includes verifying the certificate of the second user using a certificate authority (CA) public key, wherein the certificate includes the public key of the second user. The verification of 680 also includes verifying the signed message of the second user using the public key of the second user. The signed message is signed by the private key of the second user and indicates the association between the blockchain address and the second user.

[0090] Finally, in 685, the application provides the second user's identity information to the first user in response to the registered information being verified. The identity information may be provided instead of or in addition to the blockchain address. For example, the identity information may be provided within a digital wallet. In some embodiments, the identity information may include one or both of the second user's name and website.

[0091] In addition to methods 600 , 630 , 660 , and variations thereof, non-transitory computer-readable media storing program instructions executable to implement such methods, as well as systems configured to implement such methods, are also contemplated.

[0092] The various techniques described herein may be performed by one or more computer programs. The term "program" is broadly interpreted to cover a sequence of instructions in a programming language that can be executed by a computing device. These programs may be written in any suitable computer language, including low-level languages ​​(e.g., assembly languages) and high-level languages ​​(e.g., Python). Programs may be written in compiled languages ​​(e.g., C or C++) or interpreted languages ​​(e.g., JavaScript).

[0093] Program instructions may be stored on a "computer-readable storage medium" or "computer-readable medium" so that a computer system executes the program instructions. In general, these phrases include any tangible or non-transitory storage device or storage medium. The terms "tangible" and "non-transitory" are intended to exclude propagating electromagnetic signals, but do not limit the type of storage medium. Thus, the phrases "computer-readable storage medium" or "computer-readable medium" are intended to cover types of storage devices that do not necessarily store information permanently (e.g., random access memory (RAM)). Thus, the term "non-transitory" is a limitation on the nature of the medium itself (i.e., the medium cannot be a signal), rather than a limitation on the data storage persistence of the medium (e.g., RAM versus ROM).

[0094] The phrases "computer-readable storage medium" and "computer-readable medium" are intended to refer to storage media within a computer system as well as removable media, such as a CD-ROM, a memory stick, or a portable hard drive, etc. The phrase covers any type of volatile memory within a computer system (including DRAM, DDR RAM, SRAM, EDO RAM, Rambus RAM, etc.), as well as non-volatile memory (e.g., magnetic media, such as a hard drive or optical storage device). The phrase is expressly intended to cover the memory of the server that causes the download of program instructions, the memory within any intermediate computer system involved in the download, and the memory of all destination computing devices. Furthermore, the phrase is intended to cover combinations of different types of memory.

[0095] In addition, the computer-readable medium or storage medium can be located in a first group of one or more computer systems in which the program is executed, and in a second group of one or more computer systems connected to the first group via a network. In the latter example, the second group of computer systems can provide program instructions to the first group of computer systems for execution. In short, the phrases "computer-readable storage medium" and "computer-readable medium" can include two or more media that can reside in different locations (e.g., in different computers connected via a network).

[0096] It should be noted that in some cases, program instructions can be stored on a storage medium, but cannot be executed in a specific computing environment. For example, a specific computing environment (e.g., a first computer system) may have a parameter set that forbids program instructions that are still resident on the storage medium of the first computer system. The record that these stored program instructions "can" be executed is intended to illustrate and cover this possibility. In other words, the program instructions stored on a computer-readable medium can be referred to as "executable" to perform a certain function, regardless of whether the current software configuration parameters allow this execution. Executability means that when the instruction is executed and if the instruction is executed, they execute the function in question.

[0097] The present disclosure relates to various software operations performed in the context of one or more computer systems. For example, applications 120A-B can each be executed on a respective computer system. Similarly, registry 255 can be implemented on a computer system associated with a blockchain. Each of these components is then implemented physically (i.e., on computer hardware).

[0098] In general, any service or function of the software development environment described in this disclosure can be performed by a host computing device, which is any computer system that can be connected to a computer network. A given host computing device can be configured according to any known configuration of computer hardware. A typical hardware configuration includes a processor subsystem, a memory, and one or more I / O devices coupled via an interconnect. A given host computing device can also be implemented as two or more computer systems operating together.

[0099] The processor subsystem of the host computing device may include one or more processors or processing units. In some embodiments of the host computing device, multiple instances of the processor subsystem may be coupled to a system interconnect. The processor subsystem (or each processor unit within the processor subsystem) may contain any of a variety of processor features known in the art, such as caches, hardware accelerators, etc.

[0100] The system memory of the host computing device can be used to store program instructions that can be executed by the processor subsystem to cause the host computing device to perform various operations described herein. The system memory can be implemented using different physical, non-transient memory media, such as hard disk storage devices, floppy disk storage devices, removable disk storage devices, flash memory, random access memory (RAM-SRAM, EDO RAM, SDRAM, DDR SDRAM, RAMBUS RAM, etc.), read-only memory (PROM, EEPROM, etc.), etc. The memory in the host computing device is not limited to the main storage device. On the contrary, the host computing device can also include other forms of storage devices, such as cache memory in the processor subsystem and auxiliary storage devices (e.g., hard disk drives, storage arrays, etc.) in I / O devices. In some embodiments, these other forms of storage devices can also store program instructions that can be executed by the processor subsystem.

[0101] The interconnection of the host computing device can connect the processor subsystem and memory to various I / O devices. One possible I / O interface is a bridge chip (e.g., a south bridge) from the front-end bus to one or more back-end buses. Examples of I / O devices include storage devices (hard drives, optical drives, removable flash drives, storage arrays, SANs or their associated controllers), network interface devices (e.g., to a computer network), or other devices (e.g., graphics, user interface devices).

[0102] The present disclosure includes references to "embodiments," which are non-limiting implementations of the disclosed concepts. References to "an embodiment," "one embodiment," "a specific embodiment," "some embodiments," "various embodiments," etc., do not necessarily refer to the same embodiment. A large number of possible embodiments are contemplated, including specific embodiments described in detail as well as modifications or substitutions that fall within the spirit or scope of the present disclosure. Not all embodiments necessarily exhibit any or all of the potential advantages described herein.

[0103] The present disclosure may discuss potential advantages that may result from the disclosed embodiments. Not all implementations of these embodiments will necessarily exhibit any or all potential advantages. Whether an advantage is achieved for a particular implementation depends on many factors, some of which are outside the scope of the present disclosure. In fact, there are multiple reasons why an implementation falling within the scope of the claims may not exhibit some or all of any of the disclosed advantages. For example, a particular implementation may include other circuits outside the scope of the present disclosure, which, in combination with one of the disclosed embodiments, negate or reduce one or more of the disclosed advantages. In addition, suboptimal design execution of a particular implementation (e.g., implementation techniques or tools) may also negate or reduce the disclosed advantages. Even assuming a skilled implementation, the realization of the advantages may still depend on other factors, such as the environmental conditions in which the implementation is deployed. For example, the input provided to a particular implementation may prevent one or more problems solved in the present disclosure from occurring in a particular situation, resulting in the inability to achieve the benefits of its solution. In view of the existence of possible factors outside the present disclosure, it is clearly intended that any potential advantages described herein should not be interpreted as having to meet the claim limitations to prove infringement. Instead, the identification of these potential advantages is intended to illustrate the type of (one or more) improvements that are available to designers who benefit from the present disclosure. Such permissive descriptions of advantages (eg, stating that a particular advantage "may occur") are not intended to doubt whether such advantages can in fact be achieved, but rather to recognize that achievement of such advantages often depends on technical realities of additional factors.

[0104] Unless otherwise stated, the embodiments are non-limiting. That is, the disclosed embodiments are not intended to limit the scope of the claims drafted based on the present disclosure, even if only a single example is described therein with respect to a particular feature. In the absence of any contrary description in the present disclosure, the disclosed embodiments are intended to be illustrative and not restrictive. Therefore, the present application is intended to allow claims covering the disclosed embodiments, as well as such substitutions, modifications, and equivalents that are obvious to those skilled in the art having the benefit of the present disclosure.

[0105] For example, features in this application may be combined in any suitable manner. Thus, during the examination of this application (or an application claiming priority thereto), new claims may be formulated to any such combination of features. In particular, with reference to the appended claims, features of dependent claims may, where appropriate, be combined with features of other dependent claims, including claims that are dependent on other independent claims. Similarly, features from individual independent claims may be combined where appropriate.

[0106] Thus, while the appended dependent claims may be drafted such that each dependent claim is dependent on a single other claim, additional dependencies are contemplated. Any combination of features consistent with the present disclosure in the dependent claims is contemplated and may be claimed in this or another application. In short, the combinations are not limited to those specifically listed in the appended claims.

[0107] Where appropriate, it may also be considered that claims drafted in one format or legal type (eg, apparatus) are intended to support corresponding claims in another format or legal type (eg, method).

[0108] Because this disclosure is a legal document, various terms and phrases may be subject to administrative and judicial interpretation. It is hereby notified that the definitions provided in the following paragraphs as well as throughout this disclosure will be used to determine how to interpret claims drafted based on this disclosure.

[0109] Unless the context clearly indicates otherwise, reference to an item in the singular (i.e., a noun or noun phrase beginning with "a," "an," or "the") is intended to mean "one or more." Thus, reference to "an item" in a claim does not exclude additional instances of that item in the absence of accompanying context. A "plurality" item refers to a collection of two or more items.

[0110] The word "may" is used herein in a permissive sense (ie, having the potential to, being able to), rather than in the mandatory sense (ie, must).

[0111] The terms "including" and "comprising" and forms thereof are open ended and mean "including, but not limited to."

[0112] When the term "or" is used in this disclosure with respect to a list of options, it will generally be understood to be used in a non-exclusive sense unless the context dictates otherwise. Thus, the recitation of "x or y" is equivalent to "x or y, or both," thus covering: 1) x but not y, 2) y but not x, and 3) both x and y. On the other hand, phrases such as "x or y but not both" clearly indicate that "or" is used in an exclusive sense.

[0113] The statement "w, x, y or z or any combination thereof" or "at least one of ... w, x, y and z" is intended to cover all possibilities ranging from a single element to the total number of elements in the set. For example, given the set [w, x, y, z], these phrases cover any single element of the set (e.g., w instead of x, y or z), any two elements (e.g., w and x instead of y or z), any three elements (e.g., w, x and y instead of z), and all four elements. Thus, the phrase "at least one of ... w, x, y and z" refers to at least one element in the set [w, x, y, z], thereby covering all possible combinations in the list of elements. The phrase should not be interpreted as requiring the presence of at least one instance of w, at least one instance of x, at least one instance of y, and at least one instance of z.

[0114] In this disclosure, various "labels" may precede a noun or noun phrase. Unless the context dictates otherwise, different labels (e.g., "first circuit," "second circuit," "particular circuit," "given circuit," etc.) used for a feature refer to different instances of the feature. Additionally, unless otherwise noted, the labels "first," "second," and "third," when applied to features, do not imply any type of ordering (e.g., spatial, temporal, logical, etc.).

[0115] The phrase "based on" is used to describe one or more factors that influence a determination. The term does not exclude the possibility that additional factors may influence the determination. That is, the determination may be based only on the specified factors, or on the specified factors and other unspecified factors. Consider the phrase "A is determined based on B." The phrase states that B is a factor used to determine A or influences the determination of A. The phrase does not exclude that the determination of A may also be based on some other factor, such as C. The phrase is also intended to cover embodiments in which A is determined based only on B. As used herein, the phrase "based on" is synonymous with the phrase "based at least in part on."

[0116] The phrases "in response to" and "in response to..." describe one or more factors that trigger an effect. The phrase does not exclude the possibility that additional factors may influence or otherwise trigger the effect in conjunction with or independently of the specified factors. That is, the effect may be responsive only to these factors, or may be responsive to the specified factors as well as other unspecified factors. Consider the phrase "A is performed in response to B." The phrase specifies that B is a factor that triggers the execution of A or triggers a specific result of A. The phrase does not exclude that A may also be performed in response to some other factor (e.g., C). The phrase also does not exclude that A may be performed in response to B and C together. The phrase is also intended to cover embodiments in which A is performed only in response to B. As used herein, the phrase "in response to..." is synonymous with the phrase "at least partially in response to...". Similarly, the phrase "in response to" is synonymous with the phrase "at least partially in response to."

[0117] Within the present disclosure, different entities (which may be variously referred to as "units," "circuits," other components, etc.) may be described or claimed as being "configured" to perform one or more tasks or operations. The expression "[the entity] is configured to [perform one or more tasks]" is used herein to refer to a structure (i.e., something physical). More specifically, the expression is used to indicate that the structure is arranged to perform one or more tasks during operation. A structure may be said to be "configured to" perform a task even if it is not currently being operated. Thus, an entity described or stated as "configured to" perform a task refers to something physical, such as a device, a circuit, a memory having a processor unit and storing program instructions executable to implement the task, and so on. The phrase is not used herein to refer to something intangible.

[0118] In some cases, various units / circuits / components may be described herein as performing a set of tasks or operations. It should be understood that these entities are "configured to" perform these tasks / operations, even if not specifically stated.

[0119] The term "configured to" is not intended to mean "configurable to". For example, an unprogrammed FPGA would not be considered to be "configured to" perform a particular function. However, the unprogrammed FPGA may be "configurable to" perform that function. After appropriate programming, the FPGA may then be said to be "configured to" perform a particular function.

Claims

1. A system comprising: Processor subsystem; A memory storing program instructions executable by the processor subsystem to perform operations, the operations comprising: Detecting, by an application of the first user, a request to perform a blockchain transaction, wherein the request includes information specifying a blockchain address of the second user; Calling, by the application, an application programming interface (API) of a registry of the blockchain, wherein the calling includes passing the blockchain address to the API; identifying, by the application in response to a call to the API, registration information stored in a record of the registry corresponding to the blockchain address; and The registration information is verified by the application, wherein the verification includes: verifying a certificate of the second user using a certificate authority (CA) public key, the certificate including the public key of the second user; and verifying a signed message from the second user using a public key of the second user, wherein the signed message indicates an association between the blockchain address and the second user; and In response to the registration information being verified, the application provides the first user with the identity information of the second user.

2. The system according to claim 1, wherein: The registration information includes the certificate of the second user and the signed message, the certificate includes the public key of the second user, the signed message is signed by the private key of the second user, and wherein the public key and the private key of the second user constitute a key pair.

3. The system according to claim 2, wherein: The signed message indicates that the second user owns the blockchain address, and wherein the blockchain address constitutes a hash value of the blockchain public key of the second user.

4. The system according to claim 1, wherein: The registration information includes a URL and the signed message, the URL having an address that returns the certificate when extracted using the HTTPS protocol, the certificate having the public key of the second user, and wherein the signed message is signed by the private key of the second user; and The public key and private key of the second user constitute a key pair.

5. The system according to claim 1, wherein: The identity information includes the second user's name, the second user's website, or both.

6. A method comprising: receiving, at a server computer system, a registration request for a blockchain address from a registration entity; verifying, by the server computer system, the registration request; as well as In response to the registration request being verified, storing, by the server computer system, registration information from the registration request in a first record of a registry of the blockchain; and Wherein, the registration information can be retrieved from the registration table and can be used to: Verifying the registration entity's certificate using a certificate authority (CA) public key, the certificate being signed by the CA private key; and verifying a signed message using a public key of the registration entity, the signed message indicating an association between the blockchain address and the registration entity; as well as The identity information of the registration entity is determined.

7. The method of claim 6, further comprising, after the first record is stored in the registry: receiving, at the server computer system, from a requesting entity, a certificate lookup specifying the blockchain address; and The registration information is returned by the server computer system in response to the certificate lookup.

8. The method according to claim 7, wherein: The registration request specifies a tag in addition to the blockchain address, wherein the certificate lookup additionally specifies the tag, and wherein, in response to the certificate lookup, the server computer system returns the registration information in response to determining that the registry stores information indicating that the blockchain address has already been registered in conjunction with the tag.

9. The method according to claim 6, wherein: Verifying the registration request includes verifying a signature of the registration request using the blockchain public key of the registration entity, the registration request being signed by the blockchain private key of the registration entity.

10. The method according to claim 6, wherein: The registration information includes a certificate of the registration entity, and the certificate includes a public key of the registration entity.

11. The method according to claim 6, wherein: The registration information includes a URL having an address that returns the certificate having the public key of the registration entity when extracted using the HTTPS protocol.

12. The method according to claim 6, wherein: The signed message includes the public key of the registering entity.

13. The method according to claim 12, wherein: The signed message specifies the name and website of the registering entity.

14. The method according to claim 6, further comprising: receiving, at the server computer system, a second registration request specifying a second blockchain address of the registering entity and including a second signed message signed by the registering entity; as well as In response to the second registration request being verified, storing, by the server computer system, the second signed message in a second record in the registration table along with a reference to the certificate information stored in the first record such that the second record does not include the certificate information itself.

15. A method comprising: detecting, by an application executing on a computer system, a request to perform a blockchain transaction for a first user, the request including information specifying a blockchain address of a second user on a blockchain; Calling, by the application, an application programming interface (API) of a registry of the blockchain, wherein the calling includes passing the blockchain address as a parameter of the API; identifying, by the application in response to information returned from the registry, registration information stored in a record of the registry corresponding to the address; The registration information is verified by the application, wherein the verification includes: verifying a certificate of the second user using a certificate authority (CA) public key, the certificate including the public key of the second user; and verifying a signed message of the second user using the public key of the second user, the signed message indicating an association between the blockchain address and the second user, and the signed message being signed by the private key of the second user; and In response to the registration information being verified, the application provides the first user with the identity information of the second user.

16. The method according to claim 15, wherein: The identification information includes one or both of a name and a website of the second user.

17. The method according to claim 16, wherein: Providing the identity information includes replacing the blockchain address with the identity information in a user interface to be presented to the first user.

18. The method according to claim 15, wherein: The registration information includes a certificate of the second user and a signed message, the certificate including a public key of the second user, the signed message indicating an association between the blockchain address and the second user and signed by a private key of the second user, and wherein the public key and private key of the second user constitute a key pair.

19. The method according to claim 15, wherein: The registration information includes a URL and a signed message, the URL having an address that returns the certificate when extracted using the HTTPS protocol, the certificate having the public key of the second user, wherein the signed message indicates an association between the blockchain address and the second user and is signed by the private key of the second user; and The public key and private key of the second user constitute a key pair.

20. The method according to claim 15, wherein: The application is a block explorer application.