From: Ali Sherief <ali@notatether•com>
To: Bitcoin Development Mailing List <bitcoindev@googlegroups.com>
Subject: [bitcoindev] Test cases for signing legacy inputs in transactions
Date: Tue, 30 Apr 2024 04:43:49 -0700 (PDT) [thread overview]
Message-ID: <b165f262-e733-46c1-a6f3-328fc8b13288n@googlegroups.com> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 1155 bytes --]
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.
[-- Attachment #1.2: Type: text/html, Size: 1518 bytes --]
next reply other threads:[~2024-04-30 12:01 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-30 11:43 Ali Sherief [this message]
2024-04-30 12:48 ` Edil Guimarães de Medeiros
2024-05-02 10:29 ` Ali Sherief
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=b165f262-e733-46c1-a6f3-328fc8b13288n@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