Blockchain Script Constraints Using Runtime State Injection

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing blockchain technologies lack the ability to encode constraints based on the state of the blockchain, such as block headers or transactions, within locking scripts, limiting the flexibility and complexity of smart contracts and transactions.

Innovation Solution

Implementing constraints on unlocking scripts to require block headers, blockchains, or chains of block headers, and injecting this data at runtime to enable transactions that depend on the state of the blockchain, allowing validation without verifying the creator's access to secret information.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If constraints based on blockchain state (block headers, transactions) are encoded within locking scripts, then the flexibility and complexity of smart contracts are improved, but the device complexity and script length increase

Engineering Contradiction:
Improveflexibility and complexity of smart contractsVSAvoidlocking script complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The locking script is divided into two separate components: a first script containing constraints that must be satisfied, and a second script providing data to satisfy those constraints. This segmentation allows complex blockchain state verification to be organized into manageable, modular script segments that can be executed and validated separately.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

A node in the blockchain network acts as an intermediary that executes both scripts and validates whether the second script's output satisfies the first script's constraints. This intermediary mechanism enables complex state-based verification without requiring the constraints to be embedded directly within a single monolithic locking script.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Adaptability or versatility

If blockchain state data (block headers, transactions) is injected at runtime into unlocking scripts, then transactions can depend on the state of the blockchain, but the validation process becomes more complex

Engineering Contradiction:
Improvetransaction state dependencyVSAvoidvalidation process complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The first script is prepared in advance with all necessary constraints encoded, defining what conditions must be met for transaction validation. This preliminary configuration of validation rules allows the system to efficiently check blockchain state data at runtime without ad-hoc complexity during the validation phase.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The validation process uses feedback from executing the second script to determine whether the first script's constraints are satisfied. The node evaluates the output of the second script against the constraints in the first script, creating a feedback loop that automatically validates transaction state dependencies without manual intervention.

Inventive Principle:
Principle #23Feedback

3Reliability

If constraints require verification of blockchain state without accessing secret information, then transaction security is improved, but the measurement precision of constraint verification decreases

Engineering Contradiction:
Improvetransaction securityVSAvoidconstraint verification precision
Core Design Contradiction:
ReliabilityVSMeasurement precision

Solution Approach 1:

The unlocking script itself provides the necessary data to satisfy the locking script's constraints, without requiring external verification of secret information. The script autonomously generates and includes the blockchain state data needed for validation, allowing the system to verify constraints while maintaining security through cryptographic proof rather than secret exposure.

Inventive Principle:
Principle #25Self-service

Data Source

PatentUS20260004291A1Script-based blockchain interaction
Publication Date: 2026.01.01 NCHAIN LICENSING AG
  • US20260004291A1 patent drawing
  • US20260004291A1 patent drawing
  • US20260004291A1 patent drawing

AI summary

There may be provided a computer-implemented method. It may be implemented using a blockchain network such as, for example, the Bitcoin network. The computer-implemented method includes: i) receiving, at a node in a blockchain network, a first transaction associated with a digital asset, the first transaction including a first script that specifies a set of constraints on a second transaction to transfer control of the digital asset, the set of constraints including a constraint that a set of data obtained by the node includes information obtained from a blockchain associated with the blockchain network; ii) obtaining the second transaction, the second transaction including a second script that, as a result of being executed, causes the node to obtain the set of data; and iii) validating the second transaction by executing the first script and the second script.