Multi-Level Blockchain Embedding for Reliable Secondary Data Chains
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing blockchain systems face challenges in efficiently embedding and securing secondary data chains, particularly when the secondary blockchain or its network becomes unviable, or when data integrity is required for non-blockchain data structures.
Innovation Solution
A multi-level data chain protocol is implemented, where a secondary data chain is embedded as a higher-level chain on a core blockchain, using carrier pairs signed with signatures, and recorded as core blockchain transactions to leverage the immutability and security of the core blockchain.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If a secondary blockchain is used to store data, then data structure flexibility is improved, but system reliability deteriorates when the secondary blockchain becomes unviable
Solution Approach 1:
The patent embeds a secondary blockchain structure within the core blockchain by nesting secondary block data inside core block transactions. Each core block contains transactions that carry secondary block headers and data, creating a nested hierarchy where the secondary blockchain is contained within the core blockchain. This allows the secondary blockchain to maintain its structural flexibility while relying on the core blockchain's reliability for persistent storage and verification.
Solution Approach 2:
The core blockchain acts as an intermediary carrier for the secondary blockchain data. Instead of the secondary blockchain standing alone, its data is transmitted and stored through the core blockchain's transaction mechanism. This intermediary relationship allows the secondary blockchain to benefit from the core blockchain's reliability while maintaining its own data structure characteristics.
2Reliability
If data is stored directly in the core blockchain, then data security is improved, but device complexity increases due to the need for multi-level protocol management
Solution Approach 1:
The patent segments the blockchain system into two functional layers: the core blockchain layer for security and verification, and the secondary blockchain layer for data organization and application logic. This segmentation allows each layer to specialize in its strengths while reducing overall complexity through clear separation of concerns. The core blockchain handles security-critical functions, while the secondary blockchain manages data structure complexity.
3Reliability
If a multi-level data chain protocol is implemented, then data integrity is improved, but manufacturing precision requirements increase for embedding carrier pairs
Solution Approach 1:
The patent uses homogeneous data structures for carrier pairs, where each carrier pair follows the same format with standardized fields for secondary block headers, data, and verification information. This homogeneity simplifies the embedding process by providing a consistent template that reduces precision requirements. The standardized structure allows for systematic processing and verification without requiring complex custom handling for each data type.
Data Source
AI summary
A computer-implemented method of using a multi-level (ML) data chain protocol to embed a data chain on a core blockchain, comprising: obtaining one or more ML transactions, wherein each ML transaction comprises one or more carrier pairs, each carrier pair comprising an input and an output, wherein each output comprises data associated with the data chain, and wherein each input comprises a signature that signs the carrier pair; generating a first ML block of the ML data chain, wherein the first ML block is a core blockchain transaction and comprises the respective carrier pairs of the obtained one or more ML transactions, wherein for each carrier pair, a respective position index of the respective input corresponds to a respective position index of the respective output, and b) a first chain output, wherein the first chain output is for being spent by a respective chain input of a subsequent ML block.


