Distributed Ledger Digital Record Platform for Enterprise Contract Consistency
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current digital record management systems are manual, resource-intensive, and insecure, particularly in cooperative efforts between enterprises, where managing and securing digital records across multiple parties is challenging.
Innovation Solution
A digital record management platform utilizing a distributed ledger system (DLS), specifically a blockchain network, to securely manage and record contracts between enterprises by generating transaction hash codes, updating records, and executing consensus protocols to ensure data consistency and immutability.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If manual digital record management is used between enterprises, then ease of operation is maintained, but security and reliability are compromised
Solution Approach 1:
The patent replaces manual mechanical record management processes with an automated distributed ledger system. The system automatically generates transaction hash codes, maintains version histories, and executes consensus protocols without manual intervention, thereby improving security while reducing operational effort.
Solution Approach 2:
The distributed ledger system performs self-verification through consensus protocols and automatic hash code generation. The system autonomously manages digital record integrity, version control, and security verification without requiring manual security management, thus improving reliability while reducing manual effort.
2Reliability
If distributed ledger system is implemented, then security and immutability are improved, but device complexity increases
Solution Approach 1:
The distributed ledger system performs multiple functions including hash code generation, version control, consensus execution, and integrity verification within a single unified platform. This multi-functionality improves immutability while managing complexity by consolidating security functions rather than adding separate systems.
Solution Approach 2:
The system segments complex security operations into modular components: transaction hash code generation, version history maintenance, consensus protocol execution, and digital signature verification. This segmentation improves immutability through specialized functions while managing overall system complexity through modular design.
3Reliability
If consensus protocol is executed for each transaction, then reliability and consistency are improved, but productivity decreases
Solution Approach 1:
The system executes consensus protocols selectively based on transaction types and sensitivity levels. Not all transactions require full consensus execution, allowing the system to maintain consistency for critical records while improving productivity for routine transactions through reduced consensus overhead.
Solution Approach 2:
The system performs preliminary hash code generation and version validation before consensus execution. This preliminary action ensures that only valid transactions proceed to consensus, improving consistency while reducing the overall time required for transaction processing by pre-validating data integrity.
4Measurement precision
If transaction hash codes are generated for all documents, then measurement precision and integrity are improved, but use of energy increases
Solution Approach 1:
The system generates transaction hash codes selectively for critical document sections and metadata rather than entire documents. This local quality approach maintains integrity verification precision for essential elements while reducing computational energy by avoiding redundant hashing of unchanged content.
Solution Approach 2:
The system performs partial hash code generation for document subsets that change between versions. By hashing only modified sections rather than entire documents, the system maintains integrity verification precision while significantly reducing the computational energy required for each transaction.
Data Source
AI summary
Implementations include actions of providing a first transaction hash including a digital representation of a digital record between a first peer and a second peer within a digital records platform, the platform provided by the first peer as a host peer, and the transaction hash being generated based on one or more documents underlying the digital record, receiving one or more edits to at least one document from the second peer, updating the first transaction hash to provide: a second transaction hash, and a transaction hash history including the first transaction hash and the second transaction hash, receiving approval of the digital record from each of the first peer and the second peer, and executing a consensus protocol by a notary service of a third node to update transaction objects across the first node and the second node, the updating indicating that the transaction objects are consistent.