* [bitcoindev] Test cases for signing legacy inputs in transactions
@ 2024-04-30 11:43 Ali Sherief
2024-04-30 12:48 ` Edil Guimarães de Medeiros
0 siblings, 1 reply; 3+ messages in thread
From: Ali Sherief @ 2024-04-30 11:43 UTC (permalink / raw)
To: Bitcoin Development Mailing List
[-- 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 --]
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: [bitcoindev] Test cases for signing legacy inputs in transactions
2024-04-30 11:43 [bitcoindev] Test cases for signing legacy inputs in transactions Ali Sherief
@ 2024-04-30 12:48 ` Edil Guimarães de Medeiros
2024-05-02 10:29 ` Ali Sherief
0 siblings, 1 reply; 3+ messages in thread
From: Edil Guimarães de Medeiros @ 2024-04-30 12:48 UTC (permalink / raw)
To: Ali Sherief; +Cc: Bitcoin Development Mailing List
[-- Attachment #1: Type: text/plain, Size: 2209 bytes --]
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:
> 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>
> .
>
--
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/CANJiN3%2BtCVERL2Px19oDM5P9VGj%3DkYeoEUxNSrUqVod9N_mVrg%40mail.gmail.com.
[-- Attachment #2: Type: text/html, Size: 3140 bytes --]
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: [bitcoindev] Test cases for signing legacy inputs in transactions
2024-04-30 12:48 ` Edil Guimarães de Medeiros
@ 2024-05-02 10:29 ` Ali Sherief
0 siblings, 0 replies; 3+ messages in thread
From: Ali Sherief @ 2024-05-02 10:29 UTC (permalink / raw)
To: Bitcoin Development Mailing List
[-- 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 --]
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2024-05-04 0:04 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2024-04-30 11:43 [bitcoindev] Test cases for signing legacy inputs in transactions Ali Sherief
2024-04-30 12:48 ` Edil Guimarães de Medeiros
2024-05-02 10:29 ` Ali Sherief
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox