Blockchain Nonce List for Concurrent Transaction Processing
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current blockchain transaction processing methods face limitations in transaction concurrency capability and are vulnerable to replay attacks, which restrict the efficiency and reliability of transaction execution, especially in high-concurrency scenarios.
Innovation Solution
A blockchain-based transaction processing method that maintains a Nonce list with group identifiers and Nonce values, allowing concurrent execution of transactions with the same group identifier while incorporating replay attack detection by incrementing Nonce values to prevent repeated transactions, thereby enhancing transaction concurrency and security.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If traditional blockchain transaction processing is used, then replay attack protection is provided through sequential Nonce verification, but transaction concurrency capability is limited
Solution Approach 1:
The Nonce list is segmented into multiple Nonce records, each associated with a specific transaction. Instead of using a single sequential Nonce counter, the system divides the verification space into discrete Nonce records that can be independently matched with transactions, enabling parallel processing while maintaining security.
Solution Approach 2:
The Nonce list is pre-generated and stored in the blockchain before transactions are submitted. This preliminary action allows client devices to retrieve and match Nonce records with transactions locally without requiring sequential verification, thereby enabling concurrent transaction processing while maintaining replay attack protection.
2Productivity
If transaction concurrency is increased to improve processing efficiency, then productivity is improved, but vulnerability to replay attacks increases
Solution Approach 1:
The system implements a feedback mechanism where transaction execution results are used to update the Nonce list. After transactions are concurrently processed, the system verifies their completion and updates the corresponding Nonce records in the list, ensuring that replayed transactions can be detected and rejected based on the updated state.
Solution Approach 2:
The Nonce list acts as an intermediary between transaction submission and execution verification. It provides a decoupled verification mechanism that allows transactions to be processed concurrently while the Nonce list maintains the security boundary by providing unique matchable records for each transaction, preventing replay attacks without blocking parallel processing.
3Reliability
If sequential Nonce verification is used to prevent replay attacks, then security is maintained, but transaction execution time increases
Solution Approach 1:
The Nonce list is pre-generated and stored in the blockchain before transactions are submitted. This preliminary action allows client devices to retrieve and match Nonce records with transactions locally without requiring sequential verification, thereby enabling concurrent transaction processing while maintaining replay attack protection.
Solution Approach 2:
The system uses Nonce records as copies or references that can be independently matched with transactions. Instead of performing sequential verification of a single Nonce counter, the system creates multiple independent Nonce record copies in the list, each of which can be matched with a corresponding transaction in parallel, significantly reducing verification time while maintaining security.
Data Source
Figure 1~2
Figure 3
Figure 4~5
AI summary
A blockchain-based transaction processing method is disclosed. A Nonce list corresponding to a user account is maintained in a blockchain, the Nonce list includes a plurality of Nonce records, the Nonce record includes a group identifier and a Nonce value, and the method includes: obtaining, from the Nonce list, available Nonce records that include the same group identifier for a plurality of transactions that need to be concurrently executed and are initiated by a user through the user account; respectively adding the obtained available Nonce records to the plurality of transactions; and publishing the plurality of transactions in the blockchain, so that a node device in the blockchain matches an available Nonce record in a transaction published by the client device with the Nonce record in the Nonce list, and when the available Nonce record matches any target Nonce record in the Nonce list, processes the transaction, and concurrently executes a plurality of transactions with the same group identifier in processed transactions.