Blockchain multi-chain mutual trust method and system based on secondary on-chain

Abstract

The application provides a kind of based on secondary chain's blockchain multi-chain mutual trust method and system, comprising: data storage step: the data to be stored is uploaded to the storage platform, and the data is encrypted and stored by blockchain, and the corresponding storage hash and block information are generated after storage success;Second chain step: the storage chain is formed by storing the storage hash on another chain;Certificate generation step: for the data stored successfully, generate certificate file through H5 page and PDF file;Storage query step: when taking evidence, evidence is inquired through the query page of storage platform;Evidence verification step: evidence data is verified through the storage platform.The application solves the problem of non-interoperability of alliance chain platform data by adopting the secondary chain blockchain multi-chain mutual trust structure, so that the business perspective achieves the effect of one place on chain and multiple uses.

Description

Technical Field

[0001] This invention relates to the field of blockchain technology, and more specifically, to a method and system for multi-chain mutual trust based on secondary on-chaining. Background Technology

[0002] Currently, third-party clients need to perform development integration when connecting to Company A's blockchain, and a similar amount of development is required when connecting to Company B. To reduce the workload for these third-party clients, it is now necessary to establish a seamless blockchain integration process between Company A and Company B.

[0003] By establishing a blockchain front-end service to connect with application on-chain, the convenience of application on-chain can be improved. Existing technology (Chinese patent application number CN202110701778.5, which discloses "an automated system and method for blockchain on-chain") can better connect to the business layer, but it does not consider how to handle system interaction when crossing chains. If a business wants to connect to two blockchains for evidence storage, it needs to connect to each blockchain separately. If the two blockchains have already cross-chained on-chain, it can be used in multiple places after being uploaded to one blockchain. Summary of the Invention

[0004] In view of the shortcomings of the existing technology, the purpose of this invention is to provide a blockchain multi-chain mutual trust method and system based on secondary on-chain.

[0005] The blockchain multi-chain mutual trust method based on secondary on-chaining provided by the present invention includes:

[0006] Data notarization steps: Upload the data that needs to be notarized to the notarization platform, encrypt the data and then use the blockchain for notarization. After successful notarization, the corresponding notarization hash and block information are generated.

[0007] Secondary on-chain step: Forming an evidence storage chain by storing the evidence storage hash on another chain;

[0008] Certificate generation steps: Generate a certificate file from the successfully stored data using an H5 page and a PDF file;

[0009] Evidence search steps: When collecting evidence, search for evidence through the search page of the evidence storage platform;

[0010] Evidence verification steps: Verify the evidence data through the evidence storage platform.

[0011] Preferably, the secondary on-chain step includes: the business party requests the blockchain-1 front-end service to upload data to the blockchain and generate a blockchain-1 notarization number; the blockchain-1 front-end service requests the blockchain-2 front-end service to store the notarization hash of blockchain-1 into blockchain-2; the blockchain-2 front-end service returns the notarization information of blockchain-2 to the blockchain-1 front-end service; and the blockchain-1 front-end service returns the notarization information of blockchain-1 and blockchain-2 to the business party.

[0012] Preferably, the evidence query step includes: obtaining the evidence hash and authorization code provided by the evidence registrant when submitting the evidence, querying the evidence data uploaded to the blockchain or downloading the evidence file uploaded to the blockchain, and if the evidence content of the blockchain being queried is the evidence hash of another blockchain, then automatically querying the evidence information of that blockchain and returning it to the business party.

[0013] Preferably, the evidence verification step includes: the certified user submits the original data or original file of the evidence to be verified on the evidence verification page, and provides the notarization hash obtained during notarization. After submission for verification, if the evidence information does not exist, a cross-chain query is automatically performed through the front-end service. If the evidence information can be found and the submitted data is consistent with the on-chain data, it means that the submitted evidence has not been tampered with since notarization and is valid evidence data. At this time, the verification result is returned; otherwise, the verification fails.

[0014] Preferably, the cross-chain query process is as follows: Blockchain 1 front-end service requests Blockchain 2 front-end service to query the evidence storage data uploaded from Blockchain 2; Blockchain 2 front-end service requests Blockchain 2 to query block information; Blockchain 2 returns the evidence storage data to Blockchain 2 front-end service; Blockchain 2 front-end service returns the evidence storage data to Blockchain 1 front-end service; and Blockchain 1 front-end service returns the evidence storage data to the business party.

[0015] The blockchain multi-chain mutual trust system based on secondary on-chaining provided by the present invention includes:

[0016] Data storage module: Upload the data that needs to be stored to the storage platform, encrypt the data and then use the blockchain for storage. After successful storage, the corresponding storage hash and block information are generated.

[0017] Secondary on-chain module: Forms an evidence storage chain by storing the evidence storage hash on another chain;

[0018] Certificate generation module: Generates certificate files from successfully stored data via H5 pages and PDF files;

[0019] Evidence storage query module: Evidence can be queried through the query page of the evidence storage platform when collecting evidence;

[0020] Evidence verification module: Verify evidence data through the evidence storage platform.

[0021] Preferably, the secondary on-chain module includes: the business party requests the blockchain-1 front-end service to upload data to the blockchain and generate a blockchain-1 notarization number; the blockchain-1 front-end service requests the blockchain-2 front-end service to store the notarization hash of blockchain-1 into blockchain-2; the blockchain-2 front-end service returns the notarization information of blockchain-2 to the blockchain-1 front-end service; and the blockchain-1 front-end service returns the notarization information of blockchain-1 and blockchain-2 to the business party.

[0022] Preferably, the evidence storage query module includes: the evidence storage hash obtained when submitting the evidence storage and the authorization code provided by the evidence storage party; querying the evidence storage data uploaded to the blockchain or downloading the evidence files uploaded to the blockchain; if the evidence storage content of the blockchain being queried is the evidence storage hash of another blockchain, then automatically querying the evidence storage information of that blockchain and returning it to the business party.

[0023] Preferably, the evidence verification module includes: the certified user submits the original data or original file of the evidence to be verified on the evidence verification page, and provides the notarization hash obtained during notarization. After submission for verification, if the evidence information does not exist, a cross-chain query is automatically performed through the front-end service. If the evidence information can be found and the submitted data is consistent with the on-chain data, it means that the submitted evidence has not been tampered with since notarization and is valid evidence data. At this time, the verification result is returned; otherwise, the verification fails.

[0024] Preferably, the cross-chain query process is as follows: Blockchain 1 front-end service requests Blockchain 2 front-end service to query the evidence storage data uploaded from Blockchain 2; Blockchain 2 front-end service requests Blockchain 2 to query block information; Blockchain 2 returns the evidence storage data to Blockchain 2 front-end service; Blockchain 2 front-end service returns the evidence storage data to Blockchain 1 front-end service; and Blockchain 1 front-end service returns the evidence storage data to the business party.

[0025] Compared with the prior art, the present invention has the following beneficial effects:

[0026] This invention establishes its own consortium blockchain platform among multiple organizations. Data uploaded to the blockchain in one place can be queried and verified across multiple consortium blockchains, reducing the cost for third-party businesses to connect to multiple blockchains simultaneously. The same business point only needs to be uploaded to any one blockchain system, and all uploaded data will be synchronized. By adopting a multi-chain mutual trust structure with secondary on-chain uploading, the problem of data incompatibility between consortium blockchain platforms is solved, enabling business parties to achieve the effect of uploading data to one place and using it in multiple places. Attached Figure Description

[0027] Other features, objects, and advantages of the present invention will become more apparent from the following detailed description of non-limiting embodiments with reference to the accompanying drawings:

[0028] Figure 1 This is a flowchart of the blockchain multi-chain mutual trust technology solution based on secondary on-chaining of the present invention. Detailed Implementation

[0029] The present invention will now be described in detail with reference to specific embodiments. These embodiments will help those skilled in the art to further understand the present invention, but do not limit the invention in any way. It should be noted that those skilled in the art can make several changes and improvements without departing from the concept of the present invention. These all fall within the protection scope of the present invention.

[0030] Example 1:

[0031] This invention provides a blockchain multi-chain mutual trust method based on secondary on-chain, comprising:

[0032] Data notarization steps: When data needs to be notarized, the data to be notarized is uploaded to the notarization platform. After the data is encrypted, it is notarized through the blockchain. After successful notarization, the corresponding notarization hash and block information will be generated.

[0033] The second on-chain step involves creating an evidence storage chain by storing the evidence hash on another blockchain. The business party requests the Blockchain 1 front-end service to upload data to the blockchain and generate a Blockchain 1 evidence storage number. The Blockchain 1 front-end service then requests the Blockchain 2 front-end service to store the evidence hash from Blockchain 1 into Blockchain 2. The Blockchain 2 front-end service returns the evidence storage information from Blockchain 2 to the Blockchain 1 front-end service. Finally, the Blockchain 1 front-end service returns the evidence storage information from both Blockchain 1 and Blockchain 2 to the business party.

[0034] Certificate generation steps: For successfully stored data, a certificate file is generated via an H5 page and a PDF file; for data that fails to be stored, the business party is directly notified of the storage failure in the logic of the on-chain process, the storage operation is terminated, and the business party can re-initiate the storage process.

[0035] Evidence retrieval steps: When evidence needs to be retrieved, evidence can be retrieved through the query page of the evidence platform. Submit the evidence hash obtained during evidence retrieval and the authorization code provided by the evidence retrieval party to query the evidence data on the blockchain or download the evidence files on the blockchain. If the evidence content of the blockchain being queried is the evidence hash of another blockchain, the platform will automatically query the evidence information of that blockchain and return it to the business party.

[0036] Evidence verification steps: Evidence data can be verified through the evidence storage platform. Authenticated users can submit the original data or original files of the evidence to be verified on the evidence verification page and provide the storage hash obtained during storage. After submission, if the evidence information does not exist, a cross-chain query will be automatically performed through the front-end service. If the evidence information can be found and the submitted data is consistent with the on-chain data, it means that the submitted evidence has not been tampered with since storage and is valid evidence data. At this time, the verification result is returned. Otherwise, the verification fails.

[0037] The cross-chain query process is as follows: Blockchain 1 front-end service requests Blockchain 2 front-end service to query the evidence storage data uploaded from Blockchain 2; Blockchain 2 front-end service requests Blockchain 2 to query block information; Blockchain 2 returns the evidence storage data to Blockchain 2 front-end service; Blockchain 2 front-end service returns the evidence storage data to Blockchain 1 front-end service; and Blockchain 1 front-end service returns the evidence storage data to the business party.

[0038] Example 2:

[0039] The present invention also provides a blockchain multi-chain mutual trust system based on secondary on-chain. The blockchain multi-chain mutual trust system based on secondary on-chain can be implemented by executing the process steps of the blockchain multi-chain mutual trust method based on secondary on-chain. That is, those skilled in the art can understand the blockchain multi-chain mutual trust method based on secondary on-chain as a preferred embodiment of the blockchain multi-chain mutual trust system based on secondary on-chain.

[0040] The blockchain multi-chain mutual trust system based on secondary on-chain provided by the present invention includes: a data storage module: uploading the data to be stored to the storage platform, encrypting the data, and then using the blockchain for solidification; generating corresponding storage hash and block information after successful storage; a secondary on-chain module: forming a storage chain by storing the storage hash on another chain; a certificate generation module: generating certificate files for successfully stored data through H5 pages and PDF files; a storage query module: querying evidence through the query page of the storage platform during evidence collection; and an evidence verification module: verifying evidence data through the storage platform.

[0041] The secondary on-chain module includes: the business party requests the blockchain-1 front-end service to upload data to the blockchain and generate a blockchain-1 notarization number; the blockchain-1 front-end service requests the blockchain-2 front-end service to store the notarization hash of blockchain-1 into blockchain-2; the blockchain-2 front-end service returns the notarization information of blockchain-2 to the blockchain-1 front-end service; and the blockchain-1 front-end service returns the notarization information of blockchain-1 and blockchain-2 to the business party.

[0042] The evidence storage query module includes: obtaining the evidence storage hash and authorization code provided by the evidence storage party when submitting the evidence storage, querying the evidence storage data uploaded to the chain or downloading the evidence files uploaded to the chain, and automatically querying the evidence storage information of the blockchain and returning it to the business party if the evidence storage content of the blockchain being queried is the evidence storage hash of another blockchain.

[0043] The evidence verification module includes: authenticating users submit the original data or original files of the evidence to be verified on the evidence verification page, and provide the notarization hash obtained during notarization. After submission for verification, if the evidence information does not exist, a cross-chain query is automatically performed through the front-end service. If the evidence information can be found and the submitted data is consistent with the on-chain data, it means that the submitted evidence has not been tampered with since notarization and is valid evidence data. At this time, the verification result is returned; otherwise, the verification fails.

[0044] The cross-chain query process is as follows: Blockchain 1 front-end service requests Blockchain 2 front-end service to query the evidence storage data uploaded from Blockchain 2; Blockchain 2 front-end service requests Blockchain 2 to query block information; Blockchain 2 returns the evidence storage data to Blockchain 2 front-end service; Blockchain 2 front-end service returns the evidence storage data to Blockchain 1 front-end service; and Blockchain 1 front-end service returns the evidence storage data to the business party.

[0045] like Figure 1 The process of the blockchain multi-chain mutual trust method based on secondary on-chaining of the present invention is as follows:

[0046] The business initiates a request to the Blockchain 1 front-end service to upload data to the blockchain. The Blockchain 1 front-end service uploads the data to the blockchain on Blockchain 1, and Blockchain 1 returns the evidence storage information to the Blockchain 1 front-end service. The Blockchain 1 front-end service then sends a request to the Blockchain 2 front-end service for a second upload based on the evidence storage information from Blockchain 1. The Blockchain 2 front-end service uploads the data to the blockchain on Blockchain 2, and Blockchain 2 returns the evidence storage information from the second upload to the Blockchain 1 front-end service. The Blockchain 1 front-end service then returns the evidence storage information from both Blockchain 1 and Blockchain 2 to the business.

[0047] The business initiates a blockchain evidence storage query request to the Blockchain 1 front-end service. The Blockchain 1 front-end service then requests to query block information from Blockchain 1. Blockchain 1 returns evidence storage information to the Blockchain 1 front-end service. If the required data is found in Blockchain 1, the Blockchain 1 front-end service returns the evidence storage information to the business. Otherwise, the Blockchain 1 front-end service sends a request to the Blockchain 2 front-end service to query the evidence storage data uploaded to Blockchain 2. The Blockchain 2 front-end service then requests to query block information from Blockchain 2. Blockchain 2 returns the evidence storage data to the Blockchain 2 front-end service, which in turn returns the evidence storage data to the Blockchain 1 front-end service. Finally, the Blockchain 1 front-end service returns the evidence storage data to the business.

[0048] Alternatively, the business can initiate a blockchain evidence storage query request to the Blockchain 2 front-end service. The Blockchain 2 front-end service then requests to query block information from Blockchain 2. Blockchain 2 returns evidence storage data to the Blockchain 2 front-end service. If the required data is found in Blockchain 2, the Blockchain 2 front-end service returns the evidence storage data to the business. Otherwise, the Blockchain 2 front-end service requests to query evidence storage information from the Blockchain 1 front-end service, and the Blockchain 1 front-end service requests to query block information from Blockchain 1. Blockchain 1 returns evidence storage data to the Blockchain 1 front-end service, which in turn returns the evidence storage data to the Blockchain 2 front-end service. The Blockchain 2 front-end service then sends the evidence storage data to the business.

[0049] Those skilled in the art will understand that, in addition to implementing the system, apparatus, and their modules provided by this invention in purely computer-readable program code, the same program can be implemented in the form of logic gates, switches, application-specific integrated circuits, programmable logic controllers, and embedded microcontrollers by logically programming the method steps. Therefore, the system, apparatus, and their modules provided by this invention can be considered a hardware component, and the modules included therein for implementing various programs can also be considered structures within the hardware component; alternatively, modules for implementing various functions can be considered both software programs implementing the method and structures within the hardware component.

[0050] Specific embodiments of the present invention have been described above. It should be understood that the present invention is not limited to the specific embodiments described above, and those skilled in the art can make various changes or modifications within the scope of the claims, which do not affect the essence of the present invention. Unless otherwise specified, the embodiments and features described in this application can be arbitrarily combined with each other.

Claims

1. A blockchain multi-chain mutual trust method based on secondary on-chaining, characterized in that, include: Data notarization steps: Upload the data that needs to be notarized to the notarization platform, encrypt the data and then use the blockchain for notarization. After successful notarization, the corresponding notarization hash and block information are generated. Secondary on-chain step: Forming an evidence storage chain by storing the evidence storage hash on another chain; Certificate generation steps: Generate a certificate file from the successfully stored data using an H5 page and a PDF file; Evidence search steps: When collecting evidence, search for evidence through the search page of the evidence storage platform; Evidence verification steps: Verify evidence data through the evidence storage platform; The second on-chain step includes: the business party requests the blockchain 1 front-end service to upload data to the blockchain and generate a blockchain 1 evidence number; the blockchain 1 front-end service requests the blockchain 2 front-end service to store the blockchain 1 evidence hash into the blockchain 2; the blockchain 2 front-end service returns the blockchain 2 evidence information to the blockchain 1 front-end service; and the blockchain 1 front-end service returns the blockchain 1 and blockchain 2 evidence information to the business party. The evidence storage query step includes: obtaining the evidence storage hash and authorization code provided by the evidence storage party when submitting the evidence storage, querying the evidence storage data on the blockchain or downloading the evidence file on the blockchain, and if the evidence storage content of the blockchain being queried is the evidence storage hash of another blockchain, then automatically querying the evidence storage information of that blockchain and returning it to the business party. The evidence verification steps include: the certified user submits the original data or original file of the evidence to be verified on the evidence verification page, and provides the notarization hash obtained during notarization. After submission for verification, if the evidence information does not exist, a cross-chain query is automatically performed through the front-end service. If the evidence information can be found and the submitted data is consistent with the on-chain data, it means that the submitted evidence has not been tampered with since notarization and is valid evidence data. At this time, the verification result is returned; otherwise, the verification fails.

2. The blockchain multi-chain mutual trust method based on secondary on-chain as described in claim 1, characterized in that, The cross-chain query process is as follows: Blockchain 1 front-end service requests Blockchain 2 front-end service to query the evidence storage data uploaded from Blockchain 2; Blockchain 2 front-end service requests Blockchain 2 to query block information; Blockchain 2 returns the evidence storage data to Blockchain 2 front-end service; Blockchain 2 front-end service returns the evidence storage data to Blockchain 1 front-end service; and Blockchain 1 front-end service returns the evidence storage data to the business party.

3. A blockchain multi-chain mutual trust system based on secondary on-chaining, characterized in that, include: Data storage module: Upload the data that needs to be stored to the storage platform, encrypt the data and then use the blockchain for storage. After successful storage, the corresponding storage hash and block information are generated. Secondary on-chain module: Forms an evidence storage chain by storing the evidence storage hash on another chain; Certificate generation module: Generates certificate files from successfully stored data via H5 pages and PDF files; Evidence storage query module: Evidence can be queried through the query page of the evidence storage platform when collecting evidence; Evidence verification module: Verifies evidence data through the evidence storage platform; The secondary on-chain module includes: the business party requests the blockchain 1 front-end service to put the data on the blockchain and generate the blockchain 1 evidence number; the blockchain 1 front-end service requests the blockchain 2 front-end service to store the blockchain 1 evidence hash into the blockchain 2; the blockchain 2 front-end service returns the blockchain 2 evidence information to the blockchain 1 front-end service; and the blockchain 1 front-end service returns the blockchain 1 and blockchain 2 evidence information to the business party. The evidence storage query module includes: the evidence storage hash obtained when submitting evidence storage and the authorization code provided by the evidence storage party; querying the evidence storage data uploaded to the chain or downloading the evidence files uploaded to the chain; if the evidence storage content of the blockchain being queried is the evidence storage hash of another blockchain, it will automatically query the evidence storage information of that blockchain and return it to the business party. The evidence verification module includes: authenticating users submit the original data or original files of the evidence to be verified on the evidence verification page, and provide the notarization hash obtained during notarization. After submission for verification, if the evidence information does not exist, a cross-chain query is automatically performed through the front-end service. If the evidence information can be found and the submitted data is consistent with the on-chain data, it means that the submitted evidence has not been tampered with since notarization and is valid evidence data. At this time, the verification result is returned; otherwise, the verification fails.

4. The blockchain multi-chain mutual trust system based on secondary on-chain as described in claim 3, characterized in that, The cross-chain query process is as follows: Blockchain 1 front-end service requests Blockchain 2 front-end service to query the evidence storage data uploaded from Blockchain 2; Blockchain 2 front-end service requests Blockchain 2 to query block information; Blockchain 2 returns the evidence storage data to Blockchain 2 front-end service; Blockchain 2 front-end service returns the evidence storage data to Blockchain 1 front-end service; and Blockchain 1 front-end service returns the evidence storage data to the business party.

Images