Multisignature Transaction Signing With Sighash Single Flags

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

In blockchain transactions with multisignature requirements, the traditional sighash ALL signing approach necessitates initial communication between parties to establish transaction details before signing, which can be inefficient and does not accurately reflect the hierarchical spending structure, leading to unauthorized transfers.

Innovation Solution

A computer-implemented method for generating multisignature transactions that allows parties to electronically sign specific outputs and inputs of a multisignature transaction using sighash single flags, independent of other transaction components, thereby satisfying the multisignature requirement without requiring all inputs and outputs to be known upfront.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If traditional sighash ALL signing approach is used, then all transaction components can be authorized, but initial communication between parties is required and efficiency is reduced

Engineering Contradiction:
Improveauthorization completenessVSAvoidtransaction efficiency
Core Design Contradiction:
ReliabilityVSProductivity

Solution Approach 1:

The patent segments the transaction signing process by introducing sighash single flags that allow independent signing of specific inputs and outputs. Each signature can be generated autonomously for its designated component without requiring coordination with other signing parties, thereby eliminating the need for initial communication while maintaining complete authorization through cumulative signatures.

Inventive Principle:
Principle #1Segmentation

2Reliability

If traditional sighash ALL signing approach is used, then comprehensive authorization is achieved, but hierarchical spending structure is not reflected

Engineering Contradiction:
Improveauthorization completenessVSAvoidhierarchical structure representation
Core Design Contradiction:
ReliabilityVSAdaptability or versatility

Solution Approach 1:

The patent applies local quality by assigning different sighash single flags to different inputs and outputs based on their hierarchical importance and authorization requirements. This allows the transaction structure to reflect hierarchical spending patterns where certain components require higher-level authorization while others can be signed independently, thereby adapting the authorization mechanism to the specific hierarchical needs of each transaction component.

Inventive Principle:
Principle #3Local quality

3Reliability

If traditional sighash ALL signing approach is used, then all components are signed together, but unnecessary authorization dependencies are created

Engineering Contradiction:
Improvetransaction securityVSAvoidauthorization dependency
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The patent extracts the authorization dependency by removing the requirement for coordinated signing of all transaction components. Instead, each input and output can be signed independently using sighash single flags, extracting the unnecessary dependency while maintaining security through cryptographic verification of each individual signature against its corresponding transaction component.

Inventive Principle:
Principle #2Taking out (Extraction)

Data Source

PatentUS12531751B2Multisignature transactions
Publication Date: 2026.01.20 NCHAIN LICENSING AG
  • US12531751B2 patent drawing
  • US12531751B2 patent drawing
  • US12531751B2 patent drawing

AI summary

A computer implemented method for generating a multisignature transaction for a blockchain comprising: receiving a first output and a non-signature portion of a first input, the first input comprising an outpoint to a first spendable transaction output encoding a multisignature requirement; electronically signing the first output and the non-signature portion of the first input, thereby generating a signature for satisfying the multisignature requirement when included with: (i) an associated sighash single flag, and (ii) at least one other signature; receiving a second output and a non-signature portion of a second input, the second input comprising an outpoint to a second spendable transaction output encoding a signature requirement requiring at least one signature; and electronically signing the second output and the non-signature portion of the second input, thereby generating a signature for at least partially satisfying the signature requirement when included in a signature portion with an associated sighash single flag.