From fe875dc20226c95d9309035f9dfe5c187cdbc7d7 Mon Sep 17 00:00:00 2001
From: arjunsunar1 <168791428+arjunsunar1@users.noreply.github.com>
Date: Sat, 31 Aug 2024 23:42:57 +0400
Subject: [PATCH] =?UTF-8?q?Revert=20"[BIP322]=20remove=20empty=20message?=
 =?UTF-8?q?=20requirement=20for=20full=20(proof-of-funds)=20p=E2=80=A6"?=
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit

This reverts commit 6fc75b1b2153df40f1ff8312d7086b69bfb091de.
---
 bip-0322.mediawiki | 2 ++
 1 file changed, 2 insertions(+)

diff --git a/bip-0322.mediawiki b/bip-0322.mediawiki
index 81ef896d3b..440602f7ef 100644
--- a/bip-0322.mediawiki
+++ b/bip-0322.mediawiki
@@ -80,6 +80,8 @@ A full signature consists of the base64-encoding of the <code>to_sign</code> tra
 
 A signer may construct a proof of funds, demonstrating control of a set of UTXOs, by constructing a full signature as above, with the following modifications.
 
+* <code>message_challenge</code> is unused and shall be set to <code>OP_TRUE</code>
+* Similarly, <code>message_signature</code> is then empty.
 * All outputs that the signer wishes to demonstrate control of are included as additional inputs of <code>to_sign</code>, and their witness and scriptSig data should be set as though these outputs were actually being spent.
 
 Unlike an ordinary signature, validators of a proof of funds need access to the current UTXO set, to learn that the claimed inputs exist on the blockchain, and to learn their scriptPubKeys.