File Registration Terminal for Editable Ledger Verification
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing distributed ledger technologies face challenges in managing large files due to hash value discrepancies during file edits, leading to difficulties in confirming file associations and determining authorized edits, necessitating high rewriting performance and offline verification methods.
Innovation Solution
A registration terminal and holder terminal utilize private and public keys, random numbers, and chameleon hashes to generate and verify file identifiers, ensuring consistent association with management information even after file updates, without requiring frequent updates to the distributed ledger.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If a hash value of a file and an identifier corresponding to the hash value are recorded on the distributed ledger, then association verification with management information can be made, but when the file is corrected even a little and hash values compared in the association verification are different from each other, the association cannot be confirmed
Solution Approach 1:
The patent applies preliminary action by recording not only the current file hash but also historical hash values and version information on the distributed ledger before file edits occur. This allows the system to maintain association verification capability even when files are modified, as the ledger contains the necessary historical data to verify associations at any point in time without requiring continuous updates.
Solution Approach 2:
The patent introduces version information and historical hash values as intermediary elements between the file and the management information on the distributed ledger. These intermediaries serve as bridges that maintain association even when the file hash changes due to edits, allowing verification without direct comparison of current hashes alone.
2Reliability
Because the file is modified in processing of management, distribution, and analysis, it is necessary to keep modifying a distributed ledger each time the file is edited, and relatively high rewriting performance is required
Solution Approach 1:
The patent applies preliminary action by pre-recording version information and historical hash values on the distributed ledger before file edits occur. This allows the system to maintain association verification capability without requiring continuous updates to the ledger during file editing operations, reducing the frequency of ledger rewrites while maintaining reliability.
Solution Approach 2:
The patent creates copies of historical file states and their corresponding hash values on the distributed ledger. These copies serve as reference points that allow verification of file associations without requiring the main ledger to be continuously rewritten during file editing operations, reducing system complexity.
3Reliability
When the association between the file and the management information is secured by updating the file to the distributed ledger, then data management state can be recorded, but when files are distributed and processed or corrected off-line, a method of confirming the association with the management information is required
Solution Approach 1:
The patent applies preliminary action by pre-recording version information, historical hash values, and association data on the distributed ledger before offline file processing occurs. This allows users to edit files offline without needing to maintain continuous connection to the ledger, while still being able to verify associations by comparing local historical data with the recorded management information state.
Solution Approach 2:
The patent introduces version information and historical hash values as intermediary data that bridge offline file processing and the distributed ledger. These intermediaries allow offline edits to be verified against the ledger without requiring continuous synchronization, making the system easier to operate while maintaining reliability.
Data Source
AI summary
A registration terminal according to an embodiment is a registration terminal connectable to a distributed ledger network, and includes a first generation unit that generates a private key for an identifier used for generation of an identifier of a file and a public key for an identifier used for generation of the identifier, a second generation unit that generates a transaction related to generation of management information to the distributed ledger network and transmits the transaction to the distributed ledger network to generate the management information to the distributed ledger network, and a third generation unit that generates an identifier of a processing target file as an identifier registered in the management information by using the public key for an identifier.