Primary Locking Script Propagation Across Transaction Chains
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing methods for enforcing a chain of blockchain transactions to include the same locking script are resource-intensive, require third-party involvement, prone to transaction bloat, and susceptible to replay attacks.
Innovation Solution
Implement a mechanism where a primary locking script is propagated through a chain of transactions using auxiliary locking scripts, ensuring each transaction includes the primary locking script by verifying message and data items across consecutive transactions.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If existing methods are used to enforce locking script propagation, then the locking script can be enforced throughout the chain, but computational overhead increases and third-party validation is required
Solution Approach 1:
The locking script enforcement mechanism operates autonomously through cryptographic verification embedded in the blockchain protocol itself. Each node independently verifies locking scripts using standard cryptographic operations without requiring external third-party validators, making the system self-sufficient and reducing computational overhead associated with centralized validation services
Solution Approach 2:
The patent extracts the validation function from third-party entities and embeds it directly into the blockchain protocol's native verification mechanisms. By integrating locking script enforcement into the core protocol, the system eliminates the need for separate validation layers and reduces overall computational overhead
2Reliability
If existing methods are used to enforce locking script propagation, then the locking script can be enforced throughout the chain, but transaction size increases due to bloat
Solution Approach 1:
Instead of embedding the entire locking script in every transaction, the patent uses cryptographic hashes and reference pointers to represent locking scripts. This copying approach allows nodes to verify locking script enforcement without storing or transmitting the full script content repeatedly, significantly reducing transaction size while maintaining enforcement reliability
Solution Approach 2:
The patent segments the locking script verification process into separate components: the locking script definition is stored once in a previous transaction, while subsequent transactions contain only references and verification data. This segmentation prevents transaction bloat by separating the heavy script content from the lightweight verification requirements
3Reliability
If existing methods are used to enforce locking script propagation, then the locking script can be enforced throughout the chain, but security decreases due to replay attacks
Solution Approach 1:
The patent implements preliminary cryptographic binding by requiring each transaction to include specific cryptographic proofs that lock the locking script to that particular transaction context. This preliminary action prevents replay attacks by ensuring that a locking script verification in one transaction cannot be reused in another, as the cryptographic proofs are transaction-specific and cannot be transferred
Solution Approach 2:
The patent incorporates preliminary anti-replay mechanisms by requiring nonces, timestamps, or transaction-specific cryptographic signatures as part of the locking script enforcement process. These preliminary anti-actions preemptively block replay attempts before they can occur, maintaining security while preserving the integrity of locking script propagation
Data Source
Figure 1
Figure 2
Figure 3
AI summary
A method of enforcing a locking script to be propagated throughout a chain of blockchain transactions. The method comprises generating a primary transaction comprising a primary locking script configured to, when executed by an unlocking script of an auxiliary transaction, verify that the unlocking script comprises a message generated based on the auxiliary transaction, and verify, based on the message, that an output of the auxiliary transaction comprises an auxiliary locking script. The auxiliary locking script is configured to verify that an unlocking script of a second primary transaction comprises a message generated based on the second primary transaction, verify that the unlocking script of the second primary transaction comprises a data item comprising one or more locking scripts of the primary transaction, and verify, based on the message and the data item, that an output of the second primary transaction comprises the primary locking script.