From 805bb0b6fc093cbb7ca5f0d40fb48955e0f12fa9 Mon Sep 17 00:00:00 2001
From: Oli <gugger@gmail.com>
Date: Thu, 9 Apr 2026 12:49:16 +0200
Subject: [PATCH] BIP-0322: clarify scriptSig on to_sign for legacy
 transactions

Before this commit it was not clear that non-native SegWit outputs
(e.g. P2PKH or P2SH-P2WPKH) only work if the correct scriptSig is
provided.
This then also makes it more clear why P2SH-P2WPKH outputs are NOT
supported by the "simple" variant.
---
 bip-0322.mediawiki | 1 +
 1 file changed, 1 insertion(+)

diff --git a/bip-0322.mediawiki b/bip-0322.mediawiki
index 1ac9308b..309bde7f 100644
--- a/bip-0322.mediawiki
+++ b/bip-0322.mediawiki
@@ -96,6 +96,7 @@ The <code>to_sign</code> transaction is:
     vin[0].prevout.hash = to_spend.txid
     vin[0].prevout.n = 0
     vin[0].nSequence = 0 or (FULL format only) as appropriate (for time locks)
+    vin[0].scriptSig = [] or (FULL format only) as appropriate (for non segwit-native transactions)
     vin[0].scriptWitness = message_signature
     vout[0].nValue = 0
     vout[0].scriptPubKey = OP_RETURN