Blockchain Transaction Log for Efficient Querying
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current blockchain systems are inefficient when querying a series of related transactions generated by a service task, as they require traversing the entire blockchain, which is time-consuming and resource-intensive.
Innovation Solution
Implementing a method where each node in the blockchain network uses a pre-deployed smart contract to write the transaction identifier of previous transactions into a transaction log for each blockchain transaction, allowing for efficient querying of previous transactions by referencing the log, thereby avoiding the need to traverse the entire blockchain.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If blockchain transactions are stored and queried by traversing the entire blockchain, then all transactions are reliably recorded, but query efficiency deteriorates significantly
Solution Approach 1:
The patent applies preliminary action by writing the transaction identifier of the previous blockchain transaction into the transaction log during the transaction submission process itself. This pre-establishes the linkage relationship between transactions, so that when querying is needed, the system can directly follow the transaction log chain without traversing the entire blockchain. The transaction log is prepared in advance with the necessary navigation information (previous transaction ID), enabling efficient backward queries while maintaining data reliability.
2Loss of information
If the entire blockchain is traversed to query related transactions, then complete transaction history is obtained, but time consumption and computational resources increase
Solution Approach 1:
The patent extracts the essential navigation information (transaction identifier of the previous transaction) from the complete blockchain data and stores it in the transaction log. Instead of traversing the entire blockchain to find related transactions, the query system only needs to read the compact transaction log which contains the extracted key information. This extraction principle reduces the query complexity from O(n) traversing the entire blockchain to O(1) direct lookup in the transaction log, while still obtaining complete transaction history through iterative following of the log chain.
3Productivity
If transaction logs with previous transaction identifiers are written for each blockchain transaction, then query efficiency improves, but device complexity increases
Solution Approach 1:
The patent makes the transaction log serve multiple functions: it records the transaction identifier for query efficiency, maintains the chronological order of transactions, and provides a compact representation of the transaction chain. Instead of creating separate complex data structures for navigation and storage, the transaction log universally handles multiple purposes with a simple key-value structure (current transaction ID and previous transaction ID). This multi-functionality approach improves query efficiency while minimizing the increase in system complexity.
Data Source
AI summary
Disclosed herein are methods, systems, and apparatus, including computer programs encoded on computer storage media, for blockchain transaction processing. One of the methods includes: obtaining, by a blockchain node, a current blockchain transaction generated based on performing a service; obtaining, by the blockchain node based on executing a smart contract, a transaction identifier of a previous blockchain transaction; recording, by the blockchain node, the transaction identifier into a transaction log so that a previous blockchain transaction is identifiable from the transaction log based on the transaction identifier, wherein the transaction log stores blockchain transactions of the current block; and recording the blockchain transaction of the current block and the transaction log into the blockchain.