Blockchain Transaction Authorization With Dual Pools for Faster Inclusion
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing blockchain implementations waste computing resources and time due to repeated confirmations of pending transactions before inclusion in a block, leading to delayed transaction processing.
Innovation Solution
Implementing a system with dual transaction pools, one for unconfirmed and one for confirmed transactions, allowing confirmed transactions to be directly included in new blocks without re-confirmation, and setting time limits to ensure timely inclusion.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Loss of energy
If a traditional single pending transaction pool is used, then the system structure is simple, but transactions are confirmed repeatedly causing waste of computing resources and time
Solution Approach 1:
The patent divides the transaction pool into two distinct segments: a pending transaction pool for unconfirmed transactions and a confirmed transaction pool for transactions that have been confirmed but not yet included in a block. This segmentation allows the system to differentiate between transactions needing full verification and those that have already been verified, eliminating redundant confirmation computations while maintaining clear structural organization.
Solution Approach 2:
The confirmed transaction pool stores transactions that have undergone preliminary confirmation verification. When a new block is generated, these pre-confirmed transactions are directly included without undergoing the full confirmation process again. This preliminary action of confirming transactions once and storing them in a dedicated pool prevents subsequent redundant verification, saving computing resources.
2Reliability
If transactions are confirmed repeatedly before block inclusion, then transaction validation is thorough, but processing time increases significantly
Solution Approach 1:
The system performs the thorough validation and confirmation action once when a transaction first enters the pending transaction pool. After this preliminary confirmation, the transaction is moved to the confirmed transaction pool where it is stored with the understanding that it has already been validated. This eliminates repeated validation cycles while maintaining validation thoroughness.
Solution Approach 2:
The confirmed transaction pool maintains continuous availability of pre-validated transactions for rapid inclusion in new blocks. Instead of repeatedly re-validating the same transactions, the system continuously utilizes the confirmed transaction pool to quickly assemble new blocks, ensuring uninterrupted and efficient block generation without redundant validation steps.
3Reliability
If confirmed transactions are not quickly included in blocks, then block generation can be thorough, but transactions remain pending for significant periods
Solution Approach 1:
By performing confirmation validation as a preliminary action and storing results in the confirmed transaction pool, the system prepares transactions for rapid inclusion in new blocks. This preliminary preparation ensures that when blocks are generated, confirmed transactions can be immediately included without delays, reducing pending duration while maintaining validation reliability.
Solution Approach 2:
The system dynamically manages transaction inclusion by continuously monitoring the confirmed transaction pool and incorporating transactions into new blocks as they are generated. This dynamic approach ensures that confirmed transactions are promptly moved from the pool to the blockchain, preventing prolonged pending states while allowing thorough validation to complete beforehand.
Data Source
AI summary
A method for expedited inclusion of pre-authorized blockchain transactions in new blocks. A blockchain node will utilize a traditional pending transaction pool of unconfirmed transactions, but will also utilize a new transaction pool that is comprised of pending blockchain transactions that have been confirmed, but have not yet been added to the blockchain. When a new block is being generated by a node, they can select pending transactions from the confirmed transaction pool and include them in the new block without repeating the confirmation process, which can save time and computing resources, thereby enabling the new block to be generated faster and increasing the chance that the new block will be the one that is validated and added to the chain. Additional rules and criteria can be applied to ensure that transactions that are in the confirmed transaction pool are added to a new block in a timely fashion.