Data processing method and device based on block chain and computer equipment

Abstract

The invention relates to a data processing method and device based on a block chain, computer equipment, a storage medium and a computer program product. The method comprises the steps that a reputation authentication request sent by a target account is received, the reputation authentication request carries a target service identifier and to-be-authenticated reputation data, and the to-be-authenticated reputation data is experience data of the target account in the real world; querying whether a target registered reputation service matched with the target service identifier exists in the registered reputation service, wherein the registered reputation service is obtained based on a registration request of a certification authority account for the reputation service; if the target registered reputation service matched with the target service identifier exists, obtaining a corresponding target analysis contract based on reputation analysis contract information in the target registered reputation service; and calling the target analysis contract to authenticate the to-be-authenticated reputation data based on the data source information in the target registered reputation service to obtain an authentication result. By adopting the method, the convenience of reputation authentication can be improved.

Description

Technical Field

[0001] The present application relates to the field of computer technology, and in particular to a blockchain-based data processing method, apparatus, computer equipment, storage medium, and computer program product. Background Art

[0002] With the development of computer technology, blockchain technology has been widely used. For example, the more common evidence storage system and DID (Decentralized ID) system.

[0003] In traditional technology, there are many evidence storage and DID service providers, and each organization independently develops its own system. Since the standards for the construction of each system are different, the data verification and authentication standards are also different, resulting in increasingly complex data. In addition, the evidence storage data between systems developed by different organizations cannot be mutually recognized and interoperable, resulting in a high cost for data interoperability for reputation authentication. Summary of the invention

[0004] Based on this, it is necessary to provide a blockchain-based data processing method, device, computer equipment, computer-readable storage medium and computer program product that can improve the convenience of reputation authentication and reduce the data interoperability cost of reputation authentication in response to the above-mentioned technical problems.

[0005] In a first aspect, the present application provides a data processing method based on blockchain. The method comprises:

[0006] Receive a reputation authentication request sent by a target account, the reputation authentication request carries a target service identifier of a requested reputation service and reputation data to be authenticated, the reputation data to be authenticated is the experience data of the target account in the real world, the reputation authentication request is a request to authenticate the experience data of the target account in the real world, and the reputation service is a service to authenticate the experience data of the target account in the real world;

[0007] Querying whether there is a target registered reputation service matching the target service identifier in the registered reputation service, where the registered reputation service is obtained based on a registration request to the reputation service by the certification authority account;

[0008] If there is a target registered reputation service that matches the target service identifier, obtain the corresponding target resolution contract based on the reputation resolution contract information in the target registered reputation service;

[0009] Based on the data source information in the target registered reputation service, the target resolution contract is called to authenticate the reputation data to be authenticated to obtain the authentication result corresponding to the reputation authentication request.

[0010] In a second aspect, the present application also provides a data processing device based on blockchain. The device includes:

[0011] A request receiving module, used to receive a reputation authentication request sent by a target account, the reputation authentication request carries a target service identifier of a requested reputation service and reputation data to be authenticated, the reputation data to be authenticated is the experience data of the target account in the real world, the reputation authentication request is a request to authenticate the experience data of the target account in the real world, and the reputation service is a service to authenticate the experience data of the target account in the real world;

[0012] A matching module, used for querying whether there is a target registered reputation service matching the target service identifier in the registered reputation service, the registered reputation service being obtained based on a registration request of the certification authority account to the reputation service;

[0013] A contract acquisition module, used to acquire a corresponding target resolution contract based on the reputation resolution contract information in the target registered reputation service if there is a target registered reputation service matching the target service identifier;

[0014] The data authentication module is used to call the target resolution contract to authenticate the reputation data to be authenticated based on the data source information in the target registered reputation service, so as to obtain the authentication result corresponding to the reputation authentication request.

[0015] In a third aspect, the present application further provides a computer device. The computer device includes a memory and a processor, the memory stores a computer program, and the processor implements the following steps when executing the computer program:

[0016] Receive a reputation authentication request sent by a target account, the reputation authentication request carries a target service identifier of a requested reputation service and reputation data to be authenticated, the reputation data to be authenticated is the experience data of the target account in the real world, the reputation authentication request is a request to authenticate the experience data of the target account in the real world, and the reputation service is a service to authenticate the experience data of the target account in the real world;

[0017] Querying whether there is a target registered reputation service matching the target service identifier in the registered reputation service, where the registered reputation service is obtained based on a registration request to the reputation service by the certification authority account;

[0018] If there is a target registered reputation service that matches the target service identifier, obtain the corresponding target resolution contract based on the reputation resolution contract information in the target registered reputation service;

[0019] Based on the data source information in the target registered reputation service, the target resolution contract is called to authenticate the reputation data to be authenticated to obtain the authentication result corresponding to the reputation authentication request.

[0020] In a fourth aspect, the present application further provides a computer-readable storage medium. The computer-readable storage medium stores a computer program, and when the computer program is executed by a processor, the following steps are implemented:

[0021] Receive a reputation authentication request sent by a target account, the reputation authentication request carries a target service identifier of a requested reputation service and reputation data to be authenticated, the reputation data to be authenticated is the experience data of the target account in the real world, the reputation authentication request is a request to authenticate the experience data of the target account in the real world, and the reputation service is a service to authenticate the experience data of the target account in the real world;

[0022] Querying whether there is a target registered reputation service matching the target service identifier in the registered reputation service, where the registered reputation service is obtained based on a registration request to the reputation service by the certification authority account;

[0023] If there is a target registered reputation service that matches the target service identifier, obtain the corresponding target resolution contract based on the reputation resolution contract information in the target registered reputation service;

[0024] Based on the data source information in the target registered reputation service, the target resolution contract is called to authenticate the reputation data to be authenticated to obtain the authentication result corresponding to the reputation authentication request.

[0025] In a fifth aspect, the present application further provides a computer program product. The computer program product includes a computer program, and when the computer program is executed by a processor, the following steps are implemented:

[0026] Receive a reputation authentication request sent by a target account, the reputation authentication request carries a target service identifier of a requested reputation service and reputation data to be authenticated, the reputation data to be authenticated is the experience data of the target account in the real world, the reputation authentication request is a request to authenticate the experience data of the target account in the real world, and the reputation service is a service to authenticate the experience data of the target account in the real world;

[0027] Querying whether there is a target registered reputation service matching the target service identifier in the registered reputation service, where the registered reputation service is obtained based on a registration request to the reputation service by the certification authority account;

[0028] If there is a target registered reputation service that matches the target service identifier, obtain the corresponding target resolution contract based on the reputation resolution contract information in the target registered reputation service;

[0029] Based on the data source information in the target registered reputation service, the target resolution contract is called to authenticate the reputation data to be authenticated to obtain the authentication result corresponding to the reputation authentication request.

[0030] The above-mentioned data processing method, device, computer equipment, storage medium and computer program product based on blockchain receive a reputation authentication request sent by a target account. The reputation authentication request carries the target service identifier of the requested reputation service and the reputation data to be authenticated. The reputation data to be authenticated is the experience data of the target account in the real world. The reputation authentication request is a request to authenticate the experience data of the target account in the real world. The reputation service is a service for authenticating the experience data of the target account in the real world. Then, it queries whether there is a target registered reputation service that matches the target service identifier in the registered reputation service. The registered reputation service is obtained based on the registration request of the certification agency account for the reputation service. If there is a target registered reputation service that matches the target service identifier, the corresponding target resolution contract is obtained based on the reputation resolution contract information in the target registered reputation service. Finally, based on the data source information in the target registered reputation service, the target resolution contract is called to authenticate the reputation data to be authenticated to obtain the authentication result corresponding to the reputation authentication request. That is, the certification agency account registers the reputation service in the blockchain to obtain a registered reputation service. Then, when the target account uses the target service identifier and the reputation data to be authenticated to perform reputation authentication in the blockchain, the reputation resolution contract information and data source information in the target registered reputation service matched by the target service identifier are used to authenticate the reputation data to be authenticated, thereby obtaining the authentication result corresponding to the reputation authentication request. That is, the corresponding reputation service is registered in the blockchain through the certification agency account, so that the blockchain can realize universal reputation authentication without the need for authentication in different evidence storage systems, thereby improving the convenience of reputation authentication and reducing the data interoperability cost of reputation authentication. BRIEF DESCRIPTION OF THE DRAWINGS

[0031] Figure 1 This is an application environment diagram of a data processing method based on blockchain in one embodiment;

[0032] Figure 2 A flowchart of a data processing method based on blockchain in one embodiment;

[0033] Figure 3 A schematic diagram of a process for obtaining a target parsing contract in an embodiment;

[0034] Figure 4 A schematic diagram of a data authentication process in one embodiment;

[0035] Figure 5 A schematic diagram of a process for generating a reputation certificate in one embodiment;

[0036] Figure 6 A flowchart of reputation authentication in a specific embodiment;

[0037] Figure 7 A schematic diagram of a process of revoking reputation authentication in one embodiment;

[0038] Figure 8 A schematic diagram of a process of reputation service registration in one embodiment;

[0039] Fig. 9 A schematic diagram of a process of reputation service registration in a specific embodiment;

[0040] Fig.10 It is a flowchart of a data processing method based on blockchain in a specific embodiment;

[0041] Fig.11 It is a schematic diagram of the overall architecture of reputation authentication based on the alliance chain in a specific embodiment;

[0042] Fig.12 It is a structural block diagram of a data processing device based on blockchain in one embodiment;

[0043] Fig.13 is an internal structure diagram of a computer device in one embodiment;

[0044] Fig.14 FIG. 4 is a diagram showing the internal structure of a computer device in one embodiment. DETAILED DESCRIPTION

[0045] In order to make the purpose, technical solution and advantages of the present application more clearly understood, the present application is further described in detail below in conjunction with the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are only used to explain the present application and are not used to limit the present application.

[0046] Blockchain is a new application model of computer technologies such as distributed data storage, peer-to-peer transmission, consensus mechanism, encryption algorithm, etc. Blockchain is essentially a decentralized database, a string of data blocks generated by cryptographic methods. Each data block contains a batch of network transaction information, which is used to verify the validity of its information (anti-counterfeiting) and generate the next block. Blockchain can include the underlying blockchain platform, platform product service layer, and application service layer.

[0047] The underlying blockchain platform can include processing modules such as user management, basic services, smart contracts, and operations. Among them, the user management module is responsible for the identity information management of all blockchain participants, including maintaining the generation of public and private keys (account management), key management, and the maintenance of the correspondence between the user's real identity and the blockchain address (authority management), etc., and, under authorization, supervises and audits the transactions of certain real identities and provides risk control rule configuration (risk control audit); the basic service module is deployed on all blockchain node devices to verify the validity of business requests, and records valid requests to storage after consensus is reached. For a new business request, the basic service first performs interface adaptation analysis and authentication processing (interface adaptation), and then encrypts the business information through the consensus algorithm (consensus Management), after encryption, it is completely and consistently transmitted to the shared ledger (network communication), and recorded and stored; the smart contract module is responsible for the registration and issuance of contracts, as well as contract triggering and contract execution. Developers can define the contract logic in a certain programming language and publish it to the blockchain (contract registration). According to the logic of the contract terms, the key or other event trigger execution is called to complete the contract logic. At the same time, it also provides the function of contract upgrade and cancellation; the operation module is mainly responsible for the deployment, configuration modification, contract setting, cloud adaptation and real-time status visualization output of the product during the product release process, such as prompts, network status detection, node equipment health status detection, etc. The platform product service layer provides the basic capabilities and implementation framework of typical applications. Developers can complete the blockchain implementation of business logic based on these basic capabilities and superimpose business characteristics. The application service layer provides application services based on blockchain solutions for business participants to use.

[0048] The blockchain-based data processing method provided in the embodiments of the present application can be applied to Figure 1In the application environment shown. Among them, the blockchain node 102 in the blockchain communicates with the target account terminal 104 through the network, and the node in the blockchain communicates with the certification agency account terminal 106 through the network. The target account terminal 104 and the certification agency account terminal 106 can be blockchain nodes in the blockchain or service terminals outside the blockchain. The blockchain node 102 can be any node in the blockchain. The blockchain node can be on a terminal, on a server, or on a cloud or other server. The blockchain node 102 receives a reputation authentication request sent by the target account through the target account terminal 104. The reputation authentication request carries the target service identifier of the requested reputation service and the reputation data to be authenticated. The reputation data to be authenticated is the experience data of the target account in the real world. The reputation authentication request is a request to authenticate the experience data of the target account in the real world. The reputation service is a service to authenticate the experience data of the target account in the real world. The blockchain node 102 queries whether there is a target registered reputation service matching the target service identifier in the registered reputation service. The registered reputation service is obtained based on the registration request of the certification authority account to the reputation service through the certification authority account terminal 106. If there is a target registered reputation service matching the target service identifier, the blockchain node 102 obtains the corresponding target resolution contract based on the reputation resolution contract information in the target registered reputation service. The blockchain node 102 calls the target resolution contract to authenticate the reputation data to be authenticated based on the data source information in the target registered reputation service to obtain the authentication result corresponding to the reputation authentication request. Finally, the blockchain 102 can return the authentication result corresponding to the reputation authentication request to the target account terminal 102. The target account end can be a terminal or a server, the certification authority account end can be a terminal or a server, and the blockchain node can be a terminal or a server. The terminal can be, but is not limited to, various desktop computers, laptops, smart phones, tablet computers, IoT devices, and portable wearable devices. IoT devices can be smart speakers, smart TVs, smart air conditioners, smart car devices, etc. Portable wearable devices can be smart watches, smart bracelets, head-mounted devices, etc. The server can be implemented as an independent server or a server cluster consisting of multiple servers.

[0049] In one embodiment, Figure 2 As shown, a data processing method based on blockchain is provided, which is applied to Figure 1 The blockchain node in is used as an example to illustrate, including the following steps:

[0050] S202, receiving a reputation authentication request sent by a target account, the reputation authentication request carries a target service identifier of a requested reputation service and reputation data to be authenticated, the reputation data to be authenticated is the experience data of the target account in the real world, the reputation authentication request is a request to authenticate the experience data of the target account in the real world, and the reputation service is a service to authenticate the experience data of the target account in the real world.

[0051] Among them, the target account refers to an account that can use the blockchain. The target account is an immutable data field that can be used to represent the corresponding user. The target account can be an account address, etc. The target account is created in advance through the blockchain. The target service identifier refers to the reputation service identifier corresponding to the reputation service for which reputation data authentication is to be performed. The reputation service identifier is used to uniquely identify the corresponding reputation service and can be a string, name, address, etc. The real world refers to the objective world that exists outside the human brain. Things and their mutual connections are in the real world. It is a perceptible world. The experience data of the real world refers to the data generated after the objects in the real world interact with the real world. It can be the data of events that the objects in the real world have seen, done or encountered. For example, the experience data of the real world can be academic data, identity data, work experience data, education experience data, internship experience data, project experience data, social practice experience data, etc. Reputation authentication refers to the authentication of the experience data of the target account in the real world. This authentication is a form of credit guarantee. According to the definition of the International Organization for Standardization (ISO) and the International Electrotechnical Commission (IEC), it refers to the conformity assessment activities by nationally recognized certification bodies to prove that an organization's products, services, and management systems comply with relevant standards, technical specifications (TS) or their mandatory requirements. That is, by authenticating the experience data, the experience data can generate certification information, which indicates the validity and correctness of the experience data of the target account in the real world.

[0052] Specifically, the blockchain node receives the reputation authentication request sent by the target account through the target account end, parses the reputation authentication request, and obtains the target service identifier and the reputation data to be authenticated. Among them, the target account end can pre-create a server end using the blockchain. Then, when the reputation data needs to be authenticated, the reputation authentication request can be sent to the blockchain through the target account end using the target account.

[0053] In one embodiment, when multiple blockchains are deployed, the reputation authentication request may also carry a blockchain identifier, which is used to uniquely identify the corresponding specific blockchain. Then, the blockchain to be sent is found according to the blockchain identifier, and the reputation authentication request is sent to the blockchain corresponding to the blockchain identifier according to the address information of the blockchain, so that the blockchain node in the blockchain where the reputation service is deployed receives the reputation authentication request sent by the target account, thereby ensuring the accuracy of the blockchain that receives the reputation authentication request.

[0054] S204, querying whether there is a target registered reputation service matching the target service identifier in the registered reputation services, where the registered reputation service is obtained based on a registration request for the reputation service by the certification authority account.

[0055] Among them, the registered reputation service is obtained based on the registration request of the certification agency account for the reputation service, and is a reputation service that has been successfully registered in the blockchain, that is, a reputation service that the blockchain can provide. Different types of reputation data require different certification agencies to authenticate. At this time, the reputation service of each type of reputation data can register the corresponding reputation service in the blockchain through the corresponding certification agency, and the blockchain authenticates the corresponding type of reputation data through the registered reputation service. For example, an education certification agency can register a reputation service for authenticating academic data in the blockchain, and then students or other personnel can authenticate the academic data submitted by students or other personnel through the reputation service for authenticating academic data in the blockchain. For example, a work experience certification agency can register a reputation service for authenticating work experience data in the blockchain, and then staff or other personnel can authenticate the work experience data submitted by staff or other personnel through the reputation service for authenticating work experience data in the blockchain. An identity certification agency can register a reputation service for authenticating identity data in the blockchain, and then the submitted identity data can be authenticated through the reputation service for authenticating identity data in the blockchain. The certification agency account refers to the account created by the certification agency in the blockchain. Reputation service refers to the service for authenticating reputation data, and different types of reputation data have different corresponding reputation services.

[0056] Specifically, the blockchain node queries whether there is a target registered reputation service that matches the target service identifier in the registered reputation service. When the blockchain node receives a registration request for the reputation service from the certification authority account, it registers the reputation service. After the registration is successful, the reputation service and the corresponding reputation service identifier are obtained, and then the reputation service and the corresponding reputation service identifier are associated and saved in the blockchain. That is, the blockchain stores the association relationship between each reputation service and the corresponding reputation service identifier. When the blockchain node obtains the target service identifier, it searches for whether there is a reputation service identifier that is the same as the target service identifier in the association relationship between the reputation service and the reputation service identifier stored in the blockchain. When the same reputation service identifier is found, it indicates that there is a target registered reputation service that matches the target service identifier in the blockchain. At this time, the blockchain node performs subsequent reputation data authentication. When the same reputation service identifier is not found, it indicates that there is no target registered reputation service that matches the target service identifier in the blockchain. At this time, the blockchain node generates a prompt message that the certification service corresponding to the reputation data is not registered, and returns the prompt message that the certification service is not registered to the target account end for prompting.

[0057] S206: If there is a target registered reputation service that matches the target service identifier, obtain the corresponding target resolution contract based on the reputation resolution contract information in the target registered reputation service.

[0058] Among them, reputation resolution contract information refers to the information that can obtain the target resolution contract, which can be the address of the target resolution contract, that is, the storage address of the target resolution contract in the blockchain, and the storage address can be the address of the stored block. Data source information refers to the information where the data for verifying reputation data is located. The data source information can be stored in the blockchain or outside the blockchain. The target resolution contract refers to the smart contract that verifies the reputation data to be authenticated. The target resolution contract can be provided by the certification agency account and deployed to the blockchain when registering for the reputation service.

[0059] Specifically, the target registered reputation service in the blockchain includes reputation resolution contract information and data source information. When the blockchain node determines that there is a target registered reputation service matching the target service identifier in the blockchain, the reputation resolution contract information and data source information included in the target registered reputation service matching the target service identifier are obtained. Then, the reputation resolution contract information in the target registered reputation service is used to obtain the corresponding target resolution contract.

[0060] S208, based on the data source information in the target registered reputation service, calling the target resolution contract to authenticate the reputation data to be authenticated, so as to obtain the authentication result corresponding to the reputation authentication request.

[0061] The authentication result is used to indicate whether the reputation data to be authenticated has been authenticated, and the authentication result includes an authentication failure result and an authentication success result. The authentication success result is used to indicate whether the reputation data to be authenticated is valid or correct, and the authentication success result is used to indicate whether the reputation data to be authenticated is invalid or incorrect.

[0062] Specifically, the blockchain node calls the target resolution contract to authenticate the reputation data to be authenticated according to the data source information in the target registered reputation service. The target resolution contract obtains the registered reputation data verification information according to the data source information in the target registered reputation service, and then uses the registered reputation data verification information to verify the reputation data to be authenticated, wherein the reputation data verification information is information used to verify the reputation data, which can be the signature of the reputation data, the reputation data itself, etc. When the reputation data to be authenticated is verified using the registered reputation data verification information, the authentication result corresponding to the reputation authentication request is successful authentication. When the reputation data to be authenticated fails to be verified using the registered reputation data verification information, the authentication result corresponding to the reputation authentication request is unsuccessful authentication.

[0063] The above-mentioned data processing method, device, computer equipment, storage medium and computer program product based on blockchain receive a reputation authentication request sent by a target account. The reputation authentication request carries the target service identifier of the requested reputation service and the reputation data to be authenticated. The reputation data to be authenticated is the experience data of the target account in the real world. The reputation authentication request is a request to authenticate the experience data of the target account in the real world. The reputation service is a service for authenticating the experience data of the target account in the real world. Then, it queries whether there is a target registered reputation service that matches the target service identifier in the registered reputation service. The registered reputation service is obtained based on the registration request of the certification agency account for the reputation service. If there is a target registered reputation service that matches the target service identifier, the corresponding target resolution contract is obtained based on the reputation resolution contract information in the target registered reputation service. Finally, based on the data source information in the target registered reputation service, the target resolution contract is called to authenticate the reputation data to be authenticated to obtain the authentication result corresponding to the reputation authentication request. That is, the certification agency account registers the reputation service in the blockchain to obtain a registered reputation service. Then, when the target account uses the target service identifier and the reputation data to be authenticated to perform reputation authentication in the blockchain, the reputation resolution contract information and data source information in the target registered reputation service matched by the target service identifier are used to authenticate the reputation data to be authenticated, thereby obtaining the authentication result corresponding to the reputation authentication request. That is, the corresponding reputation service is registered in the blockchain through the certification agency account, so that the blockchain can realize universal reputation authentication without the need for authentication in different evidence storage systems, thereby improving the convenience of reputation authentication and reducing the data interoperability cost of reputation authentication.

[0064] In one embodiment, the reputation resolution contract information includes the reputation resolution contract address, and the data source information includes the data source type and the corresponding verification data storage address;

[0065] like Figure 3 As shown, S206, based on the reputation resolution contract information in the target registered reputation service, obtain the corresponding target resolution contract, including:

[0066] S302, verifying whether there is a corresponding reputation resolution contract address in the target registered reputation service, and when the corresponding reputation resolution contract address exists in the target registered reputation service, querying the corresponding target resolution contract based on the reputation resolution contract address;

[0067] S304, when the target resolution contract is queried, check whether the corresponding data source information exists in the target registered reputation service.

[0068] Among them, the reputation resolution contract address is used to represent the deployment address of the corresponding target resolution contract in the blockchain. The target resolution contract is a smart contract used to resolve and authenticate reputation data. The target resolution contract is provided by the certification agency account end, that is, the certification agency account end can deploy the target resolution contract to the blockchain when registering for the reputation service.

[0069] Specifically, the blockchain node verifies whether there is a corresponding reputation resolution contract address in the target registered reputation service, that is, the blockchain node can search the blockchain to find whether the target registered reputation service is associated with a corresponding reputation resolution contract address. When the association relationship between the target registered reputation service and the reputation resolution contract address is found, it indicates that the corresponding reputation resolution contract address exists in the target registered reputation service. When the association relationship between the target registered reputation service and the reputation resolution contract address is not found, it indicates that the corresponding reputation resolution contract address does not exist in the target registered reputation service. At this time, the blockchain node generates a prompt message of verification failure, and returns the prompt message of verification failure to the target account end corresponding to the target account. The prompt message of verification failure can be information used to prompt that the reputation resolution contract address corresponding to the target registered reputation service does not exist in the blockchain.

[0070] Then the blockchain node determines that when the corresponding reputation resolution contract address exists in the target registered reputation service, it then verifies whether a smart contract is deployed at the reputation resolution contract address. At this time, the blockchain node queries the corresponding target resolution contract in the blockchain according to the reputation resolution contract address. When the blockchain node finds the target resolution contract at the reputation resolution contract address in the blockchain, it indicates that the target resolution contract is deployed in the blockchain. When the blockchain node does not find the corresponding target resolution contract at the reputation resolution contract address in the blockchain, it indicates that the corresponding target resolution contract is not deployed in the blockchain, or the reputation resolution contract address provided is incorrect. At this time, the blockchain node generates a prompt message of contract verification failure, and returns the prompt message of contract verification failure to the target account end corresponding to the target account. The prompt message of contract verification failure can be information used to prompt that the corresponding target resolution contract is not deployed in the blockchain.

[0071] S306, when the corresponding data source information exists in the target registered reputation service, verify the validity of the data source information according to the data source type in the data source information and the corresponding verification data storage address;

[0072] S308, when the validity of the data source information is verified, the corresponding target resolution contract is obtained based on the reputation resolution contract address.

[0073] The validity of the data source information is used to indicate whether the data source information can be accessed normally.

[0074] Specifically, the blockchain node determines that when the corresponding data source information exists in the target registered reputation service, the validity of the data source information is verified according to the data source type in the data source information and the corresponding verification data storage address. When the data source type in the data source information is an on-chain data type, the blockchain node determines whether the on-chain verification information storage address corresponding to the on-chain data type exists, and verifies whether the on-chain verification information storage address stores the corresponding verification information. When the on-chain verification information storage address exists and stores the corresponding verification information, the validity verification of the data source information passes. When the on-chain verification information storage address does not exist or does not store the corresponding verification information, the validity verification of the data source information fails. When the data source type in the data source information is an off-chain data source type, the blockchain node determines whether the signature verification information storage address corresponding to the off-chain data source type can be accessed, and verifies whether the signature verification information storage address stores the corresponding verification information. When the signature verification information storage address can be accessed and stores the corresponding verification information, the validity verification of the data source information passes. When the signature verification information storage address cannot be accessed or does not store the corresponding verification information, the validity verification of the data source information fails. The blockchain determines that when the validity of the data source information is verified, the corresponding target resolution contract is obtained based on the reputation resolution contract address.

[0075] In the above embodiment, by verifying whether there is a corresponding reputation resolution contract address in the target registered reputation service, when there is a corresponding reputation resolution contract address in the target registered reputation service, the corresponding target resolution contract is queried based on the reputation resolution contract address, and when the target resolution contract is queried, it is verified whether there is corresponding data source information in the target registered reputation service, and when there is corresponding data source information in the target registered reputation service, the validity of the data source information is verified according to the data source type in the data source information and the corresponding verification data storage address, and when the validity of the data source information is verified, the corresponding target resolution contract is obtained based on the reputation resolution contract address. That is, the reputation resolution contract address and data source information in the target registered reputation service are verified, and authentication is performed after the verification is passed, avoiding direct use of the target registered reputation service for authentication, preventing errors in the target registered reputation service, reducing the consumption of service resources, saving service resources, and ensuring the normal operation of authentication.

[0076] In one embodiment, the data source information includes the off-chain data source type and the corresponding signature verification information storage address;

[0077] like Figure 4 As shown, S208, based on the data source information in the target registered reputation service, calling the target resolution contract to authenticate the reputation data to be authenticated includes:

[0078] S402, based on the off-chain data source type, the signature data to be authenticated is obtained from the reputation data to be authenticated. The signature data to be authenticated is obtained from the certification agency account end corresponding to the certification agency account. The certification agency account end corresponding to the certification agency account digitally signs the experience data of the target account in the real world to obtain the signature data to be authenticated.

[0079] The off-chain data source type refers to the type of data stored in the blockchain after being digitally signed by the target account's real-world experience data. The signature data to be authenticated can be obtained by digitally signing the target account's real-world experience data using a digital signature algorithm, and the digital signature algorithm can be an asymmetric digital signature algorithm, a symmetric digital signature algorithm, an elliptic curve digital signature algorithm, and the like.

[0080] Specifically, when the blockchain node obtains the data source information in the target registered reputation service and then determines that the data source type in the original data information is an off-chain data source type, it indicates that the verification data of the target registered reputation service is that the target registered reputation service of the off-chain data source type does not store the target account's experience data in the real world in the blockchain, and the target registered reputation service of the off-chain data source type stores the digital signature of the target account's experience data in the real world in the blockchain, thereby avoiding the leakage of private data and improving the security of private data. The blockchain node obtains the signature data to be authenticated from the reputation data to be authenticated according to the off-chain data source type in the data source information. In one embodiment, the reputation authentication request received by the blockchain node may also directly carry the signature data to be authenticated, and the signature data to be authenticated is directly obtained by parsing the reputation authentication request.

[0081] S404, calling the target parsing contract to search for signature information matching the signature data to be authenticated in the storage space corresponding to the signature verification information storage address;

[0082] S406, when signature information matching the signature data to be authenticated is found, it is determined that the authentication of the reputation data to be authenticated is successful; when signature information matching the signature data to be authenticated is not found, it is determined that the authentication of the reputation data to be authenticated is failed.

[0083] The signature verification information storage address refers to the block address of the signature information stored in the blockchain for verifying the digital signature. The signature information refers to the digital signature of the target account's real-world experience data pre-stored in the blockchain.

[0084] Specifically, the blockchain node calls the target parsing contract to search for signature information that matches the signature data to be authenticated in the storage space corresponding to the signature verification information storage address, that is, to match the signature information stored in the block corresponding to the signature verification information storage address with the signature data to be authenticated. When signature information consistent with the signature data to be authenticated is found, it means that the signature data to be authenticated is the signature data provided by the certification agency's account end. At this time, the blockchain node determines that the reputation data to be authenticated has passed the authentication. When signature information matching the signature data to be authenticated is not found, it means that the signature data to be authenticated is not the signature data provided by the certification agency's account end, that is, the signature data is incorrect. At this time, it is determined that the authentication of the reputation data to be authenticated has failed.

[0085] In the above embodiment, the signature data to be authenticated is obtained from the reputation data to be authenticated according to the off-chain data source type, and then the target parsing contract is called to search for signature information matching the signature data to be authenticated in the storage space corresponding to the signature verification information storage address. When the signature information matching the signature data to be authenticated is found, it is determined that the authentication of the reputation data to be authenticated is passed. When the signature information matching the signature data to be authenticated is not found, it is determined that the authentication of the reputation data to be authenticated fails. That is, by using the signature data to be authenticated and the signature verification information to authenticate the reputation data, it is possible to avoid writing the experience data of the target account in the real world into the blockchain, thereby avoiding the leakage of private data and improving the security of private data.

[0086] In one embodiment, the data source information includes the on-chain data source type and the corresponding on-chain verification information storage address;

[0087] S208, i.e., based on the data source information in the target registered reputation service, calling the target resolution contract to authenticate the reputation data to be authenticated, including the steps of:

[0088] Based on the on-chain data source type, the target parsing contract is called to search for reputation data matching the reputation data to be authenticated in the storage block corresponding to the on-chain verification information storage address; when reputation data matching the reputation data to be authenticated is found in the storage block corresponding to the on-chain verification information storage address, it is determined that the authentication of the reputation data to be authenticated is successful; when reputation data matching the reputation data to be authenticated is not found in the storage block corresponding to the on-chain verification information storage address, it is determined that the authentication of the reputation data to be authenticated has failed.

[0089] Among them, the on-chain data source type refers to the type in which the target account's experience data in the real world is directly stored in the blockchain. For example, when an educational institution can provide academic certification services through the blockchain, the corresponding academic degree number can be directly stored in the blockchain. The on-chain verification information storage address refers to the block address of the target account's experience data in the real world stored in the blockchain.

[0090] Specifically, the blockchain node searches for reputation data that matches the reputation data to be authenticated in the storage block corresponding to the on-chain verification information storage address through the target resolution contract according to the on-chain data source type. For example, it can verify that the reputation data to be authenticated is consistent with the various reputation data stored in the storage block. When there is consistent reputation data in the storage block, it means that the reputation data that matches the reputation data to be authenticated is found in the storage block. At this time, it is determined that the reputation data to be authenticated has been authenticated. When all the reputation data stored in the storage block are inconsistent with the reputation data to be authenticated, it means that the reputation data that matches the reputation data to be authenticated is not found in the storage block. At this time, it is determined that the reputation data to be authenticated has not been authenticated. Among them, the target resolution contract can parse the reputation data to be authenticated from the reputation authentication request, and the data format of the reputation data to be authenticated obtained by the parsing is consistent with the data format of the reputation data stored in the blockchain.

[0091] In the above embodiment, the target parsing contract is called through the on-chain data source type to search for reputation data matching the reputation data to be authenticated in the storage block corresponding to the on-chain verification information storage address. That is, the reputation data stored in the blockchain can be directly used for authentication, thereby improving the convenience and efficiency of authentication.

[0092] In one embodiment, Figure 5 As shown, S208, that is, after invoking the target resolution contract to authenticate the reputation data to be authenticated based on the data source information in the target registered reputation service to obtain the authentication result corresponding to the reputation authentication request, further includes:

[0093] S502, when the authentication result corresponding to the reputation authentication request is that the reputation data to be authenticated is authenticated, calling the reputation certification generation contract;

[0094] S504, generating a reputation certificate for the reputation authentication request and an authenticated identifier corresponding to the reputation certificate through a reputation certificate generation contract;

[0095] S506, the reputation certificate, the authenticated identifier and the reputation data to be authenticated are associated and stored in the blockchain, and the authenticated identifier is returned to the request end corresponding to the reputation authentication request.

[0096] Among them, the reputation proof generation contract refers to a smart contract used to generate an authentication proof corresponding to the reputation data. The reputation proof refers to the proof that the reputation data to be authenticated has passed the authentication, which can be the authentication success information. The authenticated identifier refers to the unique identifier used to uniquely identify the reputation proof, which can be a string, a number, a name, etc. For example, the authenticated identifier can be the hash value of the reputation proof, the authenticated identifier can be the timestamp of the reputation proof, etc.

[0097] Specifically, a reputation proof generation contract is pre-deployed in the blockchain, and a proof of the reputation data that has been authenticated can be generated through the reputation proof generation contract. That is, when the blockchain node determines that the authentication result corresponding to the reputation authentication request is that the reputation data to be authenticated has been authenticated, it obtains the pre-set reputation proof generation contract address, and calls the corresponding reputation proof generation contract according to the reputation proof generation contract address. The reputation proof generation contract generates a reputation proof for the reputation authentication request and an authenticated identifier corresponding to the reputation proof, wherein the reputation proof generation contract generates a reputation proof for the reputation authentication request, and then generates an authenticated identifier corresponding to the reputation proof, wherein the hash value corresponding to the reputation proof can be calculated by a hash value algorithm, and the hash value can be used as the authenticated identifier, or a random number generator can be used to generate a unique identifier, and the unique identifier can be used as the authenticated identifier corresponding to the reputation proof. Finally, the blockchain node associates the reputation proof, the authenticated identifier, and the reputation data to be authenticated and stores them in the blockchain, and returns the authenticated identifier to the request end corresponding to the reputation authentication request.

[0098] In one embodiment, when a blockchain node detects that the reputation data to be authenticated has been authenticated, it returns a prompt message of authentication success to the target account, and then receives a proof generation request sent by the target account. The blockchain node receives the proof generation request, and in response to the proof generation request, calls the reputation proof generation contract to generate a reputation proof for the reputation authentication request and an authenticated identifier corresponding to the reputation proof.

[0099] In one embodiment, reputation certificates for different reputation authentication requests and authenticated identifiers corresponding to different reputation certificates can be generated in the blockchain node. The blockchain provides authentication of various reputation services, such as academic certification services, work experience certification services, educational experience certification services, identity authentication services, project experience certification services, and the like. The various reputation services are registered in advance by the corresponding certification agencies in the blockchain. For example, the academic certification agency pre-registers the corresponding academic certification service in the blockchain, so that the corresponding students or other personnel can authenticate the students' academic data through the academic certification service in the blockchain, and obtain the academic certification identifier that has passed the academic data authentication. Similarly, other certification agencies can also pre-register the corresponding reputation services in the blockchain and provide corresponding reputation services through the blockchain.

[0100] In the above embodiment, when the authentication result corresponding to the reputation authentication request is that the reputation data to be authenticated is authenticated, the reputation proof generation contract is called; a reputation proof for the reputation authentication request and an authenticated identifier corresponding to the reputation proof are generated through the reputation proof generation contract; the reputation proof, the authenticated identifier and the reputation data to be authenticated are associated and stored in the blockchain, and the authenticated identifier is returned to the request end corresponding to the reputation authentication request, that is, the reputation proof and the corresponding authenticated identifier are generated through the reputation proof generation contract, thereby improving the accuracy of the reputation proof and the corresponding authenticated identifier.

[0101] In one embodiment, after S506, that is, after the reputation certificate, the authenticated identifier, and the reputation data to be authenticated are associated and stored in the blockchain, the following steps are further included:

[0102] Receive a verification request for the reputation data to be verified, the verification request includes the reputation data to be verified and the authenticated identifier to be verified corresponding to the reputation data to be verified; search for the target authenticated identifier associated with the reputation data to be verified in the blockchain; when the target authenticated identifier is consistent with the authenticated identifier to be verified, obtain a verification result of the reputation data to be verified, and return the verification result of the reputation data to be verified to the request end corresponding to the verification request. When the target authenticated identifier is inconsistent with the authenticated identifier to be verified, obtain a verification failure result of the reputation data to be verified, and return the verification failure result of the reputation data to be verified to the request end corresponding to the verification request.

[0103] The reputation data to be verified refers to the reputation data that needs to be verified for authentication. The authenticated identifier to be verified refers to the authenticated identifier that needs to be verified for authentication. The target authenticated identifier refers to the authenticated identifier associated with the reputation data to be verified stored in the blockchain.

[0104] Specifically, the blockchain node receives a verification request for the reputation data to be verified, and the verification request can be sent by any account in the blockchain. Then the blockchain node parses the verification request to obtain the reputation data to be verified and the authenticated identifier to be verified corresponding to the reputation data to be verified. Then the blockchain node searches for the target authenticated identifier associated with the reputation data to be verified in the blockchain. When the target authenticated identifier associated with the reputation data to be verified is not found, it indicates that the reputation data to be verified is unauthenticated reputation data. At this time, a prompt message indicating that the verification failed is generated, and the prompt message is returned to the request end corresponding to the verification request. When the target authenticated identifier associated with the reputation data to be verified is found, it indicates that the reputation data to be verified is authenticated reputation data. At this time, the blockchain node determines whether the target authenticated identifier is consistent with the authenticated identifier to be verified. When the target authenticated identifier is not consistent with the authenticated identifier to be verified, a verification failure result of the reputation data to be verified is obtained, and the verification failure result of the reputation data to be verified is returned to the request end corresponding to the verification request. When the target authenticated identifier is consistent with the authenticated identifier to be verified, a verification pass result of the reputation data to be verified is obtained, and the verification pass result of the reputation data to be verified is returned to the request end corresponding to the verification request.

[0105] In one embodiment, the blockchain node can match the authenticated identifier to be verified with each authenticated identifier stored in the blockchain for consistency. When a consistent authenticated identifier is matched, a verification pass result of the reputation data to be verified is obtained; when a consistent authenticated identifier is not matched, a verification failure result of the reputation data to be verified is obtained.

[0106] In the above embodiment, by receiving a verification request and using the authenticated identifier to be verified in the verification request and the target authenticated identifier associated with the reputation data to be verified to perform consistency judgment, it is possible to quickly determine whether the reputation data to be verified has passed the authentication, thereby improving the efficiency of authentication.

[0107] In a specific embodiment, Figure 6As shown, a flow chart of reputation authentication is provided. Specifically, the blockchain node obtains a reputation authentication request, which carries the input blockchain ID (identification number), the reputation service identifier and the reputation data to be authenticated. Then the blockchain node searches for the corresponding reputation service according to the reputation service identifier. When the corresponding reputation service does not exist, a prompt message that the reputation service does not exist is returned, and the process ends. When the corresponding reputation service exists, it is determined whether the reputation service has a corresponding target resolution contract, which can be determined according to the resolution contract address in the reputation service. When the corresponding target resolution contract does not exist, a prompt message of authentication failure is returned, and the process ends. When the corresponding target resolution contract exists, it is determined whether the reputation service is not an on-chain data source type. When the reputation service is an on-chain data source type, it is determined whether the on-chain verification information storage address exists. When the on-chain verification information storage address does not exist, a prompt message of authentication failure is returned, and the process ends. When the on-chain verification information storage address exists, the data of the on-chain verification information storage address is further verified to be valid. When the verification fails, a prompt message of authentication failure is returned, and the process ends. When the verification passes, the reputation proof generation contract is used to generate the corresponding reputation proof, and the authentication result is returned, prompting the user that the reputation proof has been successfully generated. When the reputation service is an off-chain data source type, the certification agency account needs to digitally sign the experience data and write it into the blockchain during registration. Then the blockchain node needs to verify the validity of the signature information of the blockchain. When the validity verification of the signature information of the blockchain passes, the reputation proof generation contract is used to generate the corresponding reputation proof, and the authentication result is returned, prompting the user that the reputation proof has been successfully generated, so that the blockchain can realize universal reputation authentication, without the need for authentication in different evidence storage systems, improving the convenience of reputation authentication and reducing the data interoperability cost of reputation authentication.

[0108] In one embodiment, the target registered reputation service also includes a reputation certification revocation flag; Figure 7 As shown, the data processing method based on blockchain also includes:

[0109] S702, receiving a certification revocation request for the reputation data to be authenticated, the certification revocation request carrying an authenticated identifier and a target service identifier corresponding to the reputation data to be authenticated;

[0110] S704, when it is detected that there is a reputation certificate revocation identifier in the registered reputation service corresponding to the target service identifier, calling the reputation certificate generation contract;

[0111] S706, generating a reputation revocation certificate for the reputation certificate corresponding to the authenticated identifier through a reputation certificate generation contract;

[0112] S708, the reputation revocation certificate, the authenticated identifier and the reputation data to be authenticated are associated and stored in the blockchain, and the reputation revocation certificate is returned to the requesting end corresponding to the certificate revocation request.

[0113] Among them, the reputation certificate revocation flag is an flag used to indicate that the reputation certificate generated by the corresponding reputation service can be revoked. The reputation certificate revocation flag included in the reputation service is set when the reputation service is registered. The certificate revocation request is a request to revoke the reputation certificate. The reputation revocation certificate refers to the revocation certificate corresponding to the reputation certificate, indicating that the reputation certificate has been revoked, that is, the reputation data corresponding to the reputation certificate is data that has not been authenticated.

[0114] Specifically, the blockchain node receives a certificate revocation request for the reputation data to be authenticated, parses the certificate revocation request, and obtains the authenticated identifier and the target service identifier corresponding to the reputation data to be authenticated. Then, it is detected whether there is a reputation certificate revocation identifier in the registered reputation service corresponding to the target service identifier. When there is no reputation certificate revocation identifier, a prompt message indicating that the certificate revocation request cannot be revoked is returned to the request end corresponding to the certificate revocation request. When there is a reputation certificate revocation identifier, the reputation certificate generation contract is called; a reputation revocation certificate for the reputation certificate corresponding to the authenticated identifier is generated through the reputation certificate generation contract, and the reputation revocation certificate is used to indicate that the reputation certificate corresponding to the authenticated identifier has been revoked. The reputation revocation certificate, the authenticated identifier, and the reputation data to be authenticated are then associated and stored in the blockchain, and the reputation revocation certificate is returned to the request end corresponding to the certificate revocation request.

[0115] In the above embodiment, by receiving a certificate revocation request for the reputation data to be authenticated, and when there is a reputation certificate revocation identifier in the registered reputation service, a reputation revocation certificate for the reputation certificate corresponding to the authenticated identifier is generated through the reputation certificate generation contract to achieve the revocation of the generated reputation certificate, thereby avoiding the problem that the generated reputation certificate is incorrect and cannot be deleted, thereby improving the accuracy of the generated reputation certificate.

[0116] In one embodiment, the target registered reputation service also includes a reputation proof reservation flag; the blockchain-based data processing method also includes:

[0117] A certificate revocation request for reputation data to be authenticated is received, the certificate revocation request carries the authenticated identifier and target service identifier corresponding to the reputation data to be authenticated; when it is detected that a reputation certificate reservation identifier exists in a registered reputation service corresponding to the target service identifier, a prompt message that the reputation certificate cannot be revoked is generated, and the prompt message that the reputation certificate cannot be revoked is transmitted to the request end corresponding to the certificate revocation request.

[0118] The reputation proof retention flag is used to indicate that the reputation proof generated by the corresponding reputation service cannot be revoked. The reputation proof retention flag included in the reputation service is set when the reputation service is registered.

[0119] Specifically, the blockchain node receives a certificate revocation request for the reputation data to be authenticated, and then detects whether there is a reputation certificate revocation identifier in the registered reputation service corresponding to the target service identifier. When there is no reputation certificate revocation identifier, it means that there is a reputation certificate retention identifier in the registered reputation service corresponding to the target service identifier. At this time, the blockchain node generates a prompt message that the reputation certificate cannot be revoked, and proves the prompt message that the reputation certificate cannot be revoked to the requesting end corresponding to the revocation request.

[0120] In the above embodiment, when a reputation certificate retention flag exists in the registered reputation service, a prompt message that the reputation certificate cannot be revoked is generated, and the prompt message that the reputation certificate cannot be revoked is used to prove the request end corresponding to the revocation request, thereby avoiding the revocation of the irrevocable reputation certificate, thereby improving the accuracy of the generated reputation certificate.

[0121] In one embodiment, the blockchain-based data processing method further includes:

[0122] When the authentication result corresponding to the reputation authentication request is authentication success, authentication success prompt information is generated, and the authentication success prompt information of the reputation authentication request is returned to the target account; when the authentication result corresponding to the reputation authentication request is authentication failure, authentication failure prompt information is generated, and the authentication failure prompt information of the reputation authentication request is returned to the target account;

[0123] Specifically, the authentication success prompt information refers to the prompt information that the reputation data to be authenticated has passed the authentication. The authentication failure prompt information refers to the prompt information that the reputation data to be authenticated has not passed the authentication. The authentication result corresponding to the reputation authentication request may include an authentication success result and an authentication failure result. Then, when the authentication result corresponding to the reputation authentication request is obtained, the authentication result can be returned. In one embodiment, when the blockchain node obtains the authentication result, the authentication result can be saved in the blockchain, and there is no need to return the authentication result to the target account.

[0124] In the above embodiment, when the authentication result corresponding to the reputation authentication request is successful authentication, authentication success prompt information is generated, and the authentication success prompt information of the reputation authentication request is returned to the target account; when the authentication result corresponding to the reputation authentication request is failed authentication, authentication failure prompt information is generated, and the authentication failure prompt information of the reputation authentication request is returned to the target account, thereby facilitating subsequent processing by the target account and improving convenience.

[0125] In one embodiment, Figure 8As shown, before S202, that is, before receiving the reputation authentication request sent by the target account, it also includes:

[0126] S802, obtaining a reputation service registration request sent by a certification authority account, the reputation service registration request carries reputation service information, and the reputation service information includes a reputation data format to be registered, a reputation resolution contract address to be registered, and a data source information to be registered.

[0127] Among them, reputation service information refers to the information required when registering a reputation service. The reputation data format to be registered refers to the reputation data format when registering a reputation service. The reputation resolution contract address to be registered refers to the reputation resolution contract address when registering a reputation service. The data source information to be registered refers to the data source information when registering a reputation service.

[0128] Specifically, the blockchain node obtains the reputation service registration request sent by the certification authority account, and parses the reputation service registration request to obtain the reputation service information. The reputation service registration request can be sent to the blockchain node through the certification authority account at the certification authority account end, or the reputation service registration request can be received at the blockchain node through the certification authority account.

[0129] S804, calling the reputation service registration contract based on the reputation service registration request, and verifying the legitimacy of the reputation data format to be registered through a preset reputation data format in the reputation service registration contract.

[0130] S806, verify the legitimacy of the reputation resolution contract address to be registered through the contract address range in the reputation service registration contract.

[0131] S808, verify the data source deployment of the data source information through the reputation service registration contract.

[0132] The preset reputation data format refers to the pre-set reputation data format for the same reputation service. The contract address range refers to the pre-set range of reputation resolution contract addresses. The data source deployment verification refers to the verification of whether the data corresponding to the data source information has been deployed to the blockchain.

[0133] Specifically, the server responds to the reputation service registration request and calls the reputation service registration contract. It verifies whether the format of the reputation data to be registered is accurate through the preset reputation data format in the reputation service registration contract. It also verifies whether the contract address of the reputation resolution contract to be registered is accessible through the contract address range in the reputation service registration contract. It also verifies whether the data corresponding to the data source information has been deployed to the blockchain through the reputation service registration contract.

[0134] S810, when the legitimacy verification of the format of the reputation data to be registered passes, the legitimacy verification of the reputation resolution contract address to be registered passes, and the data source deployment verification passes, a registered reputation service identifier of the reputation service information is generated through the reputation service registration contract;

[0135] S812, write the reputation service information and the registered reputation service identifier into the blockchain, generate a prompt message of successful registration based on the registered reputation service identifier, and return the prompt message of successful registration to the target account.

[0136] Specifically, the blockchain node determines that when the legality verification of the format of the reputation data to be registered fails, or the legality verification of the contract address of the reputation resolution to be registered fails, or the data source deployment verification fails, the registration failure prompt message is returned to the target account. The blockchain node determines that when the legality verification of the format of the reputation data to be registered passes, the legality verification of the contract address of the reputation resolution to be registered passes, and the data source deployment verification passes, the registered reputation service identifier of the reputation service information is generated through the reputation service registration contract, wherein a random number generator can be used to generate the registered reputation service identifier of the reputation service information, or the registered reputation service identifier can be generated in sequence according to a pre-set reputation service identifier generation rule, or the registered reputation service identifier can be obtained by self-incrementing according to the initial value of the registered reputation service identifier. Finally, the blockchain node writes the reputation service information and the registered reputation service identifier into the blockchain in association, generates a prompt message of successful registration based on the registered reputation service identifier, and returns the prompt message of successful registration to the target account, which can include the registered reputation service identifier.

[0137] In the above embodiment, by obtaining the reputation service registration request sent by the certification agency account, the reputation data format to be registered, the reputation resolution contract address to be registered and the data source information to be registered are verified through the reputation service registration contract, and after the verification is passed, the reputation service registration contract generates a registered reputation service identifier of the reputation service information. Then the reputation service information and the registered reputation service identifier are associated and written into the blockchain, so that any certification agency account end can register the corresponding reputation service in the blockchain, without the need to establish an independent evidence storage or DID system, which improves the versatility of reputation data authentication, and can directly use the reputation service registered in the blockchain for reputation data authentication, which improves the efficiency of reputation data authentication and reduces the data intercommunication cost of reputation authentication.

[0138] In one embodiment, the preset reputation data format includes reputation data general field information;

[0139] S804, that is, verifying the legitimacy of the reputation data format to be registered through the preset reputation data format in the reputation service registration contract, including the steps of:

[0140] Search the reputation data field information to be registered corresponding to the reputation data format to be registered in the reputation data general field information in the reputation service registration contract; when the reputation data field information to be registered is found, it is determined that the legitimacy verification of the reputation data format to be registered has passed; when the reputation data field information to be registered is not found, it is determined that the legitimacy verification of the reputation data format to be registered has not passed.

[0141] The reputation data universal field information refers to the pre-defined universal field format information of the reputation data corresponding to the reputation service, which may include the name of the field, the rule of the field, and the like.

[0142] Specifically, the blockchain node verifies the legitimacy of the reputation data field information corresponding to the reputation data format to be registered through the reputation data general field information in the reputation service registration contract, that is, searches for the reputation data field information corresponding to the reputation data format to be registered in the reputation data general field information. When the reputation data field information to be registered is found, it is determined that the legitimacy verification of the reputation data format to be registered has passed. When the reputation data field information to be registered is not found, it is determined that the legitimacy verification of the reputation data format to be registered has not passed. In one embodiment, the blockchain node can verify the legitimacy of the field rules in the reputation data field information to be registered through the reputation service registration contract to prevent illegal input and data errors.

[0143] In the above embodiment, the legality of the reputation data format to be registered is verified by using the preset reputation data format in the reputation service registration contract, so as to ensure the integrity and consistency of the reputation data format to be registered and avoid errors in the reputation data format to be registered.

[0144] In one embodiment, S806, that is, verifying the legitimacy of the to-be-registered reputation resolution contract address through the contract address range in the reputation service registration contract, includes the steps of:

[0145] Search for the contract address to be registered for reputation resolution in the contract address range in the reputation service registration contract; when the contract address to be registered for reputation resolution is found, send a validity access signal to the contract address to be registered for reputation resolution through the reputation service registration contract; when the valid signal returned by the contract address to be registered for the validity access request is obtained, it is determined that the legitimacy verification of the contract address to be registered for reputation resolution has passed.

[0146] The validity access signal refers to a network signal used to verify whether the address of the reputation resolution contract to be registered is accessible, such as a heartbeat signal, etc. The validity signal refers to the network signal returned in response to the validity access signal.

[0147] Specifically, the contract address of the reputation resolution to be registered is searched in the contract address range in the reputation service registration contract. When the contract address of the reputation resolution to be registered is not found, it means that the reputation resolution contract address is an invalid address, and it is determined that the legitimacy verification of the contract address of the reputation resolution to be registered has failed. At this time, a prompt message of registration failure is returned to the certification agency account. When the contract address of the reputation resolution to be registered is found, a validity access signal is sent to the contract address of the reputation resolution to be registered through the reputation service registration contract. Then, it is continuously detected whether a valid signal is returned in response to the validity access signal. When a valid signal returned by the contract address of the reputation resolution to be registered in response to the validity access request is obtained, it is determined that the legitimacy verification of the contract address of the reputation resolution to be registered has passed. When the returned valid signal is not obtained, it is determined that the legitimacy verification of the contract address of the reputation resolution to be registered has failed. At this time, a prompt message of registration failure is returned to the certification agency account.

[0148] In the above embodiment, the validity of the reputation resolution contract address to be registered is verified through the contract address range, thereby avoiding registration of invalid reputation resolution contract addresses and ensuring the accuracy of the registered reputation service.

[0149] In one embodiment, the data source information includes the on-chain data source type and the corresponding on-chain verification information storage address. S806, that is, performing data source deployment verification on the data source information through the reputation service registration contract, includes the steps of:

[0150] The reputation service registration contract uses the on-chain verification information storage address corresponding to the on-chain data source type to find the corresponding verification information storage block; when the corresponding verification information storage block is found, the reputation data corresponding to the reputation data format to be registered is searched in the verification information storage block; when the reputation data corresponding to the reputation data format to be registered is found, it is determined that the data source deployment verification has passed.

[0151] Specifically, the blockchain node performs data source deployment verification according to the on-chain data source type and the corresponding on-chain verification information storage address included in the data source information. That is, the blockchain node detects whether there is a verification information storage block corresponding to the on-chain verification information storage address in the blockchain. When the corresponding verification information storage block is not found, it means that the on-chain verification information storage address is incorrect. At this time, it is determined that the data source deployment verification has not passed. When the corresponding verification information storage block is found, the blockchain node searches the verification information storage block for reputation data corresponding to the reputation data format to be registered. When the reputation data corresponding to the reputation data format to be registered is found, it is determined that the data source deployment verification has passed. When the reputation data corresponding to the reputation data format to be registered is not found, it is determined that the data source deployment verification has not passed.

[0152] In the above embodiment, the data source deployment verification is performed through the on-chain data source type and the corresponding on-chain verification information storage address included in the data source information, and it is determined that the data source deployment verification passes, thereby ensuring the validity of the on-chain data source type and the corresponding on-chain verification information storage address, and avoiding registration of invalid on-chain data source types and corresponding on-chain verification information storage addresses.

[0153] In one embodiment, the data source information includes the off-chain data source type and the corresponding signature verification information storage address. S806, that is, performing data source deployment verification on the data source information through the reputation service registration contract, includes the steps of:

[0154] The reputation service registration contract uses the signature verification information storage address corresponding to the on-chain data source type to find the corresponding signature information storage block. When the corresponding signature information storage block is found, the signature data corresponding to the format of the reputation data to be registered is searched in the signature information storage block. When the signature data corresponding to the format of the reputation data to be registered is found, it is determined that the data source deployment verification has passed.

[0155] Specifically, the blockchain node performs data source deployment verification according to the off-chain data source type and the corresponding signature verification information storage address included in the data source information. That is, the blockchain node detects whether there is a signature information storage block corresponding to the signature verification information storage address in the blockchain. When the corresponding signature information storage block is not found, it means that the signature verification information storage address is incorrect. At this time, it is determined that the data source deployment verification has not passed. When the corresponding signature information storage block is found, the blockchain node searches for the corresponding signature data in the signature information storage block. When the corresponding signature data is found, it is determined that the data source deployment verification has passed. When the signature data is not found, it is determined that the data source deployment verification has not passed.

[0156] In the above embodiment, the data source deployment verification is performed through the off-chain data source type and the corresponding signature verification information storage address included in the data source information, and it is determined that the data source deployment verification passes, thereby ensuring the validity of the off-chain data source type and the corresponding signature verification information storage address, and avoiding the registration of invalid off-chain data source types and corresponding signature verification information storage addresses.

[0157] In one embodiment, the reputation service information also includes reputation certificate revocation information, and the reputation certificate revocation information includes a reputation certificate revocation mark or a reputation certificate retention mark. When the certification body account registers for the reputation service on the certification body account side, it also provides the reputation certificate revocation mark or the reputation certificate retention mark, associates the reputation certificate revocation mark or the reputation certificate retention mark with the registered reputation service, and then indicates that the registered reputation service can revoke the reputation certificate through the reputation certificate revocation mark, and indicates that the registered reputation service cannot revoke the generated reputation certificate through the reputation certificate retention mark. The reputation service information can only include one of the reputation certificate revocation mark and the reputation certificate retention mark. That is, the corresponding generated reputation certificate can be revoked through the reputation service with the reputation certificate revocation mark, avoiding the generation of incorrect reputation certificates and improving the accuracy of the reputation certificate.

[0158] In a specific embodiment, Fig. 9As shown, a flow chart of reputation service registration is provided. Specifically, the certification body can use the certification body account to register the reputation service through the certification body account terminal. The certification body can pre-set the reputation data format and data source information of the reputation service to be registered. Then send a reputation service registration request to the blockchain, the reputation service registration request can carry the reputation service information, the reputation service information can include the reputation data format, the data source information and the reputation resolution contract address, the reputation service information can also include the reputation proof revocation information, that is, the reputation proof revocation mark or the reputation proof reservation mark. Then the blockchain node in the blockchain network receives the reputation service registration request, and responds to the reputation service registration request to call the reputation service registration contract. The reputation registration contract verifies whether the reputation data format is legal, that is, whether it is consistent with the reputation data format pre-set in the reputation service registration contract. When the reputation data format is verified, verify whether the reputation resolution contract address is a contract, that is, verify whether the reputation resolution contract address is in the block address range corresponding to the block in the blockchain. When the legitimacy of the reputation resolution contract address is verified, verify whether the data source information can be accessed normally. When it is an off-chain data type, the certification body itself needs to deploy a service for digitally signing the reputation data, and obtain the signature information after digitally signing the reputation data. Then the certification body provides the signature information to the object of the reputation data, and the object of the reputation data can use the signature information for authentication, and the certification body writes the signature information into the blockchain. Then when registering the reputation service, the blockchain node needs to verify whether the signature information corresponding to the off-chain data type is written into the blockchain. When it is an on-chain data type, the blockchain node needs to verify whether the reputation data corresponding to the on-chain data type is written into the blockchain. When the data source information is verified, a registered service identifier is generated, and then the registered service identifier and the reputation service information are associated and written into the block, and the block is written into the blockchain. That is, after the reputation information is verified, the reputation service is registered into the blockchain, so that each certification body can register the corresponding reputation service in the blockchain, so that the blockchain can pass various reputation services, improving the efficiency of reputation authentication.

[0159] In one embodiment, the reputation authentication request also carries a blockchain identifier;

[0160] S204, i.e., querying whether there is a target registered reputation service matching the target service identifier in the registered reputation services, includes the following steps:

[0161] Based on the blockchain identifier, the corresponding target blockchain is found, and a registered reputation service is found in the target blockchain; in the registered reputation service, it is queried whether there is a target registered reputation service that matches the target service identifier.

[0162] Among them, the target blockchain refers to the blockchain registered with the reputation service.

[0163] Specifically, a blockchain node can access multiple different blockchains, which can be public chains, private chains, alliance chains, etc. When a blockchain node obtains a reputation authentication request, it finds the target blockchain to be accessed according to the blockchain identifier in the reputation authentication request. Then, it finds each in the target blockchain, and then queries each registered reputation service to see whether there is a target registered reputation service that matches the target service identifier, that is, the association relationship between the registered reputation service and the registered service identifier can be used to find the target registered reputation service that matches the target service identifier.

[0164] In the above embodiment, the corresponding target blockchain is found based on the blockchain identifier, and then the registered reputation service is found in the target blockchain. It is queried in the registered reputation service whether there is a target registered reputation service that matches the target service identifier. Thus, the target blockchain that can provide the reputation service can be found according to the blockchain identifier, and the reputation data authentication is performed in the target regional chain, avoiding access to the blockchain that does not provide the reputation service, saving service resources, and improving the accuracy and efficiency of the reputation authentication.

[0165] In a specific embodiment, Fig.10 As shown, a data processing method based on blockchain is provided, which specifically includes the following steps:

[0166] S1002, receiving a reputation authentication request sent by a target account, the reputation authentication request carrying a target service identifier of a requested reputation service and reputation data to be authenticated, and querying among registered reputation services whether there is a target registered reputation service that matches the target service identifier.

[0167] S1004, if there is a target registered reputation service that matches the target service identifier, check whether there is a corresponding reputation resolution contract address in the target registered reputation service. When there is a corresponding reputation resolution contract address in the target registered reputation service, query the corresponding target resolution contract based on the reputation resolution contract address. When the target resolution contract is queried, check whether there is corresponding data source information in the target registered reputation service.

[0168] S1006, when the corresponding data source information exists in the target registered reputation service, the validity of the data source information is verified according to the data source type in the data source information and the corresponding verification data storage address. When the validity of the data source information is verified, the corresponding target resolution contract is obtained based on the reputation resolution contract address.

[0169] S1008, based on the off-chain data source type, the signature data to be authenticated is obtained from the reputation data to be authenticated, the signature data to be authenticated is obtained from the authentication agency account end corresponding to the authentication agency account, and the authentication agency account end corresponding to the authentication agency account digitally signs the experience data of the target account in the real world to obtain the signature data to be authenticated;

[0170] S1010, calling the target parsing contract to search for signature information matching the signature data to be authenticated in the storage space corresponding to the signature verification information storage address. When signature information matching the signature data to be authenticated is found, it is determined that the reputation data to be authenticated has been authenticated.

[0171] S1012, when it is determined that the reputation data to be authenticated has passed the authentication, the reputation proof generation contract is called; the reputation proof generation contract generates a reputation proof for the reputation authentication request and an authenticated identifier corresponding to the reputation proof, and the reputation proof, the authenticated identifier and the reputation data to be authenticated are associated and stored in the blockchain, and the authenticated identifier is returned to the request end corresponding to the reputation authentication request.

[0172] In the above embodiment, the corresponding reputation service is registered in the blockchain through the certification agency account, so that the corresponding reputation data can be authenticated through the reputation service in the blockchain, without the need to authenticate in different evidence storage systems, thereby reducing the data interoperability cost of reputation authentication, improving the efficiency of reputation authentication, and saving the resources of the certification agency.

[0173] In a specific embodiment, Fig.11As shown, a schematic diagram of the overall architecture of reputation authentication based on the alliance chain is provided. Specifically, the overall architecture of the reputation authentication mainly includes a reputation registration contract, a reputation proof generation contract, and a reputation resolution contract deployed by the certification authority. The reputation registration contract, the reputation proof generation contract, and the reputation resolution contract deployed by the certification authority are all deployed in the alliance chain. The reputation service is registered through the reputation registration contract, and the reputation proof is generated and revoked through the reputation proof generation contract. The reputation data is verified through the reputation resolution contract. Different certification agencies can implement corresponding reputation service registration and deploy corresponding reputation resolution contracts, without providing data to a third party, and can register reputation services without restrictions. Then, after completing the reputation service registration, any organization or individual can authenticate the responsive reputation data in the blockchain. That is, the blockchain node obtains a reputation authentication request, which carries the target service identifier of the requested reputation service and the reputation data to be authenticated. Then, when it is determined that there is a reputation service corresponding to the target service identifier in the blockchain, the corresponding reputation resolution contract is obtained to authenticate the reputation data to be authenticated, and after the authentication is passed, the corresponding reputation certificate and the authenticated identifier are generated using the reputation proof generation contract, and the authenticated identifier is returned to the request end corresponding to the reputation authentication request. Among them, if the reputation data to be authenticated is an on-chain data type, the reputation data to be authenticated includes the data provided by the authentication agency and the corresponding signature. If it is an on-chain data type, the reputation data to be authenticated includes an identity signature that proves that the corresponding certificate can be obtained. After the identity signature is verified, the reputation data to be authenticated is authenticated. Reputation data authentication is performed through the reputation service provided by the alliance chain. That is, a unified proof generation entry is provided, which improves the versatility of reputation authentication and saves the network service resources of the authentication agency.

[0174] In a specific embodiment, the work experience authentication agency registers the identity authentication service in the blockchain, and at this time, the blockchain can provide the work experience authentication service. Specifically: the blockchain node receives the reputation authentication request sent by the target account, and the reputation authentication request carries the work experience authentication service identifier of the requested reputation service and the work experience data to be authenticated. Then the blockchain node queries whether there is a target work experience authentication service that matches the work experience authentication service identifier in the registered reputation service. If there is a target work experience authentication service that matches the work experience authentication service identifier, based on the reputation resolution contract information in the target work experience authentication service, the corresponding target resolution contract is obtained. Then, according to the data source information in the target registered reputation service, the target resolution contract is called to authenticate the reputation data to be authenticated to obtain the authentication result corresponding to the reputation authentication request, wherein the data source information includes the off-chain data type and the corresponding signature information storage address. At this time, the blockchain node obtains the work experience signature from the work experience data, and then matches the work experience signature with the signature information stored in the signature information storage address. When there is a consistent work experience signature, it is determined that the reputation authentication of the work experience data has passed. When there is no consistent work experience signature, it is determined that the reputation authentication of the work experience data has not passed. The authentication result corresponding to the reputation authentication request is then returned to the requesting end, thereby improving the versatility and efficiency of work experience data authentication.

[0175] In a specific embodiment, the project experience authentication agency registers the identity authentication service in the blockchain, at which point the blockchain can provide project experience authentication services. Specifically: receive a reputation authentication request sent by the target account, the reputation authentication request carries the project experience service identifier of the requested reputation service and the project experience data to be authenticated; query whether there is a target project experience authentication service that matches the project experience service identifier in the registered reputation service; if there is a target project experience authentication service that matches the target project experience service identifier, obtain the corresponding target resolution contract based on the reputation resolution contract information in the target project experience authentication service; based on the data source information in the target registered reputation service, call the target resolution contract to authenticate the project experience data to be authenticated, so as to obtain the authentication result corresponding to the reputation authentication request. Among them, the data source information includes the on-chain data type and the corresponding project experience information storage address. At this time, the blockchain node searches for the project experience data to be authenticated in the project experience information stored in the project experience information storage address. When the project experience data to be authenticated is found, it is determined that the reputation authentication of the project experience data has passed. When the project experience data to be authenticated is not found, it is determined that the reputation authentication of the project experience data has failed. The authentication result corresponding to the reputation authentication request is then returned to the requesting end, thereby improving the versatility and efficiency of project experience data authentication.

[0176] It should be understood that, although the various steps in the flowcharts involved in the above-mentioned embodiments are displayed in sequence according to the indication of the arrows, these steps are not necessarily executed in sequence according to the order indicated by the arrows. Unless there is a clear explanation in this article, the execution of these steps does not have a strict order restriction, and these steps can be executed in other orders. Moreover, at least a part of the steps in the flowcharts involved in the above-mentioned embodiments can include multiple steps or multiple stages, and these steps or stages are not necessarily executed at the same time, but can be executed at different times, and the execution order of these steps or stages is not necessarily to be carried out in sequence, but can be executed in turn or alternately with other steps or at least a part of the steps or stages in other steps.

[0177] Based on the same inventive concept, the embodiment of the present application also provides a blockchain-based data processing device for implementing the blockchain-based data processing method involved above. The implementation solution provided by the device to solve the problem is similar to the implementation solution recorded in the above method, so the specific limitations in the one or more blockchain-based data processing device embodiments provided below can refer to the above limitations on the blockchain-based data processing method, which will not be repeated here.

[0178] In one embodiment, Fig.12 As shown, a data processing device 1200 based on blockchain is provided, comprising: a request acceptance module 1202, a matching module 1204, a contract acquisition module 1206 and a data authentication module 1208, wherein:

[0179] The request receiving module 1202 is used to receive a reputation authentication request sent by a target account, the reputation authentication request carries a target service identifier of a requested reputation service and reputation data to be authenticated, the reputation data to be authenticated is the experience data of the target account in the real world, the reputation authentication request is a request to authenticate the experience data of the target account in the real world, and the reputation service is a service to authenticate the experience data of the target account in the real world;

[0180] A matching module 1204 is used to query whether there is a target registered reputation service matching the target service identifier in the registered reputation service, where the registered reputation service is obtained based on a registration request for the reputation service by the certification authority account;

[0181] A contract acquisition module 1206 is used to acquire a corresponding target resolution contract based on the reputation resolution contract information in the target registered reputation service if there is a target registered reputation service matching the target service identifier;

[0182] The data authentication module 1208 is used to call the target resolution contract to authenticate the reputation data to be authenticated based on the data source information in the target registered reputation service, so as to obtain the authentication result corresponding to the reputation authentication request.

[0183] In one embodiment, the reputation resolution contract information includes the reputation resolution contract address, the data source information includes the data source type and the corresponding verification data storage address, and the contract acquisition module 1206 is also used to verify whether the corresponding reputation resolution contract address exists in the target registered reputation service; when the corresponding reputation resolution contract address exists in the target registered reputation service, the corresponding target resolution contract is queried based on the reputation resolution contract address; when the target resolution contract is queried, it is verified whether the corresponding data source information exists in the target registered reputation service; when the corresponding data source information exists in the target registered reputation service, the validity of the data source information is verified according to the data source type in the data source information and the corresponding verification data storage address; when the validity of the data source information is verified, the corresponding target resolution contract is obtained based on the reputation resolution contract address.

[0184] In one embodiment, the data source information includes the off-chain data source type and the corresponding signature verification information storage address; the data authentication module 1208 is also used to obtain the signature data to be authenticated from the reputation data to be authenticated based on the off-chain data source type, and the signature data to be authenticated is obtained from the certification agency account end corresponding to the certification agency account, and the certification agency account end corresponding to the certification agency account digitally signs the experience data of the target account in the real world to obtain the signature data to be authenticated; the target parsing contract is called to search for signature information matching the signature data to be authenticated in the storage space corresponding to the signature verification information storage address; when the signature information matching the signature data to be authenticated is found, it is determined that the authentication of the reputation data to be authenticated is passed, and when the signature information matching the signature data to be authenticated is not found, it is determined that the authentication of the reputation data to be authenticated has failed.

[0185] In one embodiment, the data source information includes an on-chain data source type and a corresponding on-chain verification information storage address; the data authentication module 1208 is also used to call the target parsing contract based on the on-chain data source type to search for reputation data matching the reputation data to be authenticated in the storage block corresponding to the on-chain verification information storage address; when reputation data matching the reputation data to be authenticated is found in the storage block corresponding to the on-chain verification information storage address, it is determined that the authentication of the reputation data to be authenticated is passed; when reputation data matching the reputation data to be authenticated is not found in the storage block corresponding to the on-chain verification information storage address, it is determined that the authentication of the reputation data to be authenticated has failed.

[0186] In one embodiment, the blockchain-based data processing device 1200 further includes:

[0187] The proof generation module is used to call the reputation proof generation contract when the authentication result corresponding to the reputation authentication request is that the reputation data to be authenticated is authenticated; generate a reputation proof for the reputation authentication request and an authenticated identifier corresponding to the reputation proof through the reputation proof generation contract; associate the reputation proof, the authenticated identifier and the reputation data to be authenticated and store them in the blockchain, and return the authenticated identifier to the request end corresponding to the reputation authentication request.

[0188] In one embodiment, the blockchain-based data processing device 1200 further includes:

[0189] The proof verification module is used to receive a verification request for the reputation data to be verified, the verification request includes the reputation data to be verified and the authenticated identifier to be verified corresponding to the reputation data to be verified; search for the target authenticated identifier associated with the reputation data to be verified in the blockchain; when the target authenticated identifier is consistent with the authenticated identifier to be verified, a verification result of the reputation data to be verified is obtained, and the verification result of the reputation data to be verified is returned to the request end corresponding to the verification request; when the target authenticated identifier is inconsistent with the authenticated identifier to be verified, a verification failure result of the reputation data to be verified is obtained, and the verification failure result of the reputation data to be verified is returned to the request end corresponding to the verification request.

[0190] In one embodiment, the target registered reputation service also includes a reputation certification revocation flag; the blockchain-based data processing device 1200 also includes:

[0191] The proof revocation module receives a proof revocation request for the reputation data to be authenticated, and the proof revocation request carries the authenticated identifier and the target service identifier corresponding to the reputation data to be authenticated; when it is detected that there is a reputation proof revocation identifier in the registered reputation service corresponding to the target service identifier, the reputation proof generation contract is called; a reputation revocation certificate for the reputation proof corresponding to the authenticated identifier is generated through the reputation proof generation contract; the reputation revocation certificate, the authenticated identifier and the reputation data to be authenticated are associated and stored in the blockchain, and the reputation revocation certificate is returned to the request end corresponding to the proof revocation request.

[0192] In one embodiment, the target registered reputation service also includes a reputation proof reservation flag; the blockchain-based data processing device 1200 also includes:

[0193] The certification retention module is used to receive a certification revocation request for the reputation data to be authenticated, and the certification revocation request carries the authenticated identifier and the target service identifier corresponding to the reputation data to be authenticated; when it is detected that there is a reputation certification retention identifier in the registered reputation service corresponding to the target service identifier, a prompt message that the reputation certification cannot be revoked is generated, and the prompt message that the reputation certification cannot be revoked is sent to the request end corresponding to the certification revocation request.

[0194] In one embodiment, the blockchain-based data processing device 1200 further includes:

[0195] An information return module, used for generating authentication success prompt information when the authentication result corresponding to the reputation authentication request is authentication success, and returning the authentication success prompt information of the reputation authentication request to the target account; when the authentication result corresponding to the reputation authentication request is authentication failure, generating authentication failure prompt information, and returning the authentication failure prompt information of the reputation authentication request to the target account;

[0196] In one embodiment, the blockchain-based data processing device 1200 further includes:

[0197] A registration module is used to obtain a reputation service registration request sent by a certification authority account. The reputation service registration request carries reputation service information, including the format of the reputation data to be registered, the contract address of the reputation resolution to be registered, and the data source information to be registered; based on the reputation service registration request, the reputation service registration contract is called, and the legitimacy of the format of the reputation data to be registered is verified through the preset reputation data format in the reputation service registration contract; the legitimacy of the contract address of the reputation resolution to be registered is verified through the contract address range in the reputation service registration contract; the data source information is verified for data source deployment through the reputation service registration contract; when the legitimacy verification of the format of the reputation data to be registered passes, the legitimacy verification of the contract address of the reputation resolution to be registered passes, and the data source deployment verification passes, a registered reputation service identifier of the reputation service information is generated through the reputation service registration contract; the reputation service information and the registered reputation service identifier are associated and written into the blockchain, and a prompt message of successful registration is generated based on the registered reputation service identifier, and a prompt message of successful registration is returned to the target account.

[0198] In one embodiment, the preset reputation data format includes general field information of reputation data; the registration module is also used to search for the field information of the reputation data to be registered corresponding to the reputation data format to be registered in the general field information of the reputation data in the reputation service registration contract; when the field information of the reputation data to be registered is found, it is determined that the legitimacy verification of the reputation data format to be registered has passed; when the field information of the reputation data to be registered is not found, it is determined that the legitimacy verification of the reputation data format to be registered has not passed.

[0199] In one embodiment, the registration module is also used to search for the contract address to be registered for the reputation resolution in the contract address range in the reputation service registration contract; when the contract address to be registered for the reputation resolution is found, a validity access signal is sent to the contract address to be registered for the reputation resolution through the reputation service registration contract; when a valid signal returned by the contract address to be registered for the validity access request is obtained, it is determined that the legitimacy verification of the contract address to be registered for the reputation resolution has passed.

[0200] In one embodiment, the data source information includes an on-chain data source type and a corresponding on-chain verification information storage address. The registration module is also used to use the on-chain verification information storage address corresponding to the on-chain data source type to find the corresponding verification information storage block through the reputation service registration contract; when the corresponding verification information storage block is found, the reputation data corresponding to the reputation data format to be registered is searched in the verification information storage block; when the reputation data corresponding to the reputation data format to be registered is found, it is determined that the data source deployment verification has passed.

[0201] In one embodiment, the data source information includes the off-chain data source type and the corresponding signature verification information storage address. The registration module is also used to use the signature verification information storage address corresponding to the on-chain data source type to find the corresponding signature information storage block through the reputation service registration contract. When the corresponding signature information storage block is found, the signature data corresponding to the format of the reputation data to be registered is searched in the signature information storage block. When the signature data corresponding to the format of the reputation data to be registered is found, it is determined that the data source deployment verification has passed.

[0202] In one embodiment, the reputation service information further includes reputation certification revocation information, and the reputation certification revocation information includes a reputation certification revocation mark or a reputation certification retention mark;

[0203] In one embodiment, the reputation authentication request also carries a blockchain identifier, and the matching module 1204 is also used to find the corresponding target blockchain based on the blockchain identifier, and to find a registered reputation service in the target blockchain; and to query in the registered reputation service whether there is a target registered reputation service that matches the target service identifier.

[0204] Each module in the above-mentioned blockchain-based data processing device can be implemented in whole or in part by software, hardware, or a combination thereof. Each of the above-mentioned modules can be embedded in or independent of the processor in the computer device in the form of hardware, or can be stored in the memory in the computer device in the form of software, so that the processor can call and execute the operations corresponding to each of the above modules.

[0205] In one embodiment, a computer device is provided. The computer device may be a server, and its internal structure diagram may be as follows: Fig.13As shown. The computer device includes a processor, a memory, an input / output interface (Input / Output, referred to as I / O) and a communication interface. Among them, the processor, the memory and the input / output interface are connected through a system bus, and the communication interface is connected to the system bus through the input / output interface. Among them, the processor of the computer device is used to provide computing and control capabilities. The memory of the computer device includes a non-volatile storage medium and an internal memory. The non-volatile storage medium stores an operating system, a computer program and a database. The internal memory provides an environment for the operation of the operating system and the computer program in the non-volatile storage medium. The database of the computer device is used to store blockchain data. The input / output interface of the computer device is used to exchange information between the processor and an external device. The communication interface of the computer device is used to communicate with an external terminal through a network connection. When the computer program is executed by the processor, a data processing method based on blockchain is implemented.

[0206] In one embodiment, a computer device is provided. The computer device may be a terminal, and its internal structure diagram may be as follows: Fig.14 As shown. The computer device includes a processor, a memory, an input / output interface, a communication interface, a display unit and an input device. Among them, the processor, the memory and the input / output interface are connected through a system bus, and the communication interface, the display unit and the input device are connected to the system bus through the input / output interface. Among them, the processor of the computer device is used to provide computing and control capabilities. The memory of the computer device includes a non-volatile storage medium and an internal memory. The non-volatile storage medium stores an operating system and a computer program. The internal memory provides an environment for the operation of the operating system and the computer program in the non-volatile storage medium. The input / output interface of the computer device is used to exchange information between the processor and the external device. The communication interface of the computer device is used to communicate with an external terminal in a wired or wireless manner, and the wireless method can be implemented through WIFI, a mobile cellular network, NFC (near field communication) or other technologies. When the computer program is executed by the processor, a data processing method based on blockchain is implemented. The display unit of the computer device is used to form a visually visible image, and can be a display screen, a projection device or a virtual reality imaging device. The display screen can be a liquid crystal display screen or an electronic ink display screen. The input device of the computer device can be a touch layer covered on the display screen, or a button, trackball or touchpad set on the computer device casing, or an external keyboard, touchpad or mouse, etc.

[0207] Those skilled in the art will understand that Fig.13 or Fig.14The structure shown in the figure is only a block diagram of a part of the structure related to the solution of the present application, and does not constitute a limitation on the computer device to which the solution of the present application is applied. The specific computer device may include more or fewer components than those shown in the figure, or combine certain components, or have a different arrangement of components.

[0208] In one embodiment, a computer device is further provided, including a memory and a processor, wherein a computer program is stored in the memory, and the processor implements the steps in the above method embodiments when executing the computer program.

[0209] In one embodiment, a computer-readable storage medium is provided, on which a computer program is stored. When the computer program is executed by a processor, the steps in the above-mentioned method embodiments are implemented.

[0210] In one embodiment, a computer program product is provided, including a computer program, which implements the steps in the above method embodiments when executed by a processor.

[0211] It should be noted that the user information (including but not limited to user device information, user personal information, etc.) and data (including but not limited to data used for analysis, stored data, displayed data, etc.) involved in this application are all information and data authorized by the user or fully authorized by all parties, and the collection, use and processing of relevant data must comply with relevant laws, regulations and standards of relevant countries and regions.

[0212] Those skilled in the art can understand that all or part of the processes in the above-mentioned embodiment methods can be completed by instructing the relevant hardware through a computer program, and the computer program can be stored in a non-volatile computer-readable storage medium. When the computer program is executed, it can include the processes of the embodiments of the above-mentioned methods. Among them, any reference to the memory, database or other medium used in the embodiments provided in the present application can include at least one of non-volatile and volatile memory. Non-volatile memory can include read-only memory (ROM), magnetic tape, floppy disk, flash memory, optical memory, high-density embedded non-volatile memory, resistive random access memory (ReRAM), magnetoresistive random access memory (MRAM), ferroelectric random access memory (FRAM), phase change memory (PCM), graphene memory, etc. Volatile memory can include random access memory (RAM) or external cache memory, etc. As an illustration and not limitation, RAM can be in various forms, such as static random access memory (SRAM) or dynamic random access memory (DRAM). The database involved in each embodiment provided in this application may include at least one of a relational database and a non-relational database. Non-relational databases may include distributed databases based on blockchains, etc., but are not limited to this. The processor involved in each embodiment provided in this application may be a general-purpose processor, a central processing unit, a graphics processor, a digital signal processor, a programmable logic device, a data processing logic device based on quantum computing, etc., but are not limited to this.

[0213] The technical features of the above embodiments may be combined arbitrarily. To make the description concise, not all possible combinations of the technical features in the above embodiments are described. However, as long as there is no contradiction in the combination of these technical features, they should be considered to be within the scope of this specification.

[0214] The above-described embodiments only express several implementation methods of the present application, and the descriptions thereof are relatively specific and detailed, but they cannot be understood as limiting the scope of the present application. It should be pointed out that, for a person of ordinary skill in the art, several variations and improvements can be made without departing from the concept of the present application, and these all belong to the protection scope of the present application. Therefore, the protection scope of the present application shall be subject to the attached claims.

Claims

1. A data processing method based on blockchain, characterized in that: The method comprises: Receive a reputation authentication request sent by a target account, the reputation authentication request carries a target service identifier of a requested reputation service and reputation data to be authenticated, the reputation data to be authenticated is experience data of the target account in the real world, the reputation authentication request is a request to authenticate the experience data of the target account in the real world, and the reputation service is a service for authenticating the experience data of the target account in the real world; querying whether there is a target registered reputation service matching the target service identifier in the registered reputation service, wherein the registered reputation service is obtained based on a registration request for the reputation service by the certification authority account; If there is a target registered reputation service that matches the target service identifier, obtaining a corresponding target resolution contract based on the reputation resolution contract information in the target registered reputation service; Based on the data source information in the target registered reputation service, the target resolution contract is called to authenticate the reputation data to be authenticated to obtain an authentication result corresponding to the reputation authentication request.

2. The method according to claim 1, characterized in that: The reputation resolution contract information includes a reputation resolution contract address, the data source information includes a data source type and a corresponding verification data storage address, and the obtaining of a corresponding target resolution contract based on the reputation resolution contract information in the target registered reputation service includes: Verify whether the corresponding reputation resolution contract address exists in the target registered reputation service; When the target has a corresponding reputation resolution contract address in the registered reputation service, query the corresponding target resolution contract based on the reputation resolution contract address; When the target resolution contract is found, verify whether the corresponding data source information exists in the target registered reputation service; When the corresponding data source information exists in the target registered reputation service, verifying the validity of the data source information according to the data source type in the data source information and the corresponding verification data storage address; When the validity of the data source information is verified, the corresponding target resolution contract is obtained based on the reputation resolution contract address.

3. The method according to claim 1, characterized in that The data source information includes the off-chain data source type and the corresponding signature verification information storage address; The calling the target resolution contract to authenticate the reputation data to be authenticated based on the data source information in the target registered reputation service includes: Acquire signature data to be authenticated from the reputation data to be authenticated based on the off-chain data source type, wherein the signature data to be authenticated is obtained from the authentication agency account end corresponding to the authentication agency account, and the authentication agency account end corresponding to the authentication agency account digitally signs the experience data of the target account in the real world to obtain the signature data to be authenticated; Calling the target parsing contract to search for signature information matching the signature data to be authenticated in the storage space corresponding to the signature verification information storage address; When signature information matching the signature data to be authenticated is found, it is determined that the authentication of the reputation data to be authenticated is successful. When signature information matching the signature data to be authenticated is not found, it is determined that the authentication of the reputation data to be authenticated is failed.

4. The method according to claim 1, characterized in that The data source information includes an on-chain data source type and a corresponding on-chain verification information storage address; the data source information in the target registered reputation service is based on, and the target resolution contract is called to authenticate the reputation data to be authenticated, including: Based on the on-chain data source type, the target resolution contract is called to search for reputation data matching the reputation data to be authenticated in the storage block corresponding to the on-chain verification information storage address; When reputation data matching the reputation data to be authenticated is found in the storage block corresponding to the on-chain verification information storage address, determining that authentication of the reputation data to be authenticated is successful; When reputation data matching the reputation data to be authenticated is not found in the storage block corresponding to the on-chain verification information storage address, it is determined that authentication of the reputation data to be authenticated has failed.

5. The method according to claim 1, characterized in that: After the target resolution contract is called to authenticate the reputation data to be authenticated based on the data source information in the target registered reputation service to obtain an authentication result corresponding to the reputation authentication request, the method further includes: When the authentication result corresponding to the reputation authentication request is that the reputation data to be authenticated passes authentication, calling the reputation certification generation contract; Generate a reputation certificate for the reputation authentication request and an authenticated identifier corresponding to the reputation certificate through the reputation certificate generation contract; The reputation certificate, the authenticated identifier and the reputation data to be authenticated are associated and stored in a blockchain, and the authenticated identifier is returned to a request end corresponding to the reputation authentication request.

6. The method according to claim 5, characterized in that After the reputation certificate, the authenticated identifier and the reputation data to be authenticated are stored in association in the blockchain, the method further includes: Receiving a verification request for the reputation data to be verified, the verification request including the reputation data to be verified and an authenticated identifier to be verified corresponding to the reputation data to be verified; Searching the blockchain for a target authenticated identifier associated with the reputation data to be verified; When the target authenticated identifier is consistent with the authenticated identifier to be verified, a verification result of the reputation data to be verified is obtained, and the verification result of the reputation data to be verified is returned to the request end corresponding to the verification request; When the target authenticated identifier is not consistent with the authenticated identifier to be verified, a verification failure result of the reputation data to be verified is obtained, and the verification failure result of the reputation data to be verified is returned to the request end corresponding to the verification request.

7. The method according to claim 1, characterized in that The target registered reputation service also includes a reputation certification revocation flag; the method also includes: receiving a certification revocation request for the reputation data to be authenticated, the certification revocation request carrying an authenticated identifier corresponding to the reputation data to be authenticated and the target service identifier; When detecting that the reputation proof revocation identifier exists in the registered reputation service corresponding to the target service identifier, calling the reputation proof generation contract; Generate a reputation revocation certificate for the reputation certificate corresponding to the authenticated identifier through the reputation certificate generation contract; The reputation revocation certificate, the authenticated identifier, and the reputation data to be authenticated are associated and stored in a blockchain, and the reputation revocation certificate is returned to the requesting end corresponding to the certificate revocation request.

8. The method according to claim 1, characterized in that: The target registered reputation service also includes a reputation proof reservation mark; the method also includes: receiving a certification revocation request for the reputation data to be authenticated, the certification revocation request carrying an authenticated identifier corresponding to the reputation data to be authenticated and the target service identifier; When it is detected that the reputation certification reservation identifier exists in the registered reputation service corresponding to the target service identifier, a prompt message indicating that the reputation certification cannot be revoked is generated, and the prompt message indicating that the reputation certification cannot be revoked is sent to the request end corresponding to the certification revocation request.

9. The method according to claim 1, characterized in that: The method further comprises: When the authentication result corresponding to the reputation authentication request is successful authentication, generating authentication success prompt information, and returning the authentication success prompt information of the reputation authentication request to the target account; When the authentication result corresponding to the reputation authentication request is authentication failure, authentication failure prompt information is generated, and the authentication failure prompt information of the reputation authentication request is returned to the target account.

10. The method according to any one of claims 1 to 9, characterized in that: Before receiving the reputation authentication request sent by the target account, the method further includes: Obtaining a reputation service registration request sent by a certification authority account, the reputation service registration request carrying reputation service information, the reputation service information including a reputation data format to be registered, a reputation resolution contract address to be registered, and data source information to be registered; Invoking a reputation service registration contract based on the reputation service registration request, and verifying the legitimacy of the reputation data format to be registered through a preset reputation data format in the reputation service registration contract; Verify the legitimacy of the reputation resolution contract address to be registered through the contract address range in the reputation service registration contract; Performing data source deployment verification on the data source information through the reputation service registration contract; When the legitimacy verification of the reputation data format to be registered passes, the legitimacy verification of the reputation resolution contract address to be registered passes, and the data source deployment verification passes, a registered reputation service identifier of the reputation service information is generated through the reputation service registration contract; The reputation service information and the registered reputation service identifier are associated and written into the blockchain, and prompt information of successful registration is generated based on the registered reputation service identifier, and the prompt information of successful registration is returned to the target account.

11. The method according to claim 10, characterized in that The preset reputation data format includes reputation data general field information; The verifying the legitimacy of the reputation data format to be registered by using a preset reputation data format in the reputation service registration contract includes: Searching for the reputation data field information to be registered corresponding to the reputation data format to be registered in the reputation data general field information in the reputation service registration contract; When the field information of the reputation data to be registered is found, it is determined that the legitimacy verification of the format of the reputation data to be registered has passed; when the field information of the reputation data to be registered is not found, it is determined that the legitimacy verification of the format of the reputation data to be registered has not passed.

12. The method according to claim 10, characterized in that The verifying the legitimacy of the to-be-registered reputation resolution contract address through the contract address range in the reputation service registration contract includes: Searching for the reputation resolution contract address to be registered in the contract address range in the reputation service registration contract; When the reputation resolution contract address to be registered is found, a validity access signal is sent to the reputation resolution contract address to be registered through the reputation service registration contract; When a valid signal returned by the reputation resolution contract address to be registered in response to the validity access request is obtained, it is determined that the legitimacy verification of the reputation resolution contract address to be registered has passed.

13. The method according to claim 10, characterized in that The data source information includes an on-chain data source type and a corresponding on-chain verification information storage address, and performing data source deployment verification on the data source information through the reputation service registration contract includes: The reputation service registration contract uses the signature verification information storage address corresponding to the on-chain data source type to find the corresponding signature information storage block; When the corresponding signature information storage block is found, searching the signature information storage block for signature data corresponding to the format of the reputation data to be registered; When signature data corresponding to the format of the reputation data to be registered is found, it is determined that the data source deployment verification has passed.

14. The method according to claim 10, characterized in that The data source information includes an off-chain data source type and a corresponding signature verification information storage address, and performing data source deployment verification on the data source information through the reputation service registration contract includes: The reputation service registration contract uses the on-chain verification information storage address corresponding to the off-chain data source type to find the corresponding verification information storage block; When the corresponding verification information storage block is found, searching the verification information storage block for reputation data corresponding to the reputation data format to be registered; When reputation data corresponding to the format of the reputation data to be registered is found, it is determined that the data source deployment verification has passed.

15. The method according to claim 10, characterized in that The reputation service information also includes reputation certification revocation information, and the reputation certification revocation information includes a reputation certification revocation mark or a reputation certification retention mark.

16. The method according to claim 1, characterized in that The reputation authentication request also carries a blockchain identifier, and the querying whether there is a target registered reputation service matching the target service identifier in the registered reputation services includes: Finding a corresponding target blockchain based on the blockchain identifier, and searching the target blockchain for the registered reputation service; The registered reputation services are queried to determine whether there is a target registered reputation service that matches the target service identifier.

17. A data processing device based on blockchain, characterized in that: The device comprises: A request receiving module, configured to receive a reputation authentication request sent by a target account, wherein the reputation authentication request carries a target service identifier of a requested reputation service and reputation data to be authenticated, wherein the reputation data to be authenticated is experience data of the target account in the real world, the reputation authentication request is a request to authenticate the experience data of the target account in the real world, and the reputation service is a service to authenticate the experience data of the target account in the real world; A matching module, used for querying whether there is a target registered reputation service matching the target service identifier in the registered reputation service, wherein the registered reputation service is obtained based on a registration request for the reputation service by the certification authority account; A contract acquisition module, configured to acquire a corresponding target resolution contract based on the reputation resolution contract information in the target registered reputation service if there is a target registered reputation service matching the target service identifier; The data authentication module is used to call the target resolution contract to authenticate the reputation data to be authenticated based on the data source information in the target registered reputation service, so as to obtain an authentication result corresponding to the reputation authentication request.

18. A computer device comprising a memory and a processor, wherein the memory stores a computer program, wherein: When the processor executes the computer program, the steps of the method according to any one of claims 1 to 16 are implemented.

19. A computer-readable storage medium having a computer program stored thereon, characterized in that: When the computer program is executed by a processor, the steps of the method according to any one of claims 1 to 16 are implemented.

20. A computer program product, comprising a computer program, characterized in that When the computer program is executed by a processor, the steps of the method according to any one of claims 1 to 16 are implemented.

Images