Local Ledger Clearing With Archivist Nodes in Distributed Ledgers
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Nodes with limited storage capacity in distributed ledgers face challenges in recording new transactions due to the large size of ledgers, leading to issues in controlling the execution of operations.
Innovation Solution
Implementing archivist nodes to manage local ledgers by authorizing nodes to empty their local ledgers after verifying the integrity of their content, using a reference transaction and a message in the distributed ledger to ensure transparency and permanence of transactions.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If all transactions are archived in every node to ensure transparency and integrity verification, then the reliability and transparency of the distributed ledger are improved, but the storage capacity requirement increases significantly, making it impossible for nodes with limited storage to continue recording new transactions
Solution Approach 1:
The patent divides the node set into two functional segments: archivist nodes that maintain complete transaction histories and ordinary nodes that maintain only local ledgers with transaction references. This segmentation allows ordinary nodes to participate in the distributed ledger with limited storage while archivist nodes ensure transparency and integrity through complete archiving.
Solution Approach 2:
The patent introduces an intermediary mechanism where archivist nodes act as mediators between the distributed ledger system and ordinary nodes. When a node needs to verify transaction integrity, it queries the archivist node instead of maintaining complete transaction history itself. The archivist node provides verification services to multiple ordinary nodes, enabling them to participate with reduced storage requirements.
2Productivity
If local ledgers are emptied to free storage space for new transactions, then the productivity and continuity of transaction recording are improved, but the ability to verify transaction integrity and maintain transparency is compromised
Solution Approach 1:
The patent implements a copying mechanism where ordinary nodes create local copies of transaction data in their ledgers, storing only essential information (transaction hash, timestamp, sender, recipient) rather than complete transaction details. This allows nodes to maintain compact local ledgers that can be easily updated while still providing sufficient information for basic verification, with full verification delegated to archivist nodes.
Solution Approach 2:
The patent employs preliminary action by having nodes record transaction references and hashes in their local ledgers before the actual transaction data is archived by archivist nodes. This preliminary recording ensures that transaction existence and basic properties are immediately verifiable, while complete integrity verification is performed later by querying archivist nodes for the archived transaction data.
3Reliability
If complete transaction histories are maintained in archivist nodes to enable verification services, then the reliability of the system is improved, but the device complexity increases due to the need for specialized archivist node infrastructure and query mechanisms
Solution Approach 1:
The patent makes archivist nodes universal by designing them to perform multiple functions: maintaining complete transaction archives, verifying transaction integrity for any ordinary node, and potentially serving as backup nodes. This multi-functionality justifies the added complexity by providing centralized verification services that benefit the entire distributed ledger network, eliminating the need for each ordinary node to implement complex verification logic.
Data Source
AI summary
In known implementations of distributed ledgers, all of the transactions linked to a service are archived in nodes involved in the implementation of the service. This makes it possible to verify the authenticity and the integrity of the transactions and to ensure that the service that is provided is compliant. This poses a problem for nodes having limited storage capacities, some ledgers possibly reaching a significant size and ultimately potentially making it impossible for some modes to be able to record new transactions, thus causing a problem in terms of controlling the actual execution of the operations linked to these transactions. The present solution allows some nodes involved in the implementation of a service to be able to empty their local ledgers without this jeopardizing the correct operation of the associated distributed ledger. The transparency and the permanence of the transactions relating to the service are thus guaranteed.


