Blockchain-based information processing method and information verification method and device

Abstract

The application provides a blockchain-based information processing method and information verification method and device. The blockchain-based information processing method is applied to a supervision node of a blockchain and includes the following steps: receiving to-be-verified information sent by a client of the blockchain, verifying the to-be-verified information, and obtaining a verification result; obtaining an on-chain address of a login client and client information; if it is determined according to the verification result that the verification is successful, the on-chain address and the client information are bound, and a binding result is stored to the blockchain. The present scheme can reduce the difficulty of implementing blockchain information processing and verification.

Description

Technical Field

[0001] This application relates to the field of blockchain technology, and in particular to a blockchain-based information processing method. This application also relates to a blockchain-based information processing apparatus, a blockchain-based information verification method, a blockchain-based information verification apparatus, a computing device, and a computer-readable storage medium. Background Technology

[0002] Blockchain is a network composed of a distributed database and multiple nodes. Data stored in a blockchain can only be added in the form of blocks through a consensus algorithm; it cannot be modified or deleted. Therefore, blockchain is widely used in scenarios where data reliability is a requirement.

[0003] In related technologies, to reduce illegal tasks in the blockchain, the information of the blockchain's gateway nodes can be pre-verified, for example, through real-name verification, and the verification results can be stored. When a user initiates a task request to the blockchain through the gateway node, the verification results can be used to verify the gateway node's information. If verification fails, it indicates that the gateway node is likely improperly configured. Consequently, the task request initiated through that gateway node is likely targeting illegal tasks, and the blockchain can refuse to respond to it. Therefore, verifying the gateway node's information can reduce the blockchain's processing of illegal tasks.

[0004] However, in the aforementioned information verification, the gateway node is the node providing network access services. Therefore, to ensure security, it is necessary to specifically set up and maintain the network access service for the blockchain, or to periodically maintain the information verification functionality of third-party nodes providing network access services. Consequently, blockchain information verification presents a significant challenge in implementation. Summary of the Invention

[0005] In view of this, embodiments of this application provide a blockchain-based information processing method. This application also relates to a blockchain-based information processing apparatus, a blockchain-based information verification method, a blockchain-based information verification apparatus, a computing device, and a computer-readable storage medium, to solve the problem of high difficulty in implementing blockchain information verification in the prior art.

[0006] According to a first aspect of the embodiments of this application, a blockchain-based information processing method is provided, applied to a supervisory node of the blockchain, comprising:

[0007] Receive the verification information sent by the client, verify the verification information, and obtain the verification result;

[0008] Obtain the on-chain address and client information of the client that is logged in;

[0009] If the verification is successful based on the verification result, the on-chain address and the client information are bound together, and the binding result is stored in the blockchain.

[0010] According to a second aspect of the embodiments of this application, a blockchain-based information verification method is provided, applied to a verification node of the blockchain, comprising:

[0011] Receive the verification request sent by the client, parse the verification request, and obtain the on-chain address to be verified;

[0012] Based on the on-chain address to be verified, find the binding result that is bound to the on-chain address to be verified from the binding results stored in the blockchain. The binding result is generated by binding the on-chain address with the client information based on the verification result of the client.

[0013] If a binding result is found that is bound to the on-chain address to be verified, then the verification is considered successful.

[0014] According to a third aspect of the embodiments of this application, a blockchain-based information processing apparatus is provided, applied to a supervisory node of the blockchain, comprising:

[0015] The verification module is configured to receive the information to be verified sent by the client, verify the information to be verified, and obtain the verification result.

[0016] The acquisition module is configured to obtain the on-chain address and client information of the client that is logged in;

[0017] The binding module is configured to bind the on-chain address and the client information if the verification is successful based on the verification result, and store the binding result in the blockchain.

[0018] According to a fourth aspect of the embodiments of this application, a blockchain-based information verification device is provided, applied to a verification node of a blockchain, comprising:

[0019] The parsing module is configured to receive verification requests sent by clients, parse the verification requests, and obtain the on-chain address to be verified.

[0020] The lookup module is configured to search for a binding result that is bound to the on-chain address to be verified from the binding results stored in the blockchain, wherein the binding result is generated by binding the on-chain address with the client information based on the verification result of the client;

[0021] The verification module is configured to determine whether the verification was successful if a binding result is found that is bound to the on-chain address to be verified.

[0022] According to a fifth aspect of the embodiments of this application, a blockchain system is provided, including: a client, a supervisory node, and a verification node;

[0023] The client is configured to send verification information to the monitoring node;

[0024] The monitoring node is configured to receive the information to be verified, verify the information to be verified, and obtain a verification result; obtain the on-chain address and client information of the client that logged in; if the verification is successful according to the verification result, bind the on-chain address and the client information, and store the binding result in the blockchain;

[0025] The client is also configured to send a verification request to the verification node;

[0026] The verification node is configured to receive the verification request, parse the verification request, and obtain the on-chain address to be verified; based on the on-chain address to be verified, search for a binding result bound to the on-chain address to be verified from the binding results stored in the blockchain; if a binding result bound to the on-chain address to be verified is found, it is determined whether the verification is successful.

[0027] According to a sixth aspect of the present application, a computing device is provided, including a memory, a processor, and computer instructions stored in the memory and executable on the processor, wherein the processor executes the instructions to implement the steps of the blockchain-based information processing method or the blockchain-based information verification method.

[0028] According to a seventh aspect of the present application, a computer-readable storage medium is provided that stores computer instructions, which, when executed by a processor, implement the steps of the blockchain-based information processing method or the blockchain-based information verification method.

[0029] One embodiment of this application provides a solution that receives verification information sent by a blockchain client, verifies the information, and obtains a verification result; it then obtains the on-chain address and client information of the logged-in client; if the verification is successful based on the verification result, it binds the on-chain address and client information and stores the binding result in the blockchain. Thus, when a client initiates a verification request to the blockchain, the blockchain can use the binding result to verify the on-chain address included in the verification request. Therefore, this solution can directly achieve blockchain information verification from the perspective of on-chain address verification, without the need for dedicated network access service setup and maintenance, thereby reducing the difficulty of implementing blockchain information processing and verification. Attached Figure Description

[0030] Figure 1 This is a flowchart illustrating a blockchain-based information processing method according to an embodiment of this application;

[0031] Figure 2 This is a flowchart of another embodiment of a blockchain-based information processing method provided in this application;

[0032] Figure 3 This is a flowchart of a blockchain-based information verification method provided in one embodiment of this application;

[0033] Figure 4 This is a flowchart of an information processing and verification method applied to blockchain, provided in one embodiment of this application;

[0034] Figure 5 This is a flowchart of another embodiment of a blockchain-based information verification method provided in this application;

[0035] Figure 6 This is a schematic diagram of the structure of a blockchain-based information processing device provided in one embodiment of this application;

[0036] Figure 7 This is a schematic diagram of the structure of a blockchain-based information verification device provided in one embodiment of this application;

[0037] Figure 8 This is a schematic diagram of the structure of a blockchain system provided in one embodiment of this application;

[0038] Figure 9 This is a structural block diagram of a computing device provided in one embodiment of this application. Detailed Implementation

[0039] Many specific details are set forth in the following description to provide a full understanding of this application. However, this application can be implemented in many other ways different from those described herein, and those skilled in the art can make similar extensions without departing from the spirit of this application; therefore, this application is not limited to the specific embodiments disclosed below.

[0040] The terminology used in one or more embodiments of this application is for the purpose of describing particular embodiments only and is not intended to limit the scope of one or more embodiments of this application. The singular forms “a,” “the,” and “the” used in one or more embodiments of this application and in the appended claims are also intended to include the plural forms unless the context clearly indicates otherwise. It should also be understood that the term “and / or” used in one or more embodiments of this application refers to and includes any or all possible combinations of one or more associated listed items.

[0041] It should be understood that although the terms first, second, etc., may be used to describe various information in one or more embodiments of this application, such information should not be limited to these terms. These terms are only used to distinguish information of the same type from one another. For example, first may also be referred to as second without departing from the scope of one or more embodiments of this application, and similarly, second may also be referred to as first. Depending on the context, the word "if" as used herein may be interpreted as "when," "when," or "in response to a determination."

[0042] This application provides a blockchain-based information processing method, and also relates to a blockchain-based information processing device, a computing device, and a computer-readable storage medium, which will be described in detail in the following embodiments.

[0043] Figure 1 The flowchart illustrates a blockchain-based information processing method according to an embodiment of this application, applied to a supervisory node of the blockchain, and specifically includes the following steps:

[0044] S102: Receive the verification information sent by the client, verify the verification information, and obtain the verification result.

[0045] In practical applications, the above verification can be real-name verification, such as KYC (Know Your Customer, a mechanism that requires all users to register their real names). Furthermore, the client can proactively send verification information upon receiving user-submitted information, or it can send verification information upon receiving a verification notification or verification failure notification from the supervisory node. The timing of sending the verification notification can be varied. For example, the blockchain supervisory node can proactively send verification notifications to each client in the blockchain. Alternatively, for example, the blockchain supervisory node can send verification notifications to each client in the blockchain upon receiving an address generation request from a client. Based on this, the client displays the received verification notification, and the user submits verification information in the client according to the displayed notification. The client then sends the user-submitted verification information to the blockchain supervisory node.

[0046] Furthermore, the information to be verified is information used to demonstrate the authenticity of the user's identity, specifically including at least one of the following: the user's ID number, user video, and user image. The specific methods by which the blockchain's supervisory node verifies the information to be verified can be varied and exemplary. The supervisory node can input the information to be verified into a pre-trained recognition model to obtain a verification result. The recognition model is a neural network model trained using identity information from an identity information database and verification result labels. Alternatively, the supervisory node can, exemplary, send the information to be verified to a designated verification platform and receive the verification result returned by the designated verification platform. The designated verification platform can be a platform capable of user real-name verification, such as a security management department or a financial regulatory department.

[0047] S104, obtain the on-chain address and client information of the login client.

[0048] In practical applications, there are several ways to obtain the on-chain address of the login client. For example, if the on-chain address of the login client is sent along with the verification information, then receiving that on-chain address is sufficient. Alternatively, for example, if the client's login information is received, the on-chain address can be read from that information to obtain the login client's on-chain address. Or, if the client requests to generate an on-chain address, the generated on-chain address can be used as the login client's on-chain address. Furthermore, the client information may include the client identifier, client device information, and a summary of the aforementioned verification information.

[0049] S106 If the verification result indicates that the verification was successful, the on-chain address and client information are bound together, and the binding result is stored in the blockchain.

[0050] In practical applications, storing the binding result on the blockchain can be done in several ways. For example, the binding result can be directly stored on the blockchain, or an expiration date can be added to the binding result, and the binding result with the added expiration date can be stored on the blockchain. Here, the expiration date refers to the validity period of the binding result. For ease of understanding and logical layout, the second scenario will be specifically described below as an optional embodiment. Furthermore, to improve security, any data stored on the blockchain can be encrypted before storage.

[0051] Furthermore, the aforementioned blockchain can be any of the following: public blockchain, consortium blockchain, and private blockchain. Public blockchains typically lack access control rules, allowing any user to process tasks, which can easily lead to the execution of unauthorized tasks, such as those spreading illegal information. To address this, the solution provided in this application can verify users utilizing the public blockchain through the aforementioned binding results, improving the public blockchain's security and reducing the execution of unauthorized tasks. Consortium blockchains and private blockchains verify permissions by checking the blockchain's gateway nodes, which presents a challenge in information verification implementation. To address this, the solution provided in this application can directly verify blockchain information from the on-chain address verification dimension, eliminating the need for dedicated network access service setup and maintenance, thereby reducing the difficulty of blockchain information processing and verification. Therefore, this application has a wide range of applicable scenarios.

[0052] One embodiment of this application provides a solution that receives verification information sent by a blockchain client, verifies the information, and obtains a verification result; it then obtains the on-chain address and client information of the logged-in client; if the verification is successful based on the verification result, it binds the on-chain address and client information and stores the binding result in the blockchain. Thus, when a client initiates a verification request to the blockchain, the blockchain can use the binding result to verify the on-chain address included in the verification request. Therefore, this solution can directly achieve blockchain information verification from the perspective of on-chain address verification, without the need for dedicated network access service setup and maintenance, thereby reducing the difficulty of implementing blockchain information processing and verification.

[0053] In an optional implementation, the blockchain-based information processing method provided in this application may further include the following steps:

[0054] If the verification result indicates that the verification has failed, a verification failure notification will be sent to the client.

[0055] In practical applications, the verification failure notification can include information indicating the failure and the reason for the failure. Upon receiving the notification, the client can display it, allowing the user to resubmit the verification information. This embodiment allows users to promptly know whether the verification was successful, thereby improving the user experience.

[0056] In one optional implementation, the above-mentioned binding of on-chain addresses and client information, and storage of the binding result in the blockchain, may specifically include the following steps:

[0057] Bind the on-chain address and client information to obtain the binding result and determine the binding timestamp;

[0058] The validity period of the binding result is determined based on the binding timestamp and the preset validity period;

[0059] Add the validity period to the binding result and store the binding result with the added validity period to the blockchain.

[0060] In practical applications, binding on-chain addresses and client information can be done in various ways. For example, a correspondence can be established between on-chain addresses and client information; this correspondence is the binding result. The correspondence can be in the form of a correspondence table or pointers. Alternatively, for example, client information can be added to the on-chain address to obtain the binding result. Any method of binding on-chain addresses and client information can be used in this application, and this embodiment does not limit this. Furthermore, storing the binding result with the added validity period in the blockchain can specifically include: processing the binding result with the added validity period into a block, sending the block to the blockchain's verification nodes, and broadcasting the block in the blockchain if the blockchain's verification nodes determine that the block conforms to a preset block format. Based on this, if any node in the blockchain receives the block and has not stored the block itself, it stores the block and records the event of storing the block in the blockchain ledger.

[0061] Furthermore, the binding timestamp refers to the point in time when the binding result is obtained. There are various ways to determine the validity period of the binding result based on the binding timestamp and the preset validity period. For example, the binding timestamp and the preset validity period can be directly used as the validity period of the binding result. Alternatively, for example, the time span between the binding timestamp and the binding timestamp, which is the preset validity period, can be used as the validity period of the binding result. For instance, if the binding timestamp is September 14, 2021, at 12:00, and the preset validity period is 30 days, then the validity period of the binding result is October 14, 2021, at 12:00.

[0062] This embodiment ensures the timeliness of the binding result. Thus, during the blockchain-based information verification process, on-chain addresses that have exceeded their validity period can be automatically classified as invalid addresses, and the verification result corresponding to the verification request of an invalid address will be a verification failure. Furthermore, if a task request is initiated through this invalid address, the execution of the task corresponding to the task request will be prohibited, thereby further improving security.

[0063] In an optional implementation, the blockchain-based information processing method provided in this application may further include the following steps:

[0064] Receive the address generation request sent by the client;

[0065] Send a verification notification to the client, whereby the verification notification is used to instruct the client to send the information to be verified according to the verification notification;

[0066] Determine whether the information to be verified has already been verified;

[0067] If so, then requesting to generate a response address is prohibited.

[0068] In practical applications, to reduce the likelihood of user-sent task requests being blocked and to minimize the sending of verification notifications to a large number of already verified clients, a verification notification can be sent to the client upon receiving an address generation request (i.e., when a user requests an on-chain address). Building on this, to further enhance security by reducing the possibility of unauthorized users misusing verification information, a principle can be adopted where each verified user has only one on-chain address. This ensures a one-to-one correspondence between the information to be verified and the on-chain address, thereby guaranteeing a one-to-one correspondence between the on-chain address and the binding result. Specifically, it can be determined whether the information to be verified has already been verified; if so, responding to the address generation request should be prohibited.

[0069] Furthermore, the principle of one-to-one correspondence between the aforementioned information to be verified and on-chain addresses can be applied to this application. Figure 1 In the embodiments, that is, in the above Figure 1 Before verifying the information to be verified in the embodiment, it can be determined whether the information to be verified has been verified; if so, a verification failure notification is sent to the client; if not, the step of verifying the information to be verified is executed.

[0070] In an optional implementation, the blockchain-based information processing method provided in this application may further include the following steps:

[0071] Generate a private key corresponding to the address generation request using a specified random algorithm;

[0072] Accordingly, obtaining the on-chain address of the login client can specifically include the following steps:

[0073] Based on the private key, the public key corresponding to the address generation request is generated using the first encryption algorithm.

[0074] Based on the public key, the on-chain address of the login client is generated using a second encryption algorithm.

[0075] In practical applications, the specified random algorithm, the first encryption algorithm, and the second encryption algorithm are all irreversible algorithms, also known as asymmetric encryption algorithms. This means that the input of the algorithm cannot be derived from its output, thus ensuring the security of the private key, public key, and on-chain address. Furthermore, if it is determined that the information to be verified has not been verified, it indicates that the information has not been verified, which conforms to the principle of a one-to-one correspondence between the information to be verified and the on-chain address. Therefore, the steps of this embodiment can be executed to generate a corresponding on-chain address for the request. After this on-chain address is sent to the client, the user uses this on-chain address to log in to the client. Therefore, the generated address is the on-chain address for logging into the client.

[0076] This embodiment generates an on-chain address for the login client for users who meet the principle of one-to-one correspondence between the information to be verified and the on-chain address. This can reduce the possibility of unauthorized users impersonating verification information and further improve security.

[0077] For ease of understanding, the following will use... Figure 2 The following is a flowchart of a blockchain-based information processing method provided in another embodiment of this application, which relates to the above. Figure 1 The embodiments and some optional embodiments are described in an integrated manner.

[0078] For example, such as Figure 2 As shown, another embodiment of this application provides a blockchain-based information processing method applied to a blockchain monitoring node, which may include the following steps:

[0079] Start; initiate real-name verification of on-chain addresses and receive verification information submitted by users;

[0080] Verify whether the information to be verified meets the real-name verification requirements; if yes, bind the on-chain address, client information, and verification validity period; if no, the verification fails.

[0081] The steps in this embodiment are the same as those described above. Figure 1 Implementation Examples and Figure 1 In some optional embodiments, steps that have the same function are considered similar steps. The identical parts will not be repeated here; please refer to the above for details. Figure 1Description of the embodiments and some optional embodiments. The difference lies in the different ways of expression for the sake of brevity. Specifically: Start, which is equivalent to the client starting up or the blockchain starting up; Initiating real-name verification of the on-chain address, which is equivalent to sending a verification notification to the client; Receiving the information to be verified submitted by the user, which is equivalent to receiving the information to be verified sent by the client; Verifying whether the information to be verified meets the real-name verification requirements, which is equivalent to verifying the information to be verified and obtaining the verification result; Binding the on-chain address, client information and verification validity period, which is equivalent to binding the on-chain address and client information and obtaining the binding result, determining the binding timestamp, determining the validity period of the binding result based on the binding timestamp and the preset validity period, adding the validity period to the binding result, and storing the binding result with the added validity period to the blockchain; Verification failure, which is equivalent to sending a verification failure notification to the client.

[0082] Figure 3 The diagram illustrates a flowchart of a blockchain-based information verification method according to an embodiment of this application, applied to a blockchain verification node. The method may include the following steps:

[0083] S302 receives the verification request sent by the client, parses the verification request, and obtains the on-chain address to be verified.

[0084] In practical applications, verification requests can be requests to verify on-chain addresses, task requests, and so on. Correspondingly, there are various ways to parse a verification request to obtain the on-chain address to be verified. For example, if the verification request is for verifying an on-chain address, a preset regular expression algorithm can be used to extract keywords from the verification request; the extracted keywords are the on-chain address to be verified. Alternatively, the verification request can be matched against a preset dictionary; the successfully matched characters are the on-chain address to be verified. Or, for example, if the verification request is a task request, and task requests are typically signed using the user's private key, then the private key in the task request can be read, processed using a first encryption algorithm to obtain the public key, and then processed using a second encryption algorithm to obtain the on-chain address to be processed.

[0085] Additionally, the on-chain address to be verified may include the on-chain address of the login client, as well as the on-chain address of another user who interacts with the user using the client.

[0086] S304. Based on the on-chain address to be verified, find the binding result that is bound to the on-chain address to be verified from the binding results stored in the blockchain.

[0087] The binding result is generated by binding the on-chain address with the client information based on the verification result of the client.

[0088] In practical applications, the on-chain address is bound to the client information based on the verification result of the client, and this process can specifically include the above. Figure 1 Implementation Examples and Figure 1 The optional embodiments provide steps for any blockchain-based information processing method. Based on the on-chain address, searching for a binding result bound to the on-chain address from the binding results stored in the blockchain can specifically include: comparing the binding result recorded in the blockchain ledger stored by the verification node with the on-chain address to be verified; if the on-chain address corresponding to the binding result is the same as the on-chain address to be verified, then it is determined that a binding result bound to the on-chain address to be verified has been found; if the on-chain address corresponding to the binding result is different from the on-chain address to be verified, then it is determined that no binding result bound to the on-chain address to be verified has been found.

[0089] Furthermore, since the binding results contain client information, it's also possible to obtain the client information of the client that sent the verification request. From the binding results stored on the blockchain, we can search for candidate binding results that include this client information, and then search for binding results with on-chain addresses within those candidate results. This effectively filters the bindings using client information, improving search efficiency.

[0090] S306. If a binding result is found for an on-chain address to be verified, then the verification is considered successful.

[0091] If a binding result is found that is bound to an on-chain address to be verified, it indicates that the on-chain address to be verified is the one specified in this application. Figure 1 Implementation Examples and Figure 1 In the optional embodiment, the on-chain address that has been verified and successfully verified can be considered as having been successfully verified. If the search result is not found, the verification is considered to have failed. Furthermore, after confirming successful verification, the verification node can send a notification of successful verification to the client; if the verification request is a task request, the verification node can execute the task corresponding to the task request after confirming successful verification.

[0092] One embodiment of this application provides a solution that receives verification information sent by a blockchain client, verifies the information, and obtains a verification result; it then obtains the on-chain address and client information of the logged-in client; if the verification is successful based on the verification result, it binds the on-chain address and client information and stores the binding result in the blockchain. Thus, when a client initiates a verification request to the blockchain, the blockchain can use the binding result to verify the on-chain address included in the verification request. Therefore, this solution can directly achieve blockchain information verification from the perspective of on-chain address verification, without the need for dedicated network access service setup and maintenance, thereby reducing the difficulty of implementing blockchain information processing and verification.

[0093] For ease of understanding, the following will use... Figure 4 The flowchart shown in this application illustrates an information processing and verification method applied to blockchain, which will be used as an example to further explain the method provided in this application.

[0094] For example, such as Figure 4 As shown in the figure, an embodiment of this application provides a flow chart of an information processing and verification method applied to a blockchain. The blockchain includes a client, a monitoring node, and a verification node. The method may include:

[0095] S402, the client sends the verification information to the supervisory node.

[0096] S404, the supervisory node verifies the received information to be verified and obtains the verification result.

[0097] S406, the supervisory node obtains the on-chain address and client information of the logged-in client.

[0098] S408: If the supervisory node determines that the verification is successful based on the verification results, it binds the on-chain address and client information and stores the binding result on the blockchain.

[0099] S410, the client sends a verification request to the verification node.

[0100] S412, the verification node parses the received verification request and obtains the on-chain address to be verified.

[0101] S414, the verification node searches for the binding result of the on-chain address to be verified from the binding results stored in the blockchain.

[0102] S416 If the verification node finds a binding result for the on-chain address to be verified, the verification is considered successful.

[0103] In this embodiment, S402 to S416 are respectively related to the above... Figure 1Implementation examples Figure 1 Optional embodiments Figure 2 Implementation Examples and Figure 2 In optional embodiments, steps that are described in the same way are considered identical steps and will not be repeated here. Please refer to the above for details. Figure 1 Implementation examples Figure 1 Optional embodiments Figure 2 Implementation Examples and Figure 2 The same steps are described in optional embodiments.

[0104] In one optional implementation, the binding result includes a validity period;

[0105] Accordingly, if a binding result is found that is bound to the on-chain address to be verified, the verification is considered successful. This can specifically include the following steps:

[0106] If a binding result is found that is bound to the on-chain address to be verified, the validity period is read from the found binding result;

[0107] Based on the validity period and the current time, determine whether the on-chain address to be verified is within its validity period;

[0108] If it is in the specified state, then the verification is successful.

[0109] This embodiment can automatically classify on-chain addresses that have exceeded their validity period as invalid addresses, and the verification result corresponding to the verification request of an invalid address will be verification failure; furthermore, if a task request is initiated through the invalid address, the execution of the task corresponding to the task request will be prohibited, thereby further improving security.

[0110] Furthermore, there are various ways to determine whether the on-chain address to be verified is within its validity period based on the validity period and the current time. The following is a detailed description in the form of optional embodiments.

[0111] In one optional implementation, the above-mentioned validity period includes: the expiration time point;

[0112] Accordingly, determining whether an on-chain address to be verified is within its validity period based on the validity period and the current time can specifically include the following steps:

[0113] Compare the current time point with the expiration time point. If the current time point exceeds the expiration time point, it is determined that the face address to be verified is not within the validity period; otherwise, it is determined that the face address to be verified is within the validity period.

[0114] The failure time point can specifically include a date and a specific time. For example, if the failure time point is 22:00 on March 15, 2022, and the current time point is 22:01 on March 15, 2022, then the current time point exceeds the failure time point. Furthermore, the aforementioned time point can be accurate to the second; this embodiment does not limit the precision of the time point.

[0115] In one optional implementation, the validity period may include: a timestamp when the binding result is obtained and a preset validity period;

[0116] Accordingly, determining whether an on-chain address to be verified is within its validity period based on the validity period and the current time can specifically include the following steps:

[0117] Calculate the time span between the timestamp and the current time.

[0118] Based on the relationship between the time span and the preset validity period, it is determined whether the on-chain address to be verified is within its validity period.

[0119] Specifically, if the time span is greater than the validity period, the on-chain address to be verified is determined to be outside its validity period; otherwise, it is determined to be within its validity period. For example, the binding timestamp is September 14, 2021, 12:00, the preset validity period is 30 days, and the current time is October 16, 2021, 12:00. Thus, the time span between the timestamp and the current time is 32 days, which is greater than the preset validity period of 30 days. Therefore, it is determined that the on-chain address to be verified is not within its validity period. This embodiment can determine whether the on-chain address to be verified is within its validity period by measuring the time span between the timestamp and the current time.

[0120] In an optional implementation, the blockchain-based information verification method provided in this application may further include the following steps:

[0121] If no binding result is found for the on-chain address to be verified, a verification failure notification is sent to the client.

[0122] In practical applications, the verification failure notification can include information indicating the failure and the reason for the failure. Upon receiving the notification, the client can display it, allowing the user to resubmit the verification information. This embodiment allows users to promptly know whether the verification was successful, thereby improving the user experience.

[0123] For ease of understanding, the following will use... Figure 5 The flowchart shown below illustrates another embodiment of this application, illustrating a blockchain-based information verification method. Figure 3 Implementation Examples and Figure 3Some optional embodiments are integrated to further illustrate the blockchain-based information verification method provided in this application.

[0124] For example, such as Figure 5 As shown in another embodiment of this application, a blockchain-based information verification method is provided, applied to a blockchain verification node. This method may include the following steps:

[0125] A task begins; the corresponding chain address of the task is parsed and obtained.

[0126] The blockchain verifies whether the on-chain address corresponding to the task has passed real-name verification; if it has, it determines whether the timeliness of the real-name authentication is qualified; if it is qualified, the verification is successful and the task is executed.

[0127] If real-name verification fails, a verification failure message will be returned; if the timeliness is not up to standard, a verification failure message will be returned.

[0128] The steps in this embodiment are the same as those described above. Figure 3 Implementation Examples and Figure 3 In some optional embodiments, steps that have the same function are considered similar steps. The identical parts will not be repeated here; please refer to the above for details. Figure 3 Implementation Examples and Figure 3 Description of some optional embodiments. The difference lies in the different ways of expression for the sake of brevity. Specifically: the start of a task is equivalent to receiving a task request sent by the client; the blockchain verifies whether the on-chain address corresponding to the task has passed real-name verification, which is equivalent to the verification node searching for the binding result of the on-chain address to be verified from the binding results stored in the blockchain; determining whether the timeliness of real-name authentication is qualified is equivalent to determining whether the on-chain address to be verified is within the validity period based on the validity period and the current time; failure to pass real-name verification is equivalent to not finding it; returning verification failure information is equivalent to sending a verification failure notification to the client; failure to meet timeliness is equivalent to not being within the validity period.

[0129] Corresponding to the above method embodiments, this application also provides embodiments of a blockchain-based information processing device. Figure 6 A schematic diagram of the structure of a blockchain-based information processing device according to an embodiment of this application is shown. Figure 6 As shown, this device is used in the supervisory nodes of a blockchain and includes:

[0130] The verification module 602 is configured to receive the information to be verified sent by the client, verify the information to be verified, and obtain the verification result.

[0131] The acquisition module 604 is configured to obtain the on-chain address and client information of the client that is logged in;

[0132] The binding module 606 is configured to bind the on-chain address and the client information if the verification is successful based on the verification result, and store the binding result in the blockchain.

[0133] One embodiment of this application provides a solution that receives verification information sent by a blockchain client, verifies the information, and obtains a verification result; it then obtains the on-chain address and client information of the logged-in client; if the verification is successful based on the verification result, it binds the on-chain address and client information and stores the binding result in the blockchain. Thus, when a client initiates a verification request to the blockchain, the blockchain can use the binding result to verify the on-chain address included in the verification request. Therefore, this solution can directly achieve blockchain information verification from the perspective of on-chain address verification, without the need for dedicated network access service setup and maintenance, thereby reducing the difficulty of implementing blockchain information processing and verification.

[0134] In an alternative implementation, the binding module 606 is further configured to:

[0135] Bind the on-chain address and the client information to obtain the binding result and determine the binding timestamp;

[0136] The validity period of the binding result is determined based on the binding timestamp and the preset validity period;

[0137] The validity period is added to the binding result, and the binding result with the validity period added is stored in the blockchain.

[0138] In an alternative implementation, the verification module 602 is further configured to:

[0139] Receive an address generation request sent by the client; send a verification notification to the client, wherein the verification notification is used to instruct the client to send verification information according to the verification notification;

[0140] Determine whether the information to be verified has been verified; if so, prohibit responding to the address generation request.

[0141] In an alternative implementation, the verification module 602 is further configured to:

[0142] A private key corresponding to the address generation request is generated using a specified random algorithm;

[0143] Accordingly, the acquisition module 604 is further configured to:

[0144] Based on the private key, the public key corresponding to the address generation request is generated using the first encryption algorithm;

[0145] Based on the public key, an on-chain address for logging into the client is generated using a second encryption algorithm.

[0146] In an alternative implementation, the verification module 602 is further configured to:

[0147] If the verification fails based on the verification result, a verification failure notification is sent to the client.

[0148] The above is an illustrative scheme of a blockchain-based information verification device according to this embodiment. It should be noted that the technical solution of this blockchain-based information verification device and the technical solution of the aforementioned blockchain-based information verification method belong to the same concept. Details not described in detail in the technical solution of the blockchain-based information verification device can be found in the description of the technical solution of the aforementioned blockchain-based information verification method.

[0149] Corresponding to the above method embodiments, this application also provides embodiments of a blockchain-based information verification device. Figure 7 A schematic diagram of a blockchain-based information verification device according to an embodiment of this application is shown. Figure 7 As shown, this device is used in blockchain verification nodes and includes:

[0150] The parsing module 702 is configured to receive a verification request sent by the client, parse the verification request, and obtain the on-chain address to be verified.

[0151] The lookup module 704 is configured to look up a binding result that is bound to the on-chain address to be verified from the binding results stored in the blockchain, based on the on-chain address to be verified. The binding result is generated by binding the on-chain address with the client information based on the verification result of the client.

[0152] The verification module 706 is configured to determine that the verification is successful if a binding result is found that is bound to the on-chain address to be verified.

[0153] One embodiment of this application provides a solution that receives verification information sent by a blockchain client, verifies the information, and obtains a verification result; it then obtains the on-chain address and client information of the logged-in client; if the verification is successful based on the verification result, it binds the on-chain address and client information and stores the binding result in the blockchain. Thus, when a client initiates a verification request to the blockchain, the blockchain can use the binding result to verify the on-chain address included in the verification request. Therefore, this solution can directly achieve blockchain information verification from the perspective of on-chain address verification, without the need for dedicated network access service setup and maintenance, thereby reducing the difficulty of implementing blockchain information processing and verification.

[0154] In one optional implementation, the binding result includes a validity period;

[0155] Accordingly, the verification module 706 is further configured as follows:

[0156] If a binding result is found that is bound to the on-chain address to be verified, the validity period is read from the found binding result;

[0157] Based on the validity period and the current time, determine whether the on-chain address to be verified is within the validity period;

[0158] If it is in the specified state, then the verification is successful.

[0159] In one optional implementation, the validity period includes: a timestamp when the binding result is obtained and a preset validity duration;

[0160] The verification module 706 is further configured as follows:

[0161] Calculate the time span between the timestamp and the current time point;

[0162] Based on the relationship between the time span and the preset validity period, it is determined whether the on-chain address to be verified is within the validity period.

[0163] In an alternative implementation, the lookup module 704 is further configured to:

[0164] If no binding result is found for the on-chain address to be verified, a verification failure notification is sent to the client.

[0165] The above is an illustrative scheme of a blockchain-based information verification device according to this embodiment. It should be noted that the technical solution of this blockchain-based information verification device and the technical solution of the aforementioned blockchain-based information verification method belong to the same concept. Details not described in detail in the technical solution of the blockchain-based information verification device can be found in the description of the technical solution of the aforementioned blockchain-based information verification method.

[0166] Figure 8 A structural block diagram of a blockchain system according to an embodiment of this application is shown. The blockchain system includes: a client 802, a supervisory node 804, and a verification node 806;

[0167] The client 802 is configured to send verification information to the monitoring node 804;

[0168] The monitoring node 804 is configured to receive the information to be verified, verify the information to be verified, and obtain the verification result; obtain the on-chain address and client information of the client that logged in; if the verification is successful according to the verification result, bind the on-chain address and the client information, and store the binding result in the blockchain;

[0169] The client 802 is also configured to send a verification request to the verification node 806;

[0170] The verification node 806 is configured to receive the verification request, parse the verification request, and obtain the on-chain address to be verified; based on the on-chain address to be verified, search for a binding result bound to the on-chain address to be verified from the binding results stored in the blockchain; if a binding result bound to the on-chain address to be verified is found, the verification is determined to be successful.

[0171] One embodiment of this application provides a solution that receives verification information sent by a blockchain client, verifies the information, and obtains a verification result; it then obtains the on-chain address and client information of the logged-in client; if the verification is successful based on the verification result, it binds the on-chain address and client information and stores the binding result in the blockchain. Thus, when a client initiates a verification request to the blockchain, the blockchain can use the binding result to verify the on-chain address included in the verification request. Therefore, this solution can directly achieve blockchain information verification from the perspective of on-chain address verification, without the need for dedicated network access service setup and maintenance, thereby reducing the difficulty of implementing blockchain information processing and verification.

[0172] Figure 9A structural block diagram of a computing device 900 according to an embodiment of this application is shown. The components of the computing device 900 include, but are not limited to, a memory 920 and a processor 940. The processor 940 is connected to the memory 920 via a bus 960, and a database 9010 is used to store data.

[0173] The computing device 900 also includes an access device 980, which enables the computing device 900 to communicate via one or more networks 9012. Examples of these networks include Public Switched Telephone Network (PSTN), Local Area Network (LAN), Wide Area Network (WAN), Personal Area Network (PAN), or combinations of communication networks such as the Internet. The access device 980 may include one or more of any type of wired or wireless network interface (e.g., Network Interface Controller (NIC)), such as an IEEE 802.11 Wireless Local Area Networks (WLAN) wireless interface, a Wi-MAX (Worldwide Interoperability for Microwave Access) interface, an Ethernet interface, a Universal Serial Bus (USB) interface, a cellular network interface, a Bluetooth interface, a Near Field Communication (NFC) interface, and so on.

[0174] In one embodiment of this application, the aforementioned components of the computing device 900 and Figure 9 Other components, not shown, can also be connected to each other, for example, via a bus. It should be understood that... Figure 9 The block diagram of the computing device shown is for illustrative purposes only and is not intended to limit the scope of this application. Those skilled in the art can add or replace other components as needed.

[0175] The computing device 900 can be any type of stationary or mobile computing device, including mobile computers or mobile computing devices (e.g., tablet computers, personal digital assistants, laptop computers, notebook computers, netbooks, etc.), mobile phones (e.g., smartphones), wearable computing devices (e.g., smartwatches, smart glasses, etc.) or other types of mobile devices, or stationary computing devices such as desktop computers or PCs. The computing device 900 can also be a mobile or stationary server.

[0176] When the processor 940 executes the instructions, it implements the steps of the blockchain-based information processing method or the blockchain-based information verification method.

[0177] The above is an illustrative scheme of a computing device according to this embodiment. It should be noted that the technical solution of this computing device belongs to the same concept as the technical solution of the blockchain-based information processing method or the blockchain-based information verification method described above. For details not described in detail in the technical solution of the computing device, please refer to the description of the technical solution of the blockchain-based information processing method or the blockchain-based information verification method described above.

[0178] An embodiment of this application also provides a computer-readable storage medium storing computer instructions that, when executed by a processor, implement the steps of the blockchain-based information processing method or the blockchain-based information verification method as described above.

[0179] The above is an illustrative scheme of a computer-readable storage medium according to this embodiment. It should be noted that the technical solution of this storage medium belongs to the same concept as the technical solutions of the aforementioned blockchain-based information processing method or blockchain-based information verification method. Details not described in detail in the technical solution of the storage medium can be found in the descriptions of the aforementioned blockchain-based information processing method or blockchain-based information verification method.

[0180] The foregoing has described specific embodiments of this application. Other embodiments are within the scope of the appended claims. In some cases, the actions or steps recited in the claims may be performed in a different order than that shown in the embodiments and may still achieve the desired results. Furthermore, the processes depicted in the drawings do not necessarily require the specific or sequential order shown to achieve the desired results. In some embodiments, multitasking and parallel processing are also possible or may be advantageous.

[0181] The computer instructions include computer program code, which may be in the form of source code, object code, executable file, or some intermediate form. The computer-readable medium may include: any entity or device capable of carrying the computer program code, recording media, USB flash drive, portable hard drive, magnetic disk, optical disk, computer memory, read-only memory (ROM), random access memory (RAM), electrical carrier signals, telecommunication signals, and software distribution media, etc. It should be noted that the content included in the computer-readable medium may be appropriately added to or subtracted according to the requirements of legislation and patent practice in the jurisdiction. For example, in some jurisdictions, according to legislation and patent practice, computer-readable media may not include electrical carrier signals and telecommunication signals.

[0182] It should be noted that, for the sake of simplicity, the foregoing method embodiments are all described as a series of actions. However, those skilled in the art should understand that this application is not limited to the described order of actions, as some steps may be performed in other orders or simultaneously according to this application. Furthermore, those skilled in the art should also understand that the embodiments described in the specification are preferred embodiments, and the actions and modules involved are not necessarily essential to this application.

[0183] In the above embodiments, the descriptions of each embodiment have different focuses. For parts not described in detail in a certain embodiment, please refer to the relevant descriptions of other embodiments.

[0184] The preferred embodiments disclosed above are merely illustrative of this application. The optional embodiments do not exhaustively describe all details, nor do they limit the invention to the specific implementations described. Clearly, many modifications and variations can be made based on the content of this application. These embodiments are selected and specifically described in this application to better explain the principles and practical applications of this application, thereby enabling those skilled in the art to better understand and utilize this application. This application is limited only by the claims and their full scope and equivalents.

Claims

1. A blockchain-based information processing method, characterized in that, The method, applied to a regulatory node in a blockchain, includes: Receive the verification information sent by the client, verify the verification information, and obtain the verification result; Obtain the on-chain address and client information of the client that is logged in; If the verification is successful based on the verification result, the on-chain address and the client information are bound together, and the binding result is stored in the blockchain. The method further includes: Receive the address generation request sent by the client; A verification notification is sent to the client, wherein the verification notification is used to instruct the client to send verification information according to the verification notification; Determine whether the information to be verified has already been verified; If so, then the response to the address generation request is prohibited.

2. The method according to claim 1, characterized in that, The binding of the on-chain address and the client information, and the storage of the binding result in the blockchain, includes: Bind the on-chain address and the client information to obtain the binding result and determine the binding timestamp; The validity period of the binding result is determined based on the binding timestamp and the preset validity period; The validity period is added to the binding result, and the binding result with the validity period added is stored in the blockchain.

3. The method according to claim 1, characterized in that, The method further includes: A private key corresponding to the address generation request is generated using a specified random algorithm; Obtaining the on-chain address for logging into the client includes: Based on the private key, the public key corresponding to the address generation request is generated using the first encryption algorithm; Based on the public key, an on-chain address for logging into the client is generated using a second encryption algorithm.

4. The method according to any one of claims 1 to 3, characterized in that, The method further includes: If the verification fails based on the verification result, a verification failure notification is sent to the client.

5. A blockchain-based information processing device, characterized in that, A regulatory node for blockchain, the device comprising: The verification module is configured to receive the information to be verified sent by the client, verify the information to be verified, and obtain the verification result. The acquisition module is configured to obtain the on-chain address and client information of the client that is logged in; The binding module is configured to bind the on-chain address and the client information if the verification is successful based on the verification result, and store the binding result in the blockchain; This also includes: Receive the address generation request sent by the client; A verification notification is sent to the client, wherein the verification notification is used to instruct the client to send verification information according to the verification notification; Determine whether the information to be verified has already been verified; If so, then the response to the address generation request is prohibited.

6. A blockchain system, characterized in that, The blockchain system includes: clients, monitoring nodes, and verification nodes; The client is configured to send verification information to the monitoring node; The monitoring node is configured to receive the information to be verified, verify the information to be verified, and obtain a verification result; obtain the on-chain address and client information of the client that logged in; if the verification is successful according to the verification result, bind the on-chain address and the client information, and store the binding result in the blockchain; The client is also configured to send a verification request to the verification node; The verification node is configured to receive the verification request, parse the verification request, obtain the on-chain address to be verified, and search for a binding result bound to the on-chain address to be verified from the binding results stored in the blockchain. If a binding result bound to the on-chain address to be verified is found, the verification is determined to be successful. The monitoring node is further configured as follows: Receive the address generation request sent by the client; A verification notification is sent to the client, wherein the verification notification is used to instruct the client to send verification information according to the verification notification; Determine whether the information to be verified has already been verified; If so, then the response to the address generation request is prohibited.

7. A computing device, comprising a memory, a processor, and computer instructions stored in the memory and executable on the processor, characterized in that, When the processor executes the instructions, it implements the steps of the method according to any one of claims 1 to 4.

8. A computer-readable storage medium storing computer instructions, characterized in that, When executed by the processor, this instruction implements the steps of the method according to any one of claims 1 to 4.

9. A computer program product comprising computer instructions, characterized in that, When executed by a processor, the computer instructions implement the steps of the method according to any one of claims 1 to 4.

Images