Test cases for signing legacy inputs in transactions
3 messages, 30 Apr to 2 May 2024. Started by Ali Sherief.
Ali Sherief (2), Edil Guimarães de Medeiros
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
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 <ali@notatether•com> escreveu:
Quoted text (31 lines)
> 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 > <https://groups.google.com/d/msgid/bitcoindev/b165f262-e733-46c1-a6f3-328fc8b13288n%40googlegroups.com?utm_medium=email&utm_source=footer> > . >
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:
Quoted text (47 lines)
> 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 >