Multi-Signature Transaction Validation for Agile Policy Enforcement
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing blockchain transaction signing systems are inflexible and vulnerable to security concerns due to rigid policy enforcement, making it difficult to adapt to changing policies and external security risks.
Innovation Solution
A method and system for validating transactions with multiple digital signatures, where a first signature is applied upon policy verification and a second signature upon completion of an instruction workflow, ensuring cryptographic security and allowing agile policy updates without compromising privacy.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If a signing service implements a rudimentary policy engine, then policy rules can be enforced, but the policy rules are limited and changes are subject to the release procedures of the signing service
Solution Approach 1:
The system segments the signing service into two independent components: a signing service that handles cryptographic operations and a separate policy validation service that handles policy rule enforcement. This segmentation allows each component to be developed, updated, and maintained independently, enabling flexible policy changes without affecting the signing service's release cycle.
Solution Approach 2:
The system introduces an intermediary policy validation service that acts as a mediator between the signing service and the blockchain network. This intermediary validates policy rules separately from the signing operation, allowing policy rules to be updated independently while maintaining security through the signing service's cryptographic functions.
2Adaptability or versatility
If a signing service calls an external service for policy checks, then policy enforcement is separated from signing, but security concerns arise due to the signing service's vulnerability when relying on external resources
Solution Approach 1:
The system introduces an intermediary policy validation service that acts as a mediator between the signing service and the blockchain network. This intermediary validates policy rules separately from the signing operation, allowing policy rules to be updated independently while maintaining security through the signing service's cryptographic functions.
Solution Approach 2:
The system performs preliminary policy validation before the signing operation occurs. The policy validation service validates policy rules in advance and returns validation results to the signing service, which then proceeds with signing only if validation succeeds. This preliminary action ensures security by verifying policies before cryptographic operations begin.
3Reliability
If policy enforcement is integrated with transaction signing, then security is maintained, but the system becomes rigid and changes are difficult
Solution Approach 1:
The system segments the signing service into two independent components: a signing service that handles cryptographic operations and a separate policy validation service that handles policy rule enforcement. This segmentation allows each component to be developed, updated, and maintained independently, enabling flexible policy changes without affecting the signing service's release cycle.
Solution Approach 2:
The system extracts the policy enforcement functionality from the signing service and places it in a separate policy validation service. This extraction removes the rigidity of integrated systems while maintaining security through the signing service's cryptographic functions, as the policy validation service operates independently but is required for successful transaction processing.
Data Source
AI summary
Systems and methods for validating an instruction with multiple digital signatures may receive an instruction to initiate a transaction; generate first and second digital certificates; validate a set of one or more policy limits; sign the instruction using the first digital certificate, based on the validating; instantiate an instruction workflow associated with the transaction; sign the instruction workflow using the second digital certificate, based on completion of the instruction workflow; build a transaction request, in which the transaction request includes at least the instruction, the first signature, and the second signature; verify the first and second signatures; and sign the transaction request.


