Blockchain Committer Node Lock Delay Mechanism
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Centralized databases face issues such as single points of failure, dependency on network connectivity, limited data access, and high traffic bottlenecks, which can lead to data loss and resource wastage due to invalidation of transactions caused by synchronization delays in blockchain networks.
Innovation Solution
Implementing a blockchain network with smart contracts and committer nodes that utilize lock requests with synchronization delays to ensure that transactions are committed only after a specified lock delay, preventing invalidation and optimizing resource usage by committing transactions with active locks immediately while delaying non-qualifying transactions.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Speed
If transactions are committed immediately in a centralized database, then processing speed is improved, but data consistency and reliability deteriorate due to single point of failure and network dependency
Solution Approach 1:
The patent divides the centralized database into multiple distributed nodes across a blockchain network. Each node maintains a copy of the database state, eliminating the single point of failure. Transactions are segmented and processed independently by different nodes, with results aggregated to ensure consistency and reliability while maintaining processing speed.
Solution Approach 2:
The patent implements a lock request mechanism where nodes预先 (in advance) request locks on data before transactions are committed. This preliminary action ensures that data is reserved and protected before the actual transaction processing begins, preventing conflicts and ensuring reliability without delaying the overall transaction speed.
2Reliability
If synchronization delays are implemented to ensure consistency, then transaction commitment reliability is improved, but processing time increases
Solution Approach 1:
The lock request is executed in advance before the actual transaction commitment. By预先 reserving the lock and validating it beforehand, the system ensures that when the transaction is committed, the data is already prepared and consistent, eliminating the need for time-consuming synchronization delays during the commitment phase.
Solution Approach 2:
Each node independently validates lock requests and manages its own transaction commitment process. Nodes self-verify the lock status and transaction validity without requiring centralized coordination or synchronization delays, thereby maintaining reliability while reducing processing time.
3Adaptability or versatility
If multiple nodes access the same data simultaneously, then data accessibility is improved, but data consistency deteriorates due to potential overwriting
Solution Approach 1:
Before allowing multiple nodes to access and modify data, the system预先 issues lock requests to specific nodes. The lock request validates that the node has the right to access the data and establishes exclusive or shared access rights beforehand. This preliminary validation ensures that simultaneous access by multiple nodes does not compromise data consistency while maintaining high accessibility.
Data Source
AI summary
An example operation may include one or more of receiving, by a committer node or peer of a blockchain network, a block comprising a lock request that locks a partial state of a smart contract, the lock request comprising a submitter identifier and a lock delay, the committer node or peer configured to process blocks of transactions, the method further comprising, validating the lock request, committing transactions comprising the submitter identifier with no delay, and committing transactions not comprising the submitter identifier after the lock delay.