Distributed Ledger Data Security Flexibility
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Distributed ledger systems, such as blockchain, face challenges in interoperability with external nodes and lack flexibility in data management, leading to high data security but low flexibility, making it difficult to alter or remove personal data once stored.
Innovation Solution
A method that enables interoperability between distributed ledger systems and external nodes by using decentralized identifiers and hash values, allowing for secure data communication and flexible data management through consensus processing among nodes, enabling the 'right to be forgotten' by modifying or deleting data blocks.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If conventional blockchain systems store data in immutable data blocks with cryptographic hashing, then data security is improved, but data flexibility deteriorates
Solution Approach 1:
The patent divides data storage into two separate layers: an immutable blockchain layer storing only hash values and a mutable external storage layer storing actual data. This segmentation allows the blockchain to maintain its security properties while external storage provides flexibility for data modification and deletion.
Solution Approach 2:
The patent introduces hash values as an intermediary between the immutable blockchain and mutable external storage. The hash value serves as a reference link that maintains data integrity verification while allowing the actual data to be stored and modified externally without compromising blockchain immutability.
2Reliability
If distributed ledger systems implement consensus mechanisms for data integrity, then data security is improved, but interoperability with external nodes deteriorates
Solution Approach 1:
The patent uses hash values as intermediaries that enable communication between the distributed ledger system and external nodes. External nodes can verify data integrity through hash verification without needing to participate in the consensus mechanism, thus enabling interoperability while maintaining security.
Solution Approach 2:
The patent creates a simplified copy of data verification functionality that can operate outside the consensus mechanism. External nodes can obtain and verify hash values without being part of the distributed ledger, allowing them to interact with the system without implementing full consensus protocols.
3Productivity
If personal data is stored in blockchain data blocks for transaction processing, then transaction functionality is improved, but data privacy compliance deteriorates
Solution Approach 1:
The patent extracts personal data from the immutable blockchain structure and stores it in external mutable storage. Only hash values remain in the blockchain, while actual personal data can be deleted or modified externally to comply with privacy regulations like the right to be forgotten.
Solution Approach 2:
The hash value serves as an intermediary that maintains the link between blockchain transactions and external personal data. This allows transaction functionality to be preserved through hash verification while enabling deletion of personal data externally without affecting the integrity of the blockchain transaction record.
Data Source
Figure 1A
Figure 1B~1C
Figure 2
AI summary
It is inter-alia disclosed a method performed by at least one apparatus, the method comprising storing of a first data portion and of a second data portion of at least one data block in a data memory portion assigned to the at least one node, wherein the first data portion is stored as immutable data; causing first hash information to be stored in association with the first data portion as part of a distributed ledger; causing second hash information to be stored in association with the second data portion as part of the distributed ledger; obtaining modification request information relating to the at least one data block; causing of the second hash information associated with the second data portion to be deleted and/or causing of new second hash information to be stored in association with a new second data portion for the at least one data block as part of the distributed ledger based on the modification request information.