Delivery-date: Tue, 30 Apr 2024 06:32:10 -0700
Sender: bitcoindev@googlegroups.com
Received-SPF: pass (google.com: domain of jose.edil@gmail.com designates 2a00:1450:4864:20::532 as permitted sender) client-ip=2a00:1450:4864:20::532;
MIME-Version: 1.0
References: <b165f262-e733-46c1-a6f3-328fc8b13288n@googlegroups.com>
In-Reply-To: <b165f262-e733-46c1-a6f3-328fc8b13288n@googlegroups.com>
From: =?UTF-8?Q?Edil_Guimar=C3=A3es_de_Medeiros?= <jose.edil@gmail.com>
Date: Tue, 30 Apr 2024 09:48:09 -0300
Message-ID: <CANJiN3+tCVERL2Px19oDM5P9VGj=kYeoEUxNSrUqVod9N_mVrg@mail.gmail.com>
Subject: Re: [bitcoindev] Test cases for signing legacy inputs in transactions
To: Ali Sherief <ali@notatether.com>
Cc: Bitcoin Development Mailing List <bitcoindev@googlegroups.com>
Content-Type: multipart/alternative; boundary="000000000000e8ca4306174fc894"
Precedence: list
Mailing-list: list bitcoindev@googlegroups.com; contact bitcoindev+owners@googlegroups.com

--000000000000e8ca4306174fc894
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

Well, you might use core itself to create a bunch of private keys and
legacy transactions.
That will imply you trust core as a golden model for your software, but
since almost everyone in the network assumes to be bug compatible with
core, I don't see a problem.

Or am I missing something and being too simplistic?

Em ter., 30 de abr. de 2024 =C3=A0s 09:01, Ali Sherief <ali@notatether.com>
escreveu:

> 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 th=
e
> 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-328f=
c8b13288n%40googlegroups.com
> <https://groups.google.com/d/msgid/bitcoindev/b165f262-e733-46c1-a6f3-328=
fc8b13288n%40googlegroups.com?utm_medium=3Demail&utm_source=3Dfooter>
> .
>


--=20
Edil

--=20
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 e=
mail to bitcoindev+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/=
bitcoindev/CANJiN3%2BtCVERL2Px19oDM5P9VGj%3DkYeoEUxNSrUqVod9N_mVrg%40mail.g=
mail.com.

--000000000000e8ca4306174fc894
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div dir=3D"ltr"><div>Well, you might use core itself to c=
reate a bunch of private keys and legacy transactions.</div><div>That will =
imply you trust core as a golden model for your software, but since almost =
everyone in the network assumes to be bug compatible with core, I don&#39;t=
 see a problem.</div><div><br></div><div>Or am I missing something and bein=
g too simplistic?<br></div></div><br><div class=3D"gmail_quote"><div dir=3D=
"ltr" class=3D"gmail_attr">Em ter., 30 de abr. de 2024 =C3=A0s 09:01, Ali S=
herief &lt;<a href=3D"mailto:ali@notatether.com">ali@notatether.com</a>&gt;=
 escreveu:<br></div><blockquote class=3D"gmail_quote" style=3D"margin:0px 0=
px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">Hi al=
l,<div><br></div><div>I am aware that there are tons of raw transactions th=
at can be used for testing Segwit transaction constructors in BIP143 and al=
so in the tests/ folder of the codebase somewhere.</div><div><br></div><div=
>However, I am having a hard time finding reproducible legacy transactions.=
 This is usually for one of two reasons:</div><div><br></div><div>1) Import=
ant information for debugging the transaction signing such as the preimage =
or private key is missing.</div><div>2) The transactions were using OpenSSL=
 to create the signatures, which results in them being non-deterministic an=
d 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 find a bunch of =
raw legacy transactions, together with private keys, to test my software wi=
th.<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" target=
=3D"_blank">bitcoindev+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&amp;utm_source=3Dfooter" target=3D"_blank">https://g=
roups.google.com/d/msgid/bitcoindev/b165f262-e733-46c1-a6f3-328fc8b13288n%4=
0googlegroups.com</a>.<br>
</blockquote></div><br clear=3D"all"><br><span class=3D"gmail_signature_pre=
fix">-- </span><br><div dir=3D"ltr" class=3D"gmail_signature"><div dir=3D"l=
tr"><div><div dir=3D"ltr">Edil</div></div></div></div></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/CANJiN3%2BtCVERL2Px19oDM5P9VGj%3DkYeoEUxNSrUqVod9N_mV=
rg%40mail.gmail.com?utm_medium=3Demail&utm_source=3Dfooter">https://groups.=
google.com/d/msgid/bitcoindev/CANJiN3%2BtCVERL2Px19oDM5P9VGj%3DkYeoEUxNSrUq=
Vod9N_mVrg%40mail.gmail.com</a>.<br />

--000000000000e8ca4306174fc894--