Data security transmission method based on blockchain

Abstract

The present invention relates to the field of blockchain technology, and in particular to a data security transmission method based on blockchain. The method comprises the following steps: obtaining the original data to be transmitted, slicing and encrypting the original data to be transmitted, and obtaining encrypted slice data; generating a labeled storage strategy according to a preset multi-chain network topology and the encrypted slice data, and obtaining labeled storage strategy data; determining the storage target chain of the encrypted slice data according to the labeled storage strategy data, and obtaining the target blockchain node data; constructing a storage transaction for the encrypted slice data, and obtaining storage transaction data; performing cross-chain aggregate storage proof analysis according to the target blockchain node data and the storage transaction data, and obtaining aggregate storage proof data. The present invention effectively improves the overall performance and scalability of data transmission through cross-chain parallelization and interaction of multiple blockchains, and avoids the bottleneck limitation of a single blockchain.

Description

Technical Field

[0001] The present invention relates to the technical field of blockchain, and in particular to a data security transmission method based on blockchain. Background Art

[0002] Blockchain technology has shown broad application prospects in the field of secure data transmission due to its decentralization, immutability, and traceability. In recent years, academia and industry have been actively exploring blockchain-based data security transmission solutions and have achieved certain research results.

[0003] Early research focused on using blockchain to build secure and reliable data transmission channels. For example, designing blockchain-based data encryption and access control mechanisms, and using blockchain consensus mechanisms and smart contracts to implement trusted verification and auditing of data transmission processes. These solutions have solved the security risks of data transmission in traditional networks to a certain extent, but they have also exposed the performance bottleneck of blockchain itself.

[0004] As data scale grows and application scenarios become more complex, the processing capacity of a single blockchain is unable to meet the needs of high-concurrency, high-throughput data transmission. The transaction processing speed and storage capacity of blockchains are restricted by factors such as the underlying consensus mechanism and network bandwidth, resulting in low data transmission efficiency and insufficient scalability.

[0005] In general, while existing blockchain-based data security transmission methods solve traditional network security problems, they also face scalability challenges brought about by the performance bottleneck of the blockchain itself. Summary of the invention

[0006] Based on this, it is necessary to provide a blockchain-based data security transmission method to solve at least one of the above technical problems.

[0007] To achieve the above purpose, a data security transmission method based on blockchain includes the following steps:

[0008] Step S1: Obtain the original data to be transmitted, slice and encrypt the original data to be transmitted, and obtain encrypted slice data; generate a labeled storage strategy according to the preset multi-chain network topology structure and the encrypted slice data, and obtain labeled storage strategy data;

[0009] Step S2: Determine the storage target chain of the encrypted slice data according to the labeled storage strategy data to obtain the target blockchain node data; construct a storage transaction for the encrypted slice data to obtain storage transaction data; perform cross-chain aggregate storage proof analysis according to the target blockchain node data and storage transaction data to obtain aggregate storage proof data;

[0010] Step S3: Obtain the recipient's identity data; perform access request initiation processing based on the recipient's identity data and the aggregated storage proof data to obtain access request data; generate access challenge based on the access request data to obtain access challenge data; perform lightweight cross-chain verification based on the access challenge data to obtain local verification proof data; perform cross-chain access permission analysis based on the local verification proof data and the main chain smart contract to obtain cross-chain access permission data;

[0011] Step S4: The cross-chain access permission data is transmitted to the receiving party to initiate an extraction request, and the extraction request data is obtained; the target blockchain node constructs a zero-knowledge proof that the node has a slice according to the extraction request data, and obtains zero-knowledge proof data; the zero-knowledge proof data is transmitted to the receiving party, and the data slice is confirmed to obtain data slice confirmation data; the encrypted data segment transmission processing is performed according to the data slice confirmation data to obtain an encrypted data segment set;

[0012] Step S5: The receiver decrypts the encrypted data slices of the encrypted data segment set to obtain plaintext data slices; reconstructs the Merkle root calculation based on the labeled storage strategy data and the plaintext data slices to obtain reconstructed Merkle root data; performs a Merkle root comparison on the reconstructed Merkle root data and the Merkle root data in the labeled storage strategy data and outputs the original data to obtain the original data.

[0013] The present invention ensures the confidentiality and integrity of data through data slicing and encryption. At the same time, a label storage strategy is generated according to the multi-chain network topology and data characteristics, thereby realizing safe, reliable and efficient storage of data. Data slices are cross-chain stored according to the label storage strategy, and the integrity and traceability of the data are guaranteed through the cross-chain aggregate storage proof mechanism, thereby realizing multi-chain data collaborative management. Through the recipient identity authentication, access challenge, lightweight cross-chain verification and signature slicing technology, secure and controllable data access control is realized, ensuring that only authorized users can access the data. By using zero-knowledge proof technology, while protecting data privacy, the data holding status of the target blockchain node is verified, thereby realizing secure data extraction and transmission. Through mechanisms such as data integrity verification, data decryption, data reorganization and Merkel tree verification, it is ensured that the recipient can obtain the original data safely and completely, thereby ensuring the reliability and security of data transmission. Therefore, the present invention provides a data security transmission method based on blockchain. The scalability problem faced by the existing data security transmission method based on blockchain is solved. By distributing data slices and storing them in multiple blockchains, and using cross-chain technology to achieve interoperability and synchronization between blockchains, data transmission, storage, access control, and extraction can be processed in parallel on multiple chains, thereby effectively improving overall performance and scalability and avoiding the bottleneck limitations of a single blockchain. At the same time, multi-chain storage also improves data security and reliability.

[0014] Preferably, step S1 comprises the following steps:

[0015] Step S11: obtaining the original data to be transmitted through the sender; slicing the original data to be transmitted to obtain a data slice set;

[0016] Step S12: Generate slice information metadata according to the data slice set to obtain slice information metadata;

[0017] Step S13: Binding the slice information metadata and the data slice set to obtain a slice metadata pair;

[0018] Step S14: Slice encrypt the slice metadata pair to obtain encrypted slice data;

[0019] Step S15: Generate slice storage strategy recommendations based on the preset multi-chain network topology and encrypted slice data to obtain slice storage strategy recommendation data; integrate labeled storage strategy data based on the slice storage strategy recommendation data to obtain labeled storage strategy data.

[0020] The present invention can effectively reduce the size of a single data block and improve the efficiency and flexibility of data transmission by slicing the original data to be transmitted. At the same time, data slicing also provides a basis for subsequent distributed storage and access control. Generating slice information metadata can record important information such as identity information, size, format, checksum, etc. of each data slice, which is convenient for subsequent management, verification and retrieval of data slices, and improves the efficiency and security of data processing. Binding the slice information metadata with the corresponding data slice can ensure that each data slice is always associated with its metadata information, which is convenient for data management and use, and also improves data security and traceability. Encrypting the slice metadata can effectively protect the confidentiality and integrity of the data slice during transmission and storage, prevent data leakage and tampering, and improve data security. Generate labeled storage strategy data based on the multi-chain network topology and encrypted slice data characteristics, and the data slices can be intelligently distributed and stored on different blockchains, making full use of the advantages of the multi-chain network to improve the security, reliability and scalability of data storage.

[0021] Preferably, step S15 comprises the following steps:

[0022] Step S151: extracting slice features from the encrypted slice data to obtain a slice feature set;

[0023] Step S152: inputting the slice feature set into the pre-trained machine learning model, generating slice storage strategy recommendations according to the preset multi-chain network topology structure, and obtaining slice storage strategy recommendation data;

[0024] Step S153: Generate a data label according to the slice storage strategy suggestion data and the encrypted slice data to obtain a data label;

[0025] Step S154: construct a Merkle tree according to the data tag and calculate the root hash value of the tree to obtain the Merkle tree root hash value;

[0026] Step S155: Integrate the Merkle tree root hash value, data label, and encrypted slice data into labeled storage strategy data to obtain labeled storage strategy data.

[0027] The present invention can quantify the key feature information of data slices by extracting features from encrypted slice data, provide effective input data for subsequent machine learning models, and improve the accuracy and scientificity of storage strategy recommendations. Using a pre-trained machine learning model, the optimal slice storage strategy recommendation can be intelligently generated according to slice features and multi-chain network topology, and slice data with different features can be reasonably allocated to different blockchains, making full use of the resources of each blockchain to improve the efficiency and security of data storage. According to the slice storage strategy recommendation data, data labels can be generated, and important information such as storage location and identity can be added to each slice data, which is convenient for subsequent data positioning, retrieval and management, and improves the efficiency and security of data processing. Using data labels to construct a Merkle tree and calculate the root hash value of the tree can ensure the integrity and immutability of the data label. Any modification of the data label will cause the change of the root hash value, thereby improving the security and credibility of the data. Integrating the Merkle tree root hash value, data label and encrypted slice data into the labeled storage strategy data can organically combine the data storage strategy, integrity verification information and the data itself, facilitate subsequent data storage, verification and extraction, and improve the efficiency and security of data management.

[0028] Preferably, step S2 comprises the following steps:

[0029] Step S21: Perform labeling strategy parsing on the labeling storage strategy data through the blockchain node to obtain Merkle tree root data;

[0030] Step S22: performing encrypted slice verification on the encrypted slice data according to the Merkle tree root data to obtain encrypted slice verification data;

[0031] Step S23: Determine the storage target chain of the encrypted slice data according to the encrypted slice verification data to obtain the target blockchain node data; construct a storage transaction for the encrypted slice data to obtain storage transaction data;

[0032] Step S24: Perform storage proof cross-chain analysis based on the target blockchain node data and the storage transaction data to obtain storage proof cross-chain data;

[0033] Step S25: Generate aggregated storage proof based on the storage proof cross-chain data to obtain aggregated storage proof data.

[0034] By parsing the labeled storage strategy data, the blockchain node can quickly obtain the Merkle tree root data of the present invention, provide a basis for subsequent data verification, and ensure that the data has not been tampered with during transmission and storage. By using the Merkle tree root data to verify the encrypted slice data, the integrity of the data can be efficiently confirmed, the data can be prevented from being maliciously tampered with or damaged, and the security of data storage can be improved. According to the encrypted slice verification results and the preset storage strategy, the storage target blockchain and node information of each slice can be accurately determined, and the corresponding storage transaction data can be constructed to prepare for the cross-chain storage of the data. By performing cross-chain analysis on the storage proof on the target blockchain, it can be ensured that the data is securely stored on the target blockchain, and complete storage proof information can be obtained to provide support for subsequent data verification and traceability. Aggregating the storage proof data of all relevant blockchains to generate aggregated storage proof data can provide a global view of data integrity and security, which is convenient for data users to verify and manage the storage status of the data.

[0035] Preferably, step S24 comprises the following steps:

[0036] Step S241: performing inter-node consensus confirmation on the stored transaction data according to the target blockchain node data to obtain inter-node consensus data;

[0037] Step S242: The stored transaction data is packaged into blocks according to the consensus data between nodes and added to the target blockchain in the target blockchain node data to obtain encrypted slice storage data;

[0038] Step S243: Generate storage proof for the encrypted slice storage data according to the target blockchain node data to obtain storage proof data;

[0039] Step S244: performing storage proof anchoring processing on the storage proof data to obtain storage proof anchoring data;

[0040] Step S245: Use the preset cross-chain bridge to perform storage proof cross-chain collection on the target blockchain node data according to the storage proof anchor data to obtain storage proof cross-chain data.

[0041] The present invention can ensure that all nodes reach a consensus on the transaction by consensus confirmation of the storage transaction data between the target blockchain nodes, prevent malicious nodes from tampering with or forging transaction data, and improve the reliability and security of data storage. Packing the storage transaction data confirmed by consensus into blocks and adding them to the target blockchain can ensure the immutability and traceability of the data. Any modification to the data will be recorded on the blockchain, improving the reliability and credibility of data storage. Generating storage proof data can prove that the data has been successfully stored on the target blockchain, providing a basis for subsequent data verification and tracing, and enhancing the credibility of data storage. Anchoring the storage proof data can fix it on the blockchain to prevent it from being tampered with or deleted, further improving the credibility and durability of the storage proof. Using a cross-chain bridge to collect storage proofs on the target blockchain and other related chains, complete storage proof information can be obtained, providing more comprehensive support for subsequent data verification and tracing, while improving the efficiency of cross-chain data management.

[0042] Preferably, step S3 comprises the following steps:

[0043] Step S31: Obtain the recipient's identity data; perform access request initiation processing based on the recipient's identity data and the aggregated storage certification data to obtain access request data;

[0044] Step S32: The access request data is transmitted to the main chain smart contract of the blockchain, and the access permission is verified to obtain the access permission data;

[0045] Step S33: Generate access challenge according to access permission data and access request data to obtain access challenge data;

[0046] Step S34: transmitting the access challenge data to a preset authorization node, performing access challenge analysis, and obtaining access challenge analysis data;

[0047] Step S35: Perform lightweight cross-chain verification based on the access challenge parsing data to obtain local verification proof data;

[0048] Step S36: Generate a signature copy according to the local verification proof data to obtain signature copy data; collect signature copies of the signature copy data and perform copy verification on the signature copy data through the main chain smart contract to obtain copy verification data;

[0049] Step S37: When the number of signature copies in the copy verification data is greater than or equal to the preset signature copy threshold, a cross-chain access permission is generated to obtain cross-chain access permission data.

[0050] The present invention can ensure that only authorized users can initiate data access requests and improve the security of data access by obtaining the identity data of the recipient and combining the aggregated storage proof data to generate access request data. The access request data is transmitted to the main chain smart contract for access permission verification, and the open, transparent and tamper-proof characteristics of the smart contract can be used to ensure that the access control policy is strictly implemented to prevent unauthorized access. The access challenge is generated according to the access permission and the request content, which can further verify the identity and authority of the recipient and improve the security of data access. The access challenge data is transmitted to the preset authorization node for parsing, and the complex logic of access control can be dispersed to different nodes, thereby improving the scalability and fault tolerance of the system. Through lightweight cross-chain verification, it is possible to confirm that the data requested by the recipient is indeed stored in the multi-chain network without accessing the complete data, thereby improving the efficiency and security of data verification. By adopting the signature sharding technology, the verification results of the authorization node can be summarized and verified through the main chain smart contract to ensure the reliability and security of the verification results. Only when the number of valid signature shards collected reaches the preset threshold, the cross-chain access permission will be generated, which can effectively prevent single point failures and malicious attacks and improve the security and reliability of the system.

[0051] Preferably, step S33 includes the following steps:

[0052] Step S331: extracting request data from access request data according to access permission data to obtain a request data set;

[0053] Step S332: Generate a random seed according to a preset random number generator to obtain a random seed;

[0054] Step S333: Combine the requested data set and the random seed with the data to be signed to obtain the data to be signed;

[0055] Step S334: Use the private key of the main chain smart contract to digitally sign the signature data to obtain the challenge signature data;

[0056] Step S335: assemble the challenge signature data and the data to be signed into an access challenge to obtain the access challenge data.

[0057] The present invention can ensure that the recipient can only access the authorized data range by extracting the request data set according to the access permission data, prevent data leakage, and improve the security of data access. Using a preset random number generator to generate a random seed can increase the randomness and unpredictability of the access challenge, and effectively prevent replay attacks and other malicious behaviors. Combining the request data set and the random seed into the data to be signed can introduce randomness into the access challenge, so that each access challenge is unique, further improving security. Using the private key of the main chain smart contract to digitally sign the data can ensure the integrity and authenticity of the data to be signed, prevent the data from being tampered with, and also prove that the challenge information comes from a trusted main chain smart contract. Assembling the challenge signature data and the data to be signed into the access challenge data can pass all necessary information to the authorization node, which is convenient for it to verify and parse, and improve the efficiency and security of data access control.

[0058] Preferably, step S35 includes the following steps:

[0059] Step S351: performing data tag verification according to the access challenge parsing data to obtain data tag verification data;

[0060] Step S352: Identify the target blockchain according to the data tag verification data to obtain the target blockchain identifier;

[0061] Step S353: Perform a lightweight proof request based on the data tag verification data and the target blockchain identifier to obtain lightweight storage proof data;

[0062] Step S354: Perform local verification and certification on the lightweight storage certification data to obtain local verification and certification data.

[0063] The present invention can ensure that the data requested by the recipient to access is authentic and valid by verifying the data label, prevent it from obtaining unauthorized data access rights by using forged data labels, and improve the security of data access. By verifying the data identification target blockchain based on the data label, the blockchain storing the target data can be accurately found to prepare for subsequent lightweight proof requests. By sending a lightweight proof request, the authorized node can quickly verify whether the target data exists on the target blockchain without downloading the complete data, thereby improving the efficiency of data verification and reducing the network burden. Local verification of lightweight storage proof data can ensure the authenticity and validity of the proof information, prevent malicious nodes from providing false proofs, and improve the reliability of data verification.

[0064] Preferably, step S4 comprises the following steps:

[0065] Step S41: Transmit the cross-chain access permission data to the recipient, perform access permission parsing, and obtain access permission parsing data, wherein the access permission parsing data includes the target blockchain node and authorization data; initiate an extraction request to the target blockchain node according to the cross-chain access permission data, and obtain extraction request data;

[0066] Step S42: the target blockchain node performs access permission authentication on the authorization data according to the extraction request data to obtain cross-chain access permission data; and performs data slice positioning according to the cross-chain access permission data to obtain the data slice position;

[0067] Step S43: constructing a zero-knowledge proof that the node has a slice using zero-knowledge proof technology according to the data slice position, and obtaining zero-knowledge proof data;

[0068] Step S44: transmitting the zero-knowledge proof data to the receiving party, performing zero-knowledge proof authentication, and obtaining zero-knowledge proof authentication data; performing data slicing confirmation on the target blockchain node according to the zero-knowledge proof authentication data, and obtaining data slicing confirmation data;

[0069] Step S45: Transmit the data slice confirmation data to the target blockchain node, perform encrypted slice data transmission, and obtain encrypted slice data transmission data;

[0070] Step S46: The receiving party collects encrypted slices of the encrypted slice data transmission data to obtain an encrypted slice set; and sorts the encrypted slices of the encrypted slice set according to the labeled storage policy data to obtain an encrypted data fragment set.

[0071] The present invention can ensure that only the authorized receiver can request data from the target blockchain node by transmitting the cross-chain access permission data to the receiver and initiating an extraction request, thereby further improving the security of data access. The target blockchain node performs access permission authentication on the authorized data, which can reconfirm the receiver's access rights, prevent the cross-chain access permission data from being stolen or tampered with, and ensure that only legitimate users can access the data. By using zero-knowledge proof technology to build a proof that the node has a slice, it can prove to the receiver that the target blockchain node does have the data it requests without leaking the content of the data slice, which not only ensures data security, but also realizes the verification of data ownership. The receiver authenticates the zero-knowledge proof, which can confirm the data holding of the target blockchain node, and confirm the data slice after confirming that it is correct, so as to prepare for subsequent data transmission. The target blockchain node transmits the encrypted slice data according to the data slice confirmation information, which can ensure that the data is not stolen or tampered with during the transmission process, and ensure the confidentiality and integrity of the data. The receiver collects the encrypted slices and sorts them according to the labeled storage strategy data, which can prepare for subsequent data decryption and reorganization, and improve the efficiency of data recovery.

[0072] Preferably, step S5 comprises the following steps:

[0073] Step S51: The receiving party extracts slice metadata from the encrypted data segment set to obtain slice metadata; performs slice integrity verification on the encrypted data segment set according to the slice metadata to obtain slice integrity data;

[0074] Step S52: acquiring a decryption key for the slice metadata according to the slice integrity data to obtain a decryption key; decrypting the encrypted data segment set using the decryption key to obtain a plaintext data slice;

[0075] Step S53: reorganizing the plaintext data slices according to the slice metadata to obtain data slice reorganized data; generating a data stream for the data slice reorganized data to obtain a data stream;

[0076] Step S54: reconstructing the Merkle tree using the data stream according to the labeled storage strategy data to obtain a reconstructed Merkle tree; calculating the reconstructed Merkle tree root on the reconstructed Merkle tree to obtain reconstructed Merkle tree root data;

[0077] Step S55: Perform a Merkle tree root comparison on the reconstructed Merkle tree root data and the Merkle tree root data in the labeled storage strategy data to obtain Merkle tree root comparison data; output the original data according to the Merkle tree root comparison data to obtain the original data.

[0078] The present invention can ensure that the received data slices are not damaged or lost during the transmission process by extracting the slice metadata and performing integrity verification by the receiver, thereby ensuring the integrity of the data. By obtaining the decryption key and decrypting the data slice according to the slice integrity data, the original plaintext data can be restored, ensuring the confidentiality of the data while also preparing for subsequent data reorganization and verification. By reorganizing the plaintext data slices according to the slice metadata, the dispersedly stored data blocks can be spliced ​​together in the correct order to restore the structure and content of the original data. By reconstructing the Merkle tree using the data stream and calculating the root hash value of the tree, the integrity of the data can be verified again to ensure that the data has not been tampered with during the decryption and reorganization process. By comparing the reconstructed Merkle tree root data with the original Merkle tree root data, the integrity and authenticity of the data can be finally confirmed to ensure that the data obtained by the receiver is credible.

[0079] The present invention ensures the confidentiality and integrity of data through data slicing and encryption. At the same time, a label storage strategy is generated according to the multi-chain network topology and data characteristics, thereby realizing safe, reliable and efficient storage of data. Data slices are cross-chain stored according to the label storage strategy, and the integrity and traceability of the data are guaranteed through the cross-chain aggregate storage proof mechanism, thereby realizing multi-chain data collaborative management. Through the recipient identity authentication, access challenge, lightweight cross-chain verification and signature slicing technology, secure and controllable data access control is realized, ensuring that only authorized users can access the data. By using zero-knowledge proof technology, while protecting data privacy, the data holding status of the target blockchain node is verified, thereby realizing secure data extraction and transmission. Through mechanisms such as data integrity verification, data decryption, data reorganization and Merkel tree verification, it is ensured that the recipient can obtain the original data safely and completely, thereby ensuring the reliability and security of data transmission. Therefore, the present invention provides a data security transmission method based on blockchain. The scalability problem faced by the existing data security transmission method based on blockchain is solved. By distributing data slices and storing them in multiple blockchains, and using cross-chain technology to achieve interoperability and synchronization between blockchains, data transmission, storage, access control, and extraction can be processed in parallel on multiple chains, thereby effectively improving overall performance and scalability and avoiding the bottleneck limitations of a single blockchain. At the same time, multi-chain storage also improves data security and reliability. BRIEF DESCRIPTION OF THE DRAWINGS

[0080] Figure 1 A flowchart of a method for secure data transmission based on blockchain;

[0081] Figure 2 for Figure 1 Detailed implementation steps of step S3 in FIG.

[0082] Figure 3 for Figure 1 Detailed implementation steps of step S4 in FIG.

[0083] The purpose, features and advantages of the present invention will be further described with reference to the accompanying drawings in conjunction with the embodiments. DETAILED DESCRIPTION

[0084] The technical method of the present invention is described clearly and completely below in conjunction with the accompanying drawings. Obviously, the described embodiments are part of the embodiments of the present invention, not all of the embodiments. Based on the embodiments of the present invention, all other embodiments obtained by technicians in this field without creative work are within the scope of protection of the present invention.

[0085] In addition, the accompanying drawings are only schematic illustrations of the present invention and are not necessarily drawn to scale. The same reference numerals in the figures represent the same or similar parts, and their repeated description will be omitted. Some of the block diagrams shown in the accompanying drawings are functional entities and do not necessarily correspond to physically or logically independent entities. The functional entities can be implemented in software form, or implemented in one or more hardware modules or integrated circuits, or implemented in different networks and / or processor methods and / or microcontroller methods.

[0086] It should be understood that, although the terms "first", "second", etc. may be used herein to describe various units, these units should not be limited by these terms. These terms are used only to distinguish one unit from another unit. For example, without departing from the scope of the exemplary embodiments, the first unit may be referred to as the second unit, and similarly the second unit may be referred to as the first unit. The term "and / or" used herein includes any and all combinations of one or more of the listed associated items.

[0087] To achieve this, please refer to Figures 1 to 3 , a data security transmission method based on blockchain, comprising the following steps:

[0088] Step S1: Obtain the original data to be transmitted, slice and encrypt the original data to be transmitted, and obtain encrypted slice data; generate a labeled storage strategy according to the preset multi-chain network topology structure and the encrypted slice data, and obtain labeled storage strategy data;

[0089] Step S2: Determine the storage target chain of the encrypted slice data according to the labeled storage strategy data to obtain the target blockchain node data; construct a storage transaction for the encrypted slice data to obtain storage transaction data; perform cross-chain aggregate storage proof analysis according to the target blockchain node data and storage transaction data to obtain aggregate storage proof data;

[0090] Step S3: Obtain the recipient's identity data; perform access request initiation processing based on the recipient's identity data and the aggregated storage proof data to obtain access request data; generate access challenge based on the access request data to obtain access challenge data; perform lightweight cross-chain verification based on the access challenge data to obtain local verification proof data; perform cross-chain access permission analysis based on the local verification proof data and the main chain smart contract to obtain cross-chain access permission data;

[0091] Step S4: The cross-chain access permission data is transmitted to the receiving party to initiate an extraction request, and the extraction request data is obtained; the target blockchain node constructs a zero-knowledge proof that the node has a slice according to the extraction request data, and obtains zero-knowledge proof data; the zero-knowledge proof data is transmitted to the receiving party, and the data slice is confirmed to obtain data slice confirmation data; the encrypted data segment transmission processing is performed according to the data slice confirmation data to obtain an encrypted data segment set;

[0092] Step S5: The receiver decrypts the encrypted data slices of the encrypted data segment set to obtain plaintext data slices; reconstructs the Merkle root calculation based on the labeled storage strategy data and the plaintext data slices to obtain reconstructed Merkle root data; performs a Merkle root comparison on the reconstructed Merkle root data and the Merkle root data in the labeled storage strategy data and outputs the original data to obtain the original data.

[0093] In the embodiment of the present invention, reference Figure 1 The above is a schematic diagram of the steps of the blockchain-based data security transmission method of the present invention. In this example, the blockchain-based data security transmission method includes the following steps:

[0094] Step S1: Obtain the original data to be transmitted, slice and encrypt the original data to be transmitted, and obtain encrypted slice data; generate a labeled storage strategy according to the preset multi-chain network topology structure and the encrypted slice data, and obtain labeled storage strategy data;

[0095] Step S2: Determine the storage target chain of the encrypted slice data according to the labeled storage strategy data to obtain the target blockchain node data; construct a storage transaction for the encrypted slice data to obtain storage transaction data; perform cross-chain aggregate storage proof analysis according to the target blockchain node data and storage transaction data to obtain aggregate storage proof data;

[0096] Step S3: Obtain the recipient's identity data; perform access request initiation processing based on the recipient's identity data and the aggregated storage proof data to obtain access request data; generate access challenge based on the access request data to obtain access challenge data; perform lightweight cross-chain verification based on the access challenge data to obtain local verification proof data; perform cross-chain access permission analysis based on the local verification proof data and the main chain smart contract to obtain cross-chain access permission data;

[0097] Step S4: The cross-chain access permission data is transmitted to the receiving party to initiate an extraction request, and the extraction request data is obtained; the target blockchain node constructs a zero-knowledge proof that the node has a slice according to the extraction request data, and obtains zero-knowledge proof data; the zero-knowledge proof data is transmitted to the receiving party, and the data slice is confirmed to obtain data slice confirmation data; the encrypted data segment transmission processing is performed according to the data slice confirmation data to obtain an encrypted data segment set;

[0098] Step S5: The receiver decrypts the encrypted data slices of the encrypted data segment set to obtain plaintext data slices; reconstructs the Merkle root calculation based on the labeled storage strategy data and the plaintext data slices to obtain reconstructed Merkle root data; performs a Merkle root comparison on the reconstructed Merkle root data and the Merkle root data in the labeled storage strategy data and outputs the original data to obtain the original data.

[0099] In an embodiment of the present invention, the sender obtains the original data to be transmitted, slices and encrypts it, and generates encrypted slice data. At the same time, according to the preset multi-chain network topology and the characteristics of the encrypted slice data, the labeled storage strategy data is generated, which includes the data label of each slice, the storage target blockchain information, and the Merkle tree root hash value. According to the data label of each slice in the labeled storage strategy data and the predefined storage strategy, the storage target blockchain and the corresponding node information of the slice data are determined. Then, the storage transaction data containing the encrypted slice data, the target blockchain information and other necessary transaction information is constructed. Finally, the storage transaction data is sent to the target blockchain for storage, and the storage proofs of all associated blockchains are collected to generate aggregate storage proof data to prove that the data has been securely stored in the multi-chain network. The receiver provides its own identity information combined with the aggregate storage proof data to generate access request data to initiate an access request to the main chain smart contract. The main chain smart contract verifies the receiver's access rights and generates access challenge data. The authorized node parses the access challenge, performs lightweight cross-chain verification, confirms that the data exists in the multi-chain network, and generates local verification proof data. The main chain smart contract collects the signature slices from different authorized nodes, verifies them, and generates cross-chain access permission data when the preset conditions are met. The main chain smart contract sends the cross-chain access permission data to the receiver, and the receiver parses it and initiates an extraction request to the target blockchain node. The target blockchain node verifies the receiver's access rights and uses zero-knowledge proof technology to prove to the receiver that it owns the requested data slice without leaking the data content. After the receiver passes the verification, the target blockchain node transmits the encrypted data slice to the receiver. The receiver receives the encrypted data fragments, decrypts and splices them, and finally obtains a complete set of encrypted data fragments. Then, the receiver verifies the integrity of the data according to the slice metadata, and decrypts the encrypted data using the decryption key to obtain the plaintext data slice. Finally, the receiver reorganizes the plaintext data slice according to the slice metadata, and compares the reconstructed Merkle tree root data with the original Merkle tree root data in the labeled storage policy data to verify the data integrity and finally output the original data.

[0100] Preferably, step S1 comprises the following steps:

[0101] Step S11: obtaining the original data to be transmitted through the sender; slicing the original data to be transmitted to obtain a data slice set;

[0102] Step S12: Generate slice information metadata according to the data slice set to obtain slice information metadata;

[0103] Step S13: Binding the slice information metadata and the data slice set to obtain a slice metadata pair;

[0104] Step S14: Slice encrypt the slice metadata pair to obtain encrypted slice data;

[0105] Step S15: Generate slice storage strategy recommendations based on the preset multi-chain network topology and encrypted slice data to obtain slice storage strategy recommendation data; integrate labeled storage strategy data based on the slice storage strategy recommendation data to obtain labeled storage strategy data.

[0106] In an embodiment of the present invention, the sender first prepares the original data to be transmitted, such as a large file, a database record, or an encryption key. Then, the sender selects a suitable slicing algorithm and a slice size to divide the original data into multiple data slices to form a data slice set. For each slice in the data slice set, a slice information metadata containing its identity information, size, format, checksum, and other information is generated. These metadata can help identify, verify, and manage the slices in subsequent steps. The slice information metadata is bound to the corresponding data slice to form a slice metadata pair. The binding method can be to directly attach the metadata to the slice header, or to establish a mapping relationship to ensure that each data slice can be associated with the corresponding metadata. Each slice metadata pair is encrypted to ensure the confidentiality and integrity of the data slice during transmission and storage. The encryption algorithm can be symmetric encryption or asymmetric encryption, and the specific selection depends on the security requirements and performance requirements. The multi-chain network topology is pre-set, such as the performance, storage capacity, security level, and other information of each blockchain. Then, based on the encrypted slice data characteristics (such as size, importance, etc.) and the preset multi-chain network topology, a machine learning model or other algorithm is used to generate a slice storage strategy recommendation, such as which slices are stored on which blockchain. Finally, the slice storage strategy recommendations and encrypted slice data are integrated to generate labeled storage strategy data containing information such as data labels and Merkle tree root hash values.

[0107] Preferably, step S15 comprises the following steps:

[0108] Step S151: extracting slice features from the encrypted slice data to obtain a slice feature set;

[0109] Step S152: inputting the slice feature set into the pre-trained machine learning model, generating slice storage strategy recommendations according to the preset multi-chain network topology structure, and obtaining slice storage strategy recommendation data;

[0110] Step S153: Generate a data label according to the slice storage strategy suggestion data and the encrypted slice data to obtain a data label;

[0111] Step S154: construct a Merkle tree according to the data tag and calculate the root hash value of the tree to obtain the Merkle tree root hash value;

[0112] Step S155: Integrate the Merkle tree root hash value, data label, and encrypted slice data into labeled storage strategy data to obtain labeled storage strategy data.

[0113] In an embodiment of the present invention, the encrypted slice data is analyzed, and information that can reflect its characteristics, such as slice size, encryption algorithm, timestamp, importance level, etc., is extracted to form a slice feature set. The slice feature set is input into a pre-trained machine learning model. The model has learned the optimal storage strategy for slice data with different characteristics in a multi-chain network. The model outputs slice storage strategy recommendation data based on the input features and the preset multi-chain network topology (such as the performance, storage capacity, security level, etc. of each blockchain), that is, it is recommended that each slice be stored on which blockchain. According to the slice storage strategy recommendation data, a data label is generated for each encrypted slice data. The data label contains the identification information and other necessary information of the blockchain to which the slice belongs, which is used to quickly locate and identify the slice data in subsequent steps. A Merkle tree is constructed using all data labels, and the root hash value of the Merkle tree is calculated. The Merkle tree can ensure the integrity and immutability of the data label, and the root hash value is used for subsequent data verification. The Merkle tree root hash value, all data labels, and the encrypted slice data are integrated to form the final labeled storage strategy data. This data contains the storage location information of all slices, integrity verification information and the encrypted data itself, and will be used for subsequent cross-chain storage and data extraction.

[0114] Preferably, step S2 comprises the following steps:

[0115] Step S21: Perform labeling strategy parsing on the labeling storage strategy data through the blockchain node to obtain Merkle tree root data;

[0116] Step S22: performing encrypted slice verification on the encrypted slice data according to the Merkle tree root data to obtain encrypted slice verification data;

[0117] Step S23: Determine the storage target chain of the encrypted slice data according to the encrypted slice verification data to obtain the target blockchain node data; construct a storage transaction for the encrypted slice data to obtain storage transaction data;

[0118] Step S24: Perform storage proof cross-chain analysis based on the target blockchain node data and the storage transaction data to obtain storage proof cross-chain data;

[0119] Step S25: Generate aggregated storage proof based on the storage proof cross-chain data to obtain aggregated storage proof data.

[0120] In an embodiment of the present invention, after receiving the labeled storage policy data transmitted by the sender, the blockchain node parses the data label and the Merkle tree structure therein, and finally obtains the Merkle tree root data. The blockchain node uses the Merkle tree root data obtained by parsing to verify the encrypted slice data to ensure that the data has not been tampered with during the transmission process. The verification process can use the characteristics of the Merkle tree to efficiently compare the data label and the root hash value. According to the result of the encrypted slice verification and the storage strategy pre-defined in the labeled storage policy data, the target blockchain corresponding to each encrypted slice data is determined, and the target blockchain node data, such as the node address, communication protocol, etc., is obtained. Then, the storage transaction data is constructed, including the encrypted slice data to be stored, the target blockchain information and other necessary transaction information. The storage transaction data is sent to the corresponding target blockchain node for storage operation. The target blockchain node packs the transaction into a block, and cross-chain anchors the storage proof to other related blockchains to form storage proof cross-chain data, which is used to prove that the data has been securely stored in the multi-chain network. The storage proof cross-chain data from all related blockchains is collected and aggregated to generate the final aggregated storage proof data. This data summarizes the storage proof information of all slices on the multi-chain network and is an important proof of data integrity and security.

[0121] Preferably, step S24 comprises the following steps:

[0122] Step S241: performing inter-node consensus confirmation on the stored transaction data according to the target blockchain node data to obtain inter-node consensus data;

[0123] Step S242: The stored transaction data is packaged into blocks according to the consensus data between nodes and added to the target blockchain in the target blockchain node data to obtain encrypted slice storage data;

[0124] Step S243: Generate storage proof for the encrypted slice storage data according to the target blockchain node data to obtain storage proof data;

[0125] Step S244: performing storage proof anchoring processing on the storage proof data to obtain storage proof anchoring data;

[0126] Step S245: Use the preset cross-chain bridge to perform storage proof cross-chain collection on the target blockchain node data according to the storage proof anchor data to obtain storage proof cross-chain data.

[0127] In the embodiment of the present invention, after receiving the storage transaction data, the target blockchain node will conduct consensus confirmation between the nodes to ensure that all nodes agree on the legitimacy and validity of the transaction. The consensus mechanism can be PoW, PoS or other consensus algorithms, and finally form consensus data between nodes. According to the consensus data between nodes, the target blockchain node packages the storage transaction data into a new block and adds it to the target blockchain. At this point, the encrypted slice data is officially stored on the target blockchain to form encrypted slice storage data. The target blockchain node generates storage proof data based on the encrypted slice storage data, proving that the data has been written into the blockchain. The storage proof can be a Merkle tree proof, a simple payment verification (SPV) proof, etc., which is used to verify the integrity and authenticity of the data later. The storage proof data is anchored and written into the target blockchain or other related blockchains to form storage proof anchor data. Using the preset cross-chain bridge, according to the storage proof anchor data, the storage proof data is collected from the target blockchain and other related blockchains, and finally aggregated to form storage proof cross-chain data. The cross-chain bridge can realize data intercommunication and interaction between different blockchains, ensuring that the storage proofs of all related blockchains can be collected.

[0128] Preferably, step S3 comprises the following steps:

[0129] Step S31: Obtain the recipient's identity data; perform access request initiation processing based on the recipient's identity data and the aggregated storage certification data to obtain access request data;

[0130] Step S32: The access request data is transmitted to the main chain smart contract of the blockchain, and the access permission is verified to obtain the access permission data;

[0131] Step S33: Generate access challenge according to access permission data and access request data to obtain access challenge data;

[0132] Step S34: transmitting the access challenge data to a preset authorization node, performing access challenge analysis, and obtaining access challenge analysis data;

[0133] Step S35: Perform lightweight cross-chain verification based on the access challenge parsing data to obtain local verification proof data;

[0134] Step S36: Generate a signature copy according to the local verification proof data to obtain signature copy data; collect signature copies of the signature copy data and perform copy verification on the signature copy data through the main chain smart contract to obtain copy verification data;

[0135] Step S37: When the number of signature copies in the copy verification data is greater than or equal to the preset signature copy threshold, a cross-chain access permission is generated to obtain cross-chain access permission data.

[0136] As an example of the present invention, refer to Figure 2 As shown, in this example, step S3 includes:

[0137] Step S31: Obtain the recipient's identity data; perform access request initiation processing based on the recipient's identity data and the aggregated storage certification data to obtain access request data;

[0138] In an embodiment of the present invention, the recipient submits its own identity information, label information of the required data, and the aggregate storage certificate to the smart contract on the main chain, initiates an access request, and generates access request data containing the recipient's identity information, the requested access data range, etc.

[0139] Step S32: The access request data is transmitted to the main chain smart contract of the blockchain, and the access permission is verified to obtain the access permission data;

[0140] In an embodiment of the present invention, the access request data is sent to the main chain smart contract of the blockchain. The smart contract verifies whether the recipient has the right to access the requested data according to a pre-set access control policy, such as identity-based access control (IBAC) or attribute-based access control (ABAC), and generates access permission data.

[0141] Step S33: Generate access challenge according to access permission data and access request data to obtain access challenge data;

[0142] In the embodiment of the present invention, the main chain smart contract generates access challenge data based on the access permission data and the access request data. The access challenge data can be a task that the recipient needs to complete or a question that needs to be answered, which is used to verify the identity and authority of the recipient.

[0143] Step S34: transmitting the access challenge data to a preset authorization node, performing access challenge analysis, and obtaining access challenge analysis data;

[0144] In an embodiment of the present invention, the access challenge data is sent to a preset authorization node. The authorization node can be a node specified by the main chain smart contract or another trusted third party. The authorization node is responsible for parsing the access challenge data, such as verifying the correctness of the task completed by the recipient or the answer to the question.

[0145] Step S35: Perform lightweight cross-chain verification based on the access challenge parsing data to obtain local verification proof data;

[0146] In an embodiment of the present invention, the authorized node parses the data according to the access challenge, and performs lightweight cross-chain verification without accessing the complete data, such as verifying the data label, Merkle tree path and other information, confirming that the data requested by the recipient is indeed stored in the multi-chain network, and generating local verification proof data.

[0147] Step S36: Generate a signature copy according to the local verification proof data to obtain signature copy data; collect signature copies of the signature copy data and perform copy verification on the signature copy data through the main chain smart contract to obtain copy verification data;

[0148] In the embodiment of the present invention, the authorization node generates the signature copy data according to the local verification proof data and sends it back to the main chain smart contract. The main chain smart contract is responsible for collecting the signature copies from different authorization nodes, and performing copy verification to ensure the authenticity and validity of the signature copies, and finally generates the copy verification data.

[0149] Step S37: When the number of signature copies in the copy verification data is greater than or equal to the preset signature copy threshold, a cross-chain access permission is generated to obtain cross-chain access permission data;

[0150] In the embodiment of the present invention, the main chain smart contract determines whether the number of valid signature copies collected reaches a preset threshold based on the copy verification data. If the threshold is reached, it is considered that the recipient has passed the verification, and cross-chain access permission data is generated to allow the recipient to access the requested data.

[0151] Preferably, step S33 includes the following steps:

[0152] Step S331: extracting request data from access request data according to access permission data to obtain a request data set;

[0153] Step S332: Generate a random seed according to a preset random number generator to obtain a random seed;

[0154] Step S333: Combine the requested data set and the random seed with the data to be signed to obtain the data to be signed;

[0155] Step S334: Use the private key of the main chain smart contract to digitally sign the signature data to obtain the challenge signature data;

[0156] Step S335: assemble the challenge signature data and the data to be signed into an access challenge to obtain the access challenge data.

[0157] In an embodiment of the present invention, the main chain smart contract extracts the specific data range and related information that the recipient is allowed to access from the access request data according to the access permission data to form a request data set. The main chain smart contract calls a preset random number generator to generate a random seed. The request data set and the random seed are combined to form the data to be signed. The main chain smart contract uses its own private key to digitally sign the data to be signed and generates challenge signature data. The challenge signature data and the data to be signed are assembled to form the final access challenge data. The access challenge data will be sent to the authorization node for verifying the identity and authority of the recipient.

[0158] Preferably, step S35 includes the following steps:

[0159] Step S351: performing data tag verification according to the access challenge parsing data to obtain data tag verification data;

[0160] Step S352: Identify the target blockchain according to the data tag verification data to obtain the target blockchain identifier;

[0161] Step S353: Perform a lightweight proof request based on the data tag verification data and the target blockchain identifier to obtain lightweight storage proof data;

[0162] Step S354: Perform local verification and certification on the lightweight storage certification data to obtain local verification and certification data.

[0163] In an embodiment of the present invention, the authorization node parses the data according to the access challenge, obtains the data tag requested by the recipient, and compares and verifies it with the data tag stored in the labeled storage policy data to ensure that the data tag requested by the recipient is true and valid, and finally generates data tag verification data. The authorization node verifies the blockchain identification information contained in the data tag, identifies which target blockchain the data requested by the recipient is stored on, and obtains the target blockchain identification. The authorization node verifies the data and the target blockchain identification according to the data tag, and initiates a lightweight proof request to the target blockchain, such as requesting to provide a Merkle tree path proof or SPV proof, etc., to verify whether the data requested by the recipient actually exists on the target blockchain, and finally obtains lightweight storage proof data. The authorization node verifies the lightweight storage proof data locally, such as verifying the correctness of the Merkle tree path or the validity of the SPV proof, to ensure that the data requested by the recipient is indeed stored on the target blockchain, and finally generates local verification proof data.

[0164] Preferably, step S4 comprises the following steps:

[0165] Step S41: Transmit the cross-chain access permission data to the recipient, perform access permission parsing, and obtain access permission parsing data, wherein the access permission parsing data includes the target blockchain node and authorization data; initiate an extraction request to the target blockchain node according to the cross-chain access permission data, and obtain extraction request data;

[0166] Step S42: the target blockchain node performs access permission authentication on the authorization data according to the extraction request data to obtain cross-chain access permission data; and performs data slice positioning according to the cross-chain access permission data to obtain the data slice position;

[0167] Step S43: constructing a zero-knowledge proof that the node has a slice using zero-knowledge proof technology according to the data slice position, and obtaining zero-knowledge proof data;

[0168] Step S44: transmitting the zero-knowledge proof data to the receiving party, performing zero-knowledge proof authentication, and obtaining zero-knowledge proof authentication data; performing data slicing confirmation on the target blockchain node according to the zero-knowledge proof authentication data, and obtaining data slicing confirmation data;

[0169] Step S45: Transmit the data slice confirmation data to the target blockchain node, perform encrypted slice data transmission, and obtain encrypted slice data transmission data;

[0170] Step S46: The receiving party collects encrypted slices of the encrypted slice data transmission data to obtain an encrypted slice set; and sorts the encrypted slices of the encrypted slice set according to the labeled storage policy data to obtain an encrypted data fragment set.

[0171] As an example of the present invention, refer to Figure 3 As shown, in this example, step S4 includes:

[0172] Step S41: Transmit the cross-chain access permission data to the recipient, perform access permission parsing, and obtain access permission parsing data, wherein the access permission parsing data includes the target blockchain node and authorization data; initiate an extraction request to the target blockchain node according to the cross-chain access permission data, and obtain extraction request data;

[0173] In the embodiment of the present invention, the main chain smart contract sends the generated cross-chain access permission data to the recipient. The recipient parses the data to obtain information such as the target blockchain node address and authorization data. Then, the recipient initiates an extraction request to the target blockchain node based on the cross-chain access permission data, requesting to obtain the data slice that is authorized to access.

[0174] Step S42: the target blockchain node performs access permission authentication on the authorization data according to the extraction request data to obtain cross-chain access permission data; and performs data slice positioning according to the cross-chain access permission data to obtain the data slice position;

[0175] In the embodiment of the present invention, after receiving the extraction request, the target blockchain node first uses the authorization data to authenticate the access permission of the recipient to ensure that it has access rights. After the authentication is passed, the node locates the corresponding data slice location information in the local storage according to the data range specified in the access request.

[0176] Step S43: constructing a zero-knowledge proof that the node has a slice using zero-knowledge proof technology according to the data slice position, and obtaining zero-knowledge proof data;

[0177] In an embodiment of the present invention, the target blockchain node uses zero-knowledge proof technology to construct a proof to prove to the recipient that it owns the requested data slice without leaking any information about the content of the data slice.

[0178] Step S44: transmitting the zero-knowledge proof data to the receiving party, performing zero-knowledge proof authentication, and obtaining zero-knowledge proof authentication data; performing data slicing confirmation on the target blockchain node according to the zero-knowledge proof authentication data, and obtaining data slicing confirmation data;

[0179] In an embodiment of the present invention, the target blockchain node sends the generated zero-knowledge proof data to the recipient. The recipient uses a preset verification algorithm to authenticate the zero-knowledge proof, confirms that the target blockchain node does have the requested data slice, and generates zero-knowledge proof authentication data.

[0180] Step S45: Transmit the data slice confirmation data to the target blockchain node, perform encrypted slice data transmission, and obtain encrypted slice data transmission data;

[0181] In the embodiment of the present invention, the recipient sends the zero-knowledge proof authentication data back to the target blockchain node to confirm that the data slice has passed the verification. The target blockchain node transmits the encrypted data slice to the recipient based on the data slice confirmation information.

[0182] Step S46: The receiving party collects encrypted slices of the encrypted slice data transmission data to obtain an encrypted slice set; and sorts the encrypted slices of the encrypted slice set according to the labeled storage policy data to obtain an encrypted data segment set;

[0183] In an embodiment of the present invention, a receiver receives the encrypted slice data, decrypts and concatenates the data, and finally obtains a complete set of encrypted data fragments.

[0184] Preferably, step S5 comprises the following steps:

[0185] Step S51: The receiving party extracts slice metadata from the encrypted data segment set to obtain slice metadata; performs slice integrity verification on the encrypted data segment set according to the slice metadata to obtain slice integrity data;

[0186] Step S52: acquiring a decryption key for the slice metadata according to the slice integrity data to obtain a decryption key; decrypting the encrypted data segment set using the decryption key to obtain a plaintext data slice;

[0187] Step S53: reorganizing the plaintext data slices according to the slice metadata to obtain data slice reorganized data; generating a data stream for the data slice reorganized data to obtain a data stream;

[0188] Step S54: reconstructing the Merkle tree using the data stream according to the labeled storage strategy data to obtain a reconstructed Merkle tree; calculating the reconstructed Merkle tree root on the reconstructed Merkle tree to obtain reconstructed Merkle tree root data;

[0189] Step S55: Perform a Merkle tree root comparison on the reconstructed Merkle tree root data and the Merkle tree root data in the labeled storage strategy data to obtain Merkle tree root comparison data; output the original data according to the Merkle tree root comparison data to obtain the original data.

[0190] In an embodiment of the present invention, the receiver extracts slice metadata, such as slice size, sequence, checksum, and other information, from the encrypted data segment set. Then, based on the extracted metadata information, the integrity of the received encrypted data segment set is verified to ensure that the data is not damaged or lost during transmission. Based on the slice integrity verification result, the receiver obtains a decryption key from the slice metadata. Then, the encrypted data segment set is decrypted using the decryption key to finally obtain the plaintext data slice. The receiver reorganizes the plaintext data slices according to the slice sequence information recorded in the slice metadata, restores the original sequence of the data, and forms data slice reorganization data. Then, the reorganized data slices are connected in sequence to form a complete data stream. The receiver reconstructs the Merkle tree using the data stream according to the Merkle tree structure and data tag information recorded in the labeled storage strategy data. Then, the root hash value of the reconstructed Merkle tree is calculated to obtain the reconstructed Merkle tree root data. The receiver compares the reconstructed Merkle tree root data with the original Merkle tree root data stored in the labeled storage strategy data. If the comparison results are consistent, it means that the data is complete and has not been tampered with. Finally, the data stream is output and restored to the original data.

[0191] Therefore, the embodiments should be regarded as illustrative and non-restrictive from all points, and the scope of the present invention is limited by the appended claims rather than the above description, and it is therefore intended that all changes falling within the meaning and range of equivalent elements of the application documents are included in the present invention.

[0192] The above description is only a specific embodiment of the present invention, so that those skilled in the art can understand or implement the present invention. Various modifications to these embodiments will be apparent to those skilled in the art, and the general principles defined herein may be implemented in other embodiments without departing from the spirit or scope of the present invention. Therefore, the present invention will not be limited to the embodiments shown herein, but should conform to the widest scope consistent with the principles and novel features invented herein.

Claims

1. A data security transmission method based on blockchain, characterized in that: The following steps are involved: Step S1: Obtaining the original data to be transmitted, slicing and encrypting the original data to be transmitted, and obtaining encrypted slice data; Generate a labeled storage strategy based on the preset multi-chain network topology and encrypted slice data to obtain labeled storage strategy data; Step S2: Determine the storage target chain of the encrypted slice data according to the labeled storage strategy data to obtain the target blockchain node data; construct a storage transaction for the encrypted slice data to obtain storage transaction data; perform cross-chain aggregate storage proof analysis according to the target blockchain node data and storage transaction data to obtain aggregate storage proof data; Step S3: Obtain the recipient's identity data; Initiate access request processing based on the recipient's identity data and aggregated storage proof data to obtain access request data; generate access challenge based on the access request data to obtain access challenge data; perform lightweight cross-chain verification based on the access challenge data to obtain local verification proof data; perform cross-chain access permission analysis based on the local verification proof data and the main chain smart contract to obtain cross-chain access permission data; Step S4: Transmit the cross-chain access permission data to the recipient to initiate an extraction request and obtain the extraction request data; The target blockchain node constructs a zero-knowledge proof of the node having the slice according to the extraction request data, and obtains the zero-knowledge proof data; The zero-knowledge proof data is transmitted to the receiving party, and the data slice is confirmed to obtain the data slice confirmation data; the encrypted data fragment transmission processing is performed according to the data slice confirmation data to obtain the encrypted data fragment set; Step S5: The receiver decrypts the encrypted data slices of the encrypted data segment set to obtain plaintext data slices; reconstructs the Merkle root calculation based on the labeled storage strategy data and the plaintext data slices to obtain reconstructed Merkle root data; performs a Merkle root comparison on the reconstructed Merkle root data and the Merkle root data in the labeled storage strategy data and outputs the original data to obtain the original data.

2. The data security transmission method based on blockchain according to claim 1 is characterized in that: Step S1 includes the following steps: Step S11: obtaining the original data to be transmitted through the sender; slicing the original data to be transmitted to obtain a data slice set; Step S12: Generate slice information metadata according to the data slice set to obtain slice information metadata; Step S13: Binding the slice information metadata and the data slice set to obtain a slice metadata pair; Step S14: Slice the slice metadata pair to obtain encrypted slice data; Step S15: Generate slice storage strategy recommendations based on the preset multi-chain network topology and encrypted slice data to obtain slice storage strategy recommendation data; integrate labeled storage strategy data based on the slice storage strategy recommendation data to obtain labeled storage strategy data.

3. The data security transmission method based on blockchain according to claim 2 is characterized in that: Step S15 includes the following steps: Step S151: extracting slice features from the encrypted slice data to obtain a slice feature set; Step S152: inputting the slice feature set into the pre-trained machine learning model, generating slice storage strategy recommendations according to the preset multi-chain network topology structure, and obtaining slice storage strategy recommendation data; Step S153: Generate a data label according to the slice storage strategy suggestion data and the encrypted slice data to obtain a data label; Step S154: construct a Merkle tree according to the data tag and calculate the root hash value of the tree to obtain the Merkle tree root hash value; Step S155: Integrate the Merkle tree root hash value, data label, and encrypted slice data into labeled storage strategy data to obtain labeled storage strategy data.

4. The data security transmission method based on blockchain according to claim 1 is characterized in that: Step S2 includes the following steps: Step S21: Perform labeling strategy parsing on the labeling storage strategy data through the blockchain node to obtain Merkle tree root data; Step S22: performing encrypted slice verification on the encrypted slice data according to the Merkle tree root data to obtain encrypted slice verification data; Step S23: Determine the storage target chain of the encrypted slice data according to the encrypted slice verification data to obtain the target blockchain node data; construct a storage transaction for the encrypted slice data to obtain storage transaction data; Step S24: Perform storage proof cross-chain analysis based on the target blockchain node data and the storage transaction data to obtain storage proof cross-chain data; Step S25: Generate aggregated storage proof based on the storage proof cross-chain data to obtain aggregated storage proof data.

5. The method for secure data transmission based on blockchain according to claim 4 is characterized in that: Step S24 includes the following steps: Step S241: performing inter-node consensus confirmation on the stored transaction data according to the target blockchain node data to obtain inter-node consensus data; Step S242: The stored transaction data is packaged into blocks according to the consensus data between nodes and added to the target blockchain in the target blockchain node data to obtain encrypted slice storage data; Step S243: Generate storage proof for the encrypted slice storage data according to the target blockchain node data to obtain storage proof data; Step S244: performing storage proof anchoring processing on the storage proof data to obtain storage proof anchoring data; Step S245: Use the preset cross-chain bridge to perform storage proof cross-chain collection on the target blockchain node data according to the storage proof anchor data to obtain storage proof cross-chain data.

6. The data security transmission method based on blockchain according to claim 1 is characterized in that: Step S3 includes the following steps: Step S31: Obtain the recipient's identity data; perform access request initiation processing based on the recipient's identity data and the aggregated storage certification data to obtain access request data; Step S32: The access request data is transmitted to the main chain smart contract of the blockchain, and the access permission is verified to obtain the access permission data; Step S33: Generate access challenge according to access permission data and access request data to obtain access challenge data; Step S34: transmitting the access challenge data to a preset authorization node, performing access challenge analysis, and obtaining access challenge analysis data; Step S35: Perform lightweight cross-chain verification based on the access challenge parsing data to obtain local verification proof data; Step S36: Generate a signature copy according to the local verification proof data to obtain signature copy data; collect signature copies of the signature copy data and perform copy verification on the signature copy data through the main chain smart contract to obtain copy verification data; Step S37: When the number of signature copies in the copy verification data is greater than or equal to the preset signature copy threshold, a cross-chain access permission is generated to obtain cross-chain access permission data.

7. The method for secure data transmission based on blockchain according to claim 6 is characterized in that: Step S33 includes the following steps: Step S331: extracting request data from access request data according to access permission data to obtain a request data set; Step S332: Generate a random seed according to a preset random number generator to obtain a random seed; Step S333: Combine the requested data set and the random seed with the data to be signed to obtain the data to be signed; Step S334: Use the private key of the main chain smart contract to digitally sign the signature data to obtain the challenge signature data; Step S335: assemble the challenge signature data and the data to be signed into an access challenge to obtain the access challenge data.

8. The method for secure data transmission based on blockchain according to claim 6 is characterized in that: Step S35 includes the following steps: Step S351: performing data tag verification according to the access challenge parsing data to obtain data tag verification data; Step S352: Identify the target blockchain according to the data tag verification data to obtain the target blockchain identifier; Step S353: Perform a lightweight proof request based on the data tag verification data and the target blockchain identifier to obtain lightweight storage proof data; Step S354: Perform local verification and certification on the lightweight storage certification data to obtain local verification and certification data.

9. The method for secure data transmission based on blockchain according to claim 1, characterized in that: Step S4 includes the following steps: Step S41: Transmit the cross-chain access permission data to the recipient, perform access permission parsing, and obtain access permission parsing data, wherein the access permission parsing data includes the target blockchain node and authorization data; initiate an extraction request to the target blockchain node according to the cross-chain access permission data, and obtain extraction request data; Step S42: the target blockchain node performs access permission authentication on the authorization data according to the extraction request data to obtain cross-chain access permission data; and performs data slice positioning according to the cross-chain access permission data to obtain the data slice position; Step S43: constructing a zero-knowledge proof that the node has a slice using zero-knowledge proof technology according to the data slice position, and obtaining zero-knowledge proof data; Step S44: transmitting the zero-knowledge proof data to the receiving party, performing zero-knowledge proof authentication, and obtaining zero-knowledge proof authentication data; performing data slicing confirmation on the target blockchain node according to the zero-knowledge proof authentication data, and obtaining data slicing confirmation data; Step S45: Transmit the data slice confirmation data to the target blockchain node, perform encrypted slice data transmission, and obtain encrypted slice data transmission data; Step S46: The receiving party collects encrypted slices of the encrypted slice data transmission data to obtain an encrypted slice set; and sorts the encrypted slices of the encrypted slice set according to the labeled storage policy data to obtain an encrypted data fragment set.

10. The method for secure data transmission based on blockchain according to claim 1, characterized in that: Step S5 includes the following steps: Step S51: The receiving party extracts slice metadata from the encrypted data segment set to obtain slice metadata; performs slice integrity verification on the encrypted data segment set according to the slice metadata to obtain slice integrity data; Step S52: acquiring a decryption key for the slice metadata according to the slice integrity data to obtain a decryption key; decrypting the encrypted data segment set using the decryption key to obtain a plaintext data slice; Step S53: reorganizing the plaintext data slices according to the slice metadata to obtain data slice reorganized data; generating a data stream for the data slice reorganized data to obtain a data stream; Step S54: reconstructing the Merkle tree using the data stream according to the labeled storage strategy data to obtain a reconstructed Merkle tree; calculating the reconstructed Merkle tree root on the reconstructed Merkle tree to obtain reconstructed Merkle tree root data; Step S55: Perform a Merkle tree root comparison on the reconstructed Merkle tree root data and the Merkle tree root data in the labeled storage strategy data to obtain Merkle tree root comparison data; output the original data according to the Merkle tree root comparison data to obtain the original data.

Images