Nested Blockchain System Data Conversion and Consistency
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Large distributed systems face errors when storing data without conversion, particularly in blockchain systems where different types of data values can lead to inconsistencies and errors if not properly managed.
Innovation Solution
A nested blockchain system is implemented, where nodes generate a master cryptographically verifiable ledger with sub-ledgers, allowing for event verification and data conversion, and smart contracts are used to manage transactions and errors across multiple domains, ensuring data consistency and accuracy.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Ease of manufacture
If data is stored without conversion in blockchain systems, then storage simplicity is improved, but data consistency and accuracy deteriorate
Solution Approach 1:
The patent applies parameter changes by converting data values between different types (e.g., string to integer, or vice versa) based on the specific requirements of each blockchain domain. This conversion process transforms the data parameters to match the expected format, ensuring both storage efficiency and data consistency without requiring complete redesign of the storage structure.
Solution Approach 2:
The patent introduces an intermediary data conversion layer between data storage and verification processes. This intermediary component automatically converts data values to appropriate types before storage and performs reverse conversion during verification, acting as a mediator that maintains data consistency while preserving storage simplicity.
2Reliability
If a nested blockchain system with multiple ledgers is implemented, then data consistency is improved, but system complexity increases
Solution Approach 1:
The patent implements a nested blockchain structure where sub-ledgers are contained within a master ledger, creating a hierarchical organization of data. Each sub-ledger handles specific domain data with appropriate type conversions, while the master ledger provides overall coordination. This nesting approach organizes complexity in a manageable hierarchical structure rather than a flat monolithic system.
Solution Approach 2:
The patent segments the blockchain system into multiple independent ledgers (master ledger and sub-ledgers), each responsible for specific data types and domains. This segmentation allows each ledger to be optimized independently for its specific purpose, reducing the complexity burden on any single component while maintaining overall system consistency through inter-ledger relationships.
3Measurement precision
If event verification with multiple conditions is performed, then data accuracy is improved, but processing time increases
Solution Approach 1:
The patent applies preliminary action by pre-defining verification conditions and data type conversion rules in the smart contracts before events are processed. When events occur, the system simply checks against pre-established criteria rather than performing complex real-time analysis, significantly reducing processing time while maintaining high data accuracy through rigorous pre-set verification.
Data Source
AI summary
Described in detail herein is a nested blockchain system. The nested blockchain system can include distributed nodes in a network. A node is configured to generate a master cryptographically verifiable distributed ledger represented by a sequence of blocks. The node spawns a first sub cryptographically verifiable ledger represented by a first genesis block containing a hash value referencing the first block generated in the master cryptographically verifiable ledger, in response to a first event. The node purges the first sub cryptographically verifiable ledger, in response to a second event.