Distributed Ledger Ordering via Terminal Hash Linking
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing data management systems using distributed ledger technology face increased costs and load when proving the ordering of data across multiple ledgers, as they require obtaining a timestamp token for each record update, leading to inefficiencies in data management.
Innovation Solution
The system incorporates a record hash value from one distributed ledger into another, associating the ledgers and allowing proof of ordering without excessive data capacity increase, enabling users to associate and prove the ordering of data updates efficiently by storing a terminal value in a secondary ledger.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If a timestamp token is obtained for each record update in multiple distributed ledgers, then the ordering of data can be proven, but the operational cost and system load increase
Solution Approach 1:
The patent merges multiple distributed ledgers by storing terminal values (hash values of terminal records) from one ledger into records of another ledger. This combination allows the system to prove ordering across multiple ledgers without requiring separate timestamp tokens for each ledger, thereby reducing operational costs and system load while maintaining reliability.
2Adaptability or versatility
If multiple distributed ledgers are maintained separately, then data for different IDs can be managed independently, but proving the ordering between ledgers becomes costly and complex
Solution Approach 1:
The patent introduces terminal values (hash values) as intermediary elements that link records across different distributed ledgers. By storing these terminal values in records of other ledgers, the system creates a mediator mechanism that proves ordering between independently managed ledgers without requiring complex cross-ledger verification protocols, thus reducing device complexity while maintaining adaptability.
Data Source
Figure 1
Figure 2
Figure 3
AI summary
When a controller (21) of a client server (2) updates component data (D12) to component data (D13), the controller (21) creates in a first proof chain (a distributed ledger 51), a record (Age [3]) including a hash value of the component data (D13). Then, the controller (21) generates a terminal hash value which is a hash value of a terminal record (Age [3]) in the first proof chain. The controller (21) has the generated terminal hash value stored in a record in a second proof chain (a distributed ledger 52), and associates the distributed ledger (51) and the distributed ledger (52) with each other.