From: Ali Sherief <ali@notatether•com>
To: Bitcoin Development Mailing List <bitcoindev@googlegroups.com>
Subject: Re: [bitcoindev] Test cases for signing legacy inputs in transactions
Date: Thu, 2 May 2024 03:29:42 -0700 (PDT) [thread overview]
Message-ID: <987e5090-63c3-4db3-bcd2-03e74a17b226n@googlegroups.com> (raw)
In-Reply-To: <CANJiN3+tCVERL2Px19oDM5P9VGj=kYeoEUxNSrUqVod9N_mVrg@mail.gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 2651 bytes --]
I don't think that its a good idea to rely on my own generated Core
transactions, though. Not because I don't trust Core as having a correct
transaction implementation, but because the transactions are still
ultimately generated by me so that they are not covering all the edge cases.
-Ali
On Tuesday, April 30, 2024 at 1:32:03 PM UTC Edil Guimarães de Medeiros
wrote:
> 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 às 09:01, Ali Sherief <a...@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
>> 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+...@googlegroups•com.
>> To view this discussion on the web visit
>> https://groups.google.com/d/msgid/bitcoindev/b165f262-e733-46c1-a6f3-328fc8b13288n%40googlegroups.com
>> <https://groups.google.com/d/msgid/bitcoindev/b165f262-e733-46c1-a6f3-328fc8b13288n%40googlegroups.com?utm_medium=email&utm_source=footer>
>> .
>>
>
>
> --
> Edil
>
--
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/987e5090-63c3-4db3-bcd2-03e74a17b226n%40googlegroups.com.
[-- Attachment #1.2: Type: text/html, Size: 4273 bytes --]
prev parent reply other threads:[~2024-05-04 0:04 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-30 11:43 Ali Sherief
2024-04-30 12:48 ` Edil Guimarães de Medeiros
2024-05-02 10:29 ` Ali Sherief [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=987e5090-63c3-4db3-bcd2-03e74a17b226n@googlegroups.com \
--to=ali@notatether$(echo .)com \
--cc=bitcoindev@googlegroups.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox