Signature Server Token Permission Rule for Secure Proxy Transactions
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
In the context of blockchain and virtual currency transactions, users face challenges in managing authentication information securely, particularly when currency exchange rates fluctuate rapidly, leading to discrepancies between intended and actual transaction amounts, and existing technologies struggle to collate permission contents with actual transaction contents.
Innovation Solution
A signature server is introduced that generates a permission rule based on transaction information, issuing a token to a web application and determining whether to issue a digital signature only if the transaction contents fall within the specified permission range, ensuring that transactions are executed within the intended limits.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Ease of operation
If authentication information is managed in a server of the web application, then ease of operation is improved, but security deteriorates due to risk of leakage
Solution Approach 1:
The system is divided into two separate servers: a web application server for handling user operations and a signature server for managing authentication information. This segmentation allows the web application to maintain ease of operation while the signature server ensures security by isolating sensitive authentication data.
Solution Approach 2:
Authentication information is extracted from the web application server and stored in a dedicated signature server. This extraction removes the security risk from the web application while maintaining its operational functionality, as the signature server becomes the sole repository for sensitive credentials.
2Reliability
If a separate signature server is prepared, then security is improved, but device complexity increases
Solution Approach 1:
The signature server is designed to handle multiple functions: storing authentication information, generating digital signatures, and verifying transaction permissions. By consolidating these functions in a single dedicated server, the system improves security without proportionally increasing overall system complexity.
Solution Approach 2:
The signature server acts as an intermediary between the web application and the blockchain network. It receives transaction requests from the web application, verifies permissions against stored authentication information, and executes transactions on the blockchain. This intermediary role simplifies the architecture compared to having each component handle its own authentication logic.
3Manufacturing precision
If permission range is determined based on transaction information, then manufacturing precision is improved, but device complexity increases due to additional verification processes
Solution Approach 1:
The signature server determines the permission range based on transaction information before executing the transaction. This preliminary determination of permissions ensures precision in controlling what transactions can be executed, while the verification process is integrated into the existing transaction flow rather than adding separate complex verification systems.
Data Source
Figure 1
Figure 2
Figure 3
AI summary
A signature server includes: a processing unit that, in response to reception of a token issue request including transaction information from a user, generates a permission rule for determining a permission range of transaction contents based on the transaction information and transmits a token corresponding to the permission rule to a web application which processes a proxy transaction for the user, and in response to reception of a signature issue request based on a transaction request by the user including the token from the web application, determines whether or not to issue a digital signature corresponding to the signature issue request, based on whether or not the transaction contents included in the transaction request are within the permission range determined by the permission rule corresponding to the token included in the signature issue request.