Permission Queue for Distributed Ledger Token Verification
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
In blockchain transaction environments, the handling of permissions through N-of-M multisignature formats can lead to inefficiencies, such as multiple requests for tokens that exceed available balances, causing unnecessary resource consumption and potential for duplicate or improper transactions due to lack of token locking mechanisms.
Innovation Solution
Implementing a permission queue that locks tokens during proposed event requests, allowing for pre-validation of permissions before submitting requests to the blockchain, thereby preventing excessive resource usage and ensuring accurate token management.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If N-of-M multisignature format is used for permission handling, then security and control are improved, but system complexity and processing time increase
Solution Approach 1:
The patent implements pre-validation of permission requests before they are submitted to the blockchain. A permission queue is introduced that validates and queues requests in advance, checking token balances and permissions beforehand. This preliminary action reduces the complexity of handling permissions during blockchain transactions by preparing all necessary validations upstream.
Solution Approach 2:
The patent introduces a permission queue as an intermediary layer between token storage and blockchain transactions. This intermediary component manages the permission validation process, holding requests until they are ready to be processed. The permission queue acts as a mediator that simplifies the interaction between multiple signature requirements and blockchain operations.
2Productivity
If token transfer requests are processed without locking mechanism, then transaction speed is improved, but resource waste and duplicate transactions increase
Solution Approach 1:
The patent implements preliminary validation of token balances and permissions before allowing transactions to proceed. The system checks whether sufficient tokens are available and permissions are granted in advance, preventing invalid or duplicate transactions from being submitted to the blockchain. This pre-check mechanism avoids wasted resources on unsuccessful transactions.
Solution Approach 2:
The permission queue serves as an intermediary that manages token transfer requests and validates them against available balances and permission rules. By processing validation logic in this intermediate layer before blockchain submission, the system prevents resource waste from rejected transactions while maintaining efficient processing of valid ones.
3Reliability
If permission validation is performed on-chain, then blockchain integrity is improved, but network load and processing time increase
Solution Approach 1:
The patent extracts permission validation logic from the blockchain and places it in an off-chain permission queue system. This extraction removes time-consuming validation operations from the blockchain, allowing only the final approved transactions to be processed on-chain. The permission queue handles balance checks, permission verification, and request queuing before blockchain submission.
Solution Approach 2:
The system performs all necessary permission validations and balance checks in advance, before transactions are submitted to the blockchain. This preliminary action ensures that only valid, approved transactions reach the blockchain, reducing the validation time and network load during actual blockchain processing while maintaining integrity.
Data Source
AI summary
The disclosed systems and methods provide non-native functionality to a distributed network for distributed ledger token verification and event permissioning. The disclosed technology receives a transfer event request from a first node associated with a first token storage, where the transfer event request corresponds to movement of a requested token amount that is associated with at least one token. In response, the transfer event request is inserted into a pending transfer log that is configured to queue pending transfer event requests. A determination is made regarding a first permission based on the currently queued pending transfer event requests, and as a result, the transfer event request is transmitted to the distributed network based on the first permission, where such transfer causes the requested movement of the requested token amount.