Ledger System Transaction Request Management
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current ledger systems are time-consuming and prone to human error in managing transaction requests, and they lack efficient methods for verifying immutability, reliability, and traceability of transactions due to their non-immutable nature and complex consensus processes.
Innovation Solution
A ledger system that receives and stores transaction requests in separate request streams, with storage information indexed in an index stream and authentication information stored in a storage stream, allowing for efficient management and verification of transactions, even if the ledger server fails, by separating the storage of transaction requests from the generation of blocks and indexes.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If distributed ledger systems use consensus processes to validate transactions, then security and immutability are improved, but processing time and system complexity increase significantly
Solution Approach 1:
The patent segments the ledger system into multiple independent ledger servers, each maintaining its own ledger copy. Transaction validation is divided into individual server operations rather than requiring full consensus, allowing parallel processing while maintaining reliability through distributed storage architecture.
Solution Approach 2:
The system pre-distributes ledger copies to multiple servers before transactions occur. This preliminary setup allows immediate transaction processing without waiting for consensus assembly, as each server can independently validate and record transactions against its pre-loaded ledger copy.
2Reliability
If distributed ledger systems use consensus processes to validate transactions, then security and immutability are improved, but device complexity increases
Solution Approach 1:
The consensus process is segmented into independent server operations. Each ledger server operates autonomously with its own validation logic, eliminating the need for complex inter-server consensus coordination while maintaining reliability through distributed redundancy.
Solution Approach 2:
Each ledger server independently performs transaction validation and ledger maintenance without requiring active consensus coordination with other servers. The system achieves reliability through passive distribution and independent operation rather than active consensus management.
3Stability of the object's composition
If transaction requests are stored in a single ledger, then data consistency is improved, but storage reliability decreases due to single point of failure
Solution Approach 1:
The single ledger is segmented into multiple distributed ledger copies stored across different servers. Each server maintains an identical copy, providing both data consistency through replication and storage reliability through distribution, eliminating the single point of failure.
Solution Approach 2:
Each ledger server maintains a local copy of the complete ledger with identical data quality and consistency. This local replication ensures that every server can independently verify and process transactions while the distributed nature provides fault tolerance.
Data Source
Figure 1~2
Figure 3~4B
Figure 5
AI summary
Disclosed herein are methods, systems, and apparatus, including computer programs encoded on computer storage media, for managing transaction requests in ledger systems. One of the methods includes: receiving a plurality of transaction requests by a computing system, each of the plurality of transaction requests including content information of a corresponding transaction and authentication information of the corresponding transaction, storing each of the plurality of transaction requests in a request stream by the computing system, obtaining storage information of a transaction request of the plurality of transaction requests in the request stream by the computing system, and storing the storage information of the transaction request in an index of an index stream and authentication information of a transaction corresponding to the transaction request in a storage element of a storage stream by the computing system, the storage element corresponding to the index, the index stream being associated with the storage stream.