Multi-Level Blockchain Protocol for Secondary Data Chain Embedding
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Blockchain systems using a UTXO-based transaction model face challenges in managing secondary data chains, particularly when a secondary blockchain becomes unviable or when private data integrity proofs are required, as they lack efficient mechanisms for embedding and securing data within a core blockchain.
Innovation Solution
A multi-level blockchain protocol is implemented, where a core blockchain acts as a carrier for a secondary data chain, utilizing consensus-based locking mechanisms to ensure data integrity and immutability, allowing ML block producers to generate and record ML blocks that include data blocks from the secondary chain as core blockchain transactions.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If a secondary blockchain is used to store data, then data storage capacity and flexibility are improved, but system reliability deteriorates when the secondary blockchain becomes unviable
Solution Approach 1:
The patent embeds the secondary data chain within the core blockchain structure, where secondary data blocks are nested as transactions in the core chain. This allows the secondary chain to leverage the core blockchain's reliability while maintaining data storage flexibility. The nested structure ensures that even if the secondary chain becomes unviable, the data remains secured by the core blockchain.
Solution Approach 2:
The patent implements consensus-based locking mechanisms in advance, where data in the secondary chain is locked through consensus procedures before being embedded in the core blockchain. This preliminary locking action ensures data integrity and immutability are established beforehand, preventing future reliability issues even if the secondary chain becomes unviable.
2Reliability
If data is embedded in the core blockchain, then data integrity and immutability are improved, but device complexity increases
Solution Approach 1:
The patent segments the blockchain system into a core blockchain layer and a secondary data chain layer. The core blockchain handles consensus and security, while the secondary chain manages data storage and retrieval. This segmentation allows data integrity to be ensured through the core chain's consensus mechanism without requiring the entire system to handle all data processing, thus managing complexity through functional separation.
Solution Approach 2:
The core blockchain transactions are designed to serve multiple functions: they maintain the core chain's ledger while simultaneously carrying secondary data chain information. This multi-functionality reduces overall system complexity by using a single infrastructure (the core blockchain) to achieve both security/integrity and data storage goals, rather than requiring separate systems for each function.
3Reliability
If consensus-based locking mechanisms are used, then data security is improved, but processing time increases
Solution Approach 1:
The patent applies consensus-based locking mechanisms selectively rather than universally. Consensus procedures are applied to lock data when it is embedded in the core blockchain, providing security where needed. However, once locked, subsequent operations can proceed without repeating full consensus procedures, reducing processing time for routine operations while maintaining security for critical data embedding actions.
Data Source
AI summary
A computer-implemented method of using a multi-level, ML, blockchain protocol to reach consensus on a data chain using a core blockchain, wherein the method comprises: obtaining a target data block associated with the data chain; generating a target ML block of the ML blockchain, wherein the target ML block is a respective core blockchain transaction and comprises a) the target data block, and b) a target chain output, wherein the target chain output is configured to be spent by a respective chain input of a subsequent ML block and comprises a locking script configured to implement a respective consensus-based locking mechanism, wherein the respective consensus-based locking mechanism of each respective ML block is a function of the respective data block of that respective ML block, and c) a target chain input that references the respective chain output of a previous ML block.