Delivery-date: Tue, 30 Apr 2024 05:01:46 -0700
Sender: bitcoindev@googlegroups.com
Date: Tue, 30 Apr 2024 04:43:49 -0700 (PDT)
From: Ali Sherief <ali@notatether.com>
To: Bitcoin Development Mailing List <bitcoindev@googlegroups.com>
Message-Id: <b165f262-e733-46c1-a6f3-328fc8b13288n@googlegroups.com>
Subject: [bitcoindev] Test cases for signing legacy inputs in transactions
MIME-Version: 1.0
Content-Type: multipart/mixed; 
	boundary="----=_Part_41394_1124310358.1714477429167"
Precedence: list
Mailing-list: list bitcoindev@googlegroups.com; contact bitcoindev+owners@googlegroups.com

------=_Part_41394_1124310358.1714477429167
Content-Type: multipart/alternative; 
	boundary="----=_Part_41395_1519470858.1714477429167"

------=_Part_41395_1519470858.1714477429167
Content-Type: text/plain; charset="UTF-8"

Hi all,

I am aware that there are tons of raw transactions that can be used for 
testing Segwit transaction constructors in BIP143 and also in the tests/ 
folder of the codebase somewhere.

However, I am having a hard time finding reproducible legacy transactions. 
This is usually for one of two reasons:

1) Important information for debugging the transaction signing such as the 
preimage or private key is missing.
2) The transactions were using OpenSSL to create the signatures, which 
results in them being non-deterministic and useless for tests. As opposed 
to using libsecp256k1.

So I am just wondering if anybody knows if there is a place where I can 
find a bunch of raw legacy transactions, together with private keys, to 
test my software with.

-Ali

-- 
You received this message because you are subscribed to the Google Groups "Bitcoin Development Mailing List" group.
To unsubscribe from this group and stop receiving emails from it, send an email to bitcoindev+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/bitcoindev/b165f262-e733-46c1-a6f3-328fc8b13288n%40googlegroups.com.

------=_Part_41395_1519470858.1714477429167
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

Hi all,<div><br /></div><div>I am aware that there are tons of raw transact=
ions that can be used for testing Segwit transaction constructors in BIP143=
 and also in the tests/ folder of the codebase somewhere.</div><div><br /><=
/div><div>However, I am having a hard time finding reproducible legacy tran=
sactions. This is usually for one of two reasons:</div><div><br /></div><di=
v>1) Important information for debugging the transaction signing such as th=
e preimage or private key is missing.</div><div>2) The transactions were us=
ing OpenSSL to create the signatures, which results in them being non-deter=
ministic and useless for tests. As opposed to using libsecp256k1.<br /><br =
/>So I am just wondering if anybody knows if there is a place where I can f=
ind a bunch of raw legacy transactions, together with private keys, to test=
 my software with.<br /><br />-Ali</div>

<p></p>

-- <br />
You received this message because you are subscribed to the Google Groups &=
quot;Bitcoin Development Mailing List&quot; group.<br />
To unsubscribe from this group and stop receiving emails from it, send an e=
mail to <a href=3D"mailto:bitcoindev+unsubscribe@googlegroups.com">bitcoind=
ev+unsubscribe@googlegroups.com</a>.<br />
To view this discussion on the web visit <a href=3D"https://groups.google.c=
om/d/msgid/bitcoindev/b165f262-e733-46c1-a6f3-328fc8b13288n%40googlegroups.=
com?utm_medium=3Demail&utm_source=3Dfooter">https://groups.google.com/d/msg=
id/bitcoindev/b165f262-e733-46c1-a6f3-328fc8b13288n%40googlegroups.com</a>.=
<br />

------=_Part_41395_1519470858.1714477429167--

------=_Part_41394_1124310358.1714477429167--