Delivery-date: Fri, 03 May 2024 17:04:18 -0700 Received: from mail-yb1-f184.google.com ([209.85.219.184]) by mail.fairlystable.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.94.2) (envelope-from ) id 1s32sz-0007za-MW for bitcoindev@gnusha.org; Fri, 03 May 2024 17:04:18 -0700 Received: by mail-yb1-f184.google.com with SMTP id 3f1490d57ef6-de59ff8af0bsf438107276.2 for ; Fri, 03 May 2024 17:04:17 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlegroups.com; s=20230601; t=1714781051; x=1715385851; darn=gnusha.org; h=list-unsubscribe:list-subscribe:list-archive:list-help:list-post :list-id:mailing-list:precedence:x-original-sender:mime-version :subject:references:in-reply-to:message-id:to:from:date:sender:from :to:cc:subject:date:message-id:reply-to; bh=NYstt/56idDMsaoqEEKGA/5Cq6unoHSsw7m18GL0Yls=; b=bb7WmwxxBA66ttDN2hPjNj5LVXM9xJe3a/JrZU1AbWxntMo6AKyqFQ1fPWu9EAsHAc IGQVkGlVME6t9RZwN931vbedRI1085bsmdpoV3WobBDrUVpePVgy7LHlLIy//+xNRyfR VeoV6TIM56vMI8XH7WdDXYCd+nov53rHKRunW6LPrL9yEe4bWAzEAsrThBUKM6tqEOn/ gNohIdecSIiYG3QcZwupRyGfCQOKMp0zGbCqZ7yGp9Fa3tfo8JyhPY6n05KHJukeL0Ib 4FfxoMY8+o0HX0J3ZOGgHSyUb7OmQq0V9JSuzMHfRsLmTIWm99hB+t0AIJAxQGsa5Wh+ itfA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1714781051; x=1715385851; h=list-unsubscribe:list-subscribe:list-archive:list-help:list-post :list-id:mailing-list:precedence:x-original-sender:mime-version :subject:references:in-reply-to:message-id:to:from:date:x-beenthere :x-gm-message-state:sender:from:to:cc:subject:date:message-id :reply-to; bh=NYstt/56idDMsaoqEEKGA/5Cq6unoHSsw7m18GL0Yls=; b=iPlN6FhL/2vkSYP5KZMP8tukpeYPiBI/83Qr9NkEWMsTX13HcQbOHzNPcxlrV/VOBa VoRXsWepJy35G/cuDCkRyhX67ICcugq2/nW/AG9xZH/jgl05NZtveVeGT52cjGw7/KNH 7A8+rsv9CX0f2kUzuIbmg6KTRT8jk/gl7Lj7WR5mgkGs9hPDn8aICV4l2gT/z9uFWiGj r5paCcyvSd0Vo6YI6fo0zox8fg7/+I9SA2phdlSTaYJUcLptoQnCtP+Yy7sKSuOED5zw LqQ91GccJWc0n52Xec1ua6h2jlsBGguyFrAsS3lutS787U62/EHmmNfvMvXE8VuwoBEx 44/A== Sender: bitcoindev@googlegroups.com X-Forwarded-Encrypted: i=1; AJvYcCUQjp2X2BpKxWPOrex5pGfgFJxaqkvA4YjGZnI2tEAUtpPg90oU1LLJxaW0dEpeNVyGjyxSA9zSVwP42tWwjIDln8JoO68= X-Gm-Message-State: AOJu0YzSWlXFudX7ZyRxZ4ESvk6M8/bsSfmasOKRE81Fln8L4BCurr6I dGASxGgPZaveIzUIRoYuwkcBpJbXiWmWrKCEUW0cBXtfx56t9vYO X-Google-Smtp-Source: AGHT+IFAh1UmjQYrqML8LjG9T57kWsgAJ1VbmeN6st8+jIbMjAg6Xda4ilfZQNd1Q/0cr1MwHxpA+A== X-Received: by 2002:a25:8402:0:b0:de0:de50:d6d4 with SMTP id u2-20020a258402000000b00de0de50d6d4mr4502473ybk.8.1714781051640; Fri, 03 May 2024 17:04:11 -0700 (PDT) X-BeenThere: bitcoindev@googlegroups.com Received: by 2002:a25:dc44:0:b0:de6:720:76c2 with SMTP id 3f1490d57ef6-de8b54a8326ls859827276.1.-pod-prod-07-us; Fri, 03 May 2024 17:04:10 -0700 (PDT) X-Received: by 2002:a05:6902:1004:b0:de4:7be7:1c2d with SMTP id w4-20020a056902100400b00de47be71c2dmr1342748ybt.11.1714781049902; Fri, 03 May 2024 17:04:09 -0700 (PDT) Received: by 2002:a05:690c:f16:b0:61a:e84a:c592 with SMTP id 00721157ae682-61dfb44c61dms7b3; Thu, 2 May 2024 03:29:44 -0700 (PDT) X-Received: by 2002:a05:6902:2b0e:b0:dcb:e4a2:1ab1 with SMTP id fi14-20020a0569022b0e00b00dcbe4a21ab1mr391178ybb.11.1714645782986; Thu, 02 May 2024 03:29:42 -0700 (PDT) Date: Thu, 2 May 2024 03:29:42 -0700 (PDT) From: Ali Sherief To: Bitcoin Development Mailing List Message-Id: <987e5090-63c3-4db3-bcd2-03e74a17b226n@googlegroups.com> In-Reply-To: References: Subject: Re: [bitcoindev] Test cases for signing legacy inputs in transactions MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="----=_Part_51289_1618634159.1714645782614" X-Original-Sender: ali@notatether.com Precedence: list Mailing-list: list bitcoindev@googlegroups.com; contact bitcoindev+owners@googlegroups.com List-ID: X-Google-Group-Id: 786775582512 List-Post: , List-Help: , List-Archive: , List-Unsubscribe: , X-Spam-Score: -0.7 (/) ------=_Part_51289_1618634159.1714645782614 Content-Type: multipart/alternative; boundary="----=_Part_51290_857222038.1714645782614" ------=_Part_51290_857222038.1714645782614 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable I don't think that its a good idea to rely on my own generated Core=20 transactions, though. Not because I don't trust Core as having a correct=20 transaction implementation, but because the transactions are still=20 ultimately generated by me so that they are not covering all the edge cases= . -Ali On Tuesday, April 30, 2024 at 1:32:03=E2=80=AFPM UTC Edil Guimar=C3=A3es de= Medeiros=20 wrote: > Well, you might use core itself to create a bunch of private keys and=20 > legacy transactions. > That will imply you trust core as a golden model for your software, but= =20 > since almost everyone in the network assumes to be bug compatible with=20 > 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 =20 > escreveu: > >> Hi all, >> >> I am aware that there are tons of raw transactions that can be used for= =20 >> testing Segwit transaction constructors in BIP143 and also in the tests/= =20 >> folder of the codebase somewhere. >> >> However, I am having a hard time finding reproducible legacy=20 >> transactions. This is usually for one of two reasons: >> >> 1) Important information for debugging the transaction signing such as= =20 >> the preimage or private key is missing. >> 2) The transactions were using OpenSSL to create the signatures, which= =20 >> results in them being non-deterministic and useless for tests. As oppose= d=20 >> to using libsecp256k1. >> >> So I am just wondering if anybody knows if there is a place where I can= =20 >> find a bunch of raw legacy transactions, together with private keys, to= =20 >> test my software with. >> >> -Ali >> >> --=20 >> You received this message because you are subscribed to the Google Group= s=20 >> "Bitcoin Development Mailing List" group. >> To unsubscribe from this group and stop receiving emails from it, send a= n=20 >> email to bitcoindev+...@googlegroups.com. >> To view this discussion on the web visit=20 >> https://groups.google.com/d/msgid/bitcoindev/b165f262-e733-46c1-a6f3-328= fc8b13288n%40googlegroups.com=20 >> >> . >> > > > --=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/987e5090-63c3-4db3-bcd2-03e74a17b226n%40googlegroups.com. ------=_Part_51290_857222038.1714645782614 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable I don't think that its a good idea to rely on my own generated Core transac= tions, though. Not because I don't trust Core as having a correct transacti= on implementation, but because the transactions are still ultimately genera= ted by me so that they are not covering all the edge cases.

-Ali=

On Tuesday, April 30, 2024 at 1:32:03=E2=80=AFPM UTC Edil Guimar=C3=A3es= de Medeiros wrote:
Well, you might use core itse= lf to create a bunch of private keys and legacy transactions.
Tha= t 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 do= n't see a problem.

Or am I missing something a= nd being too simplistic?

Em ter., 30 de abr. de 2024 =C3=A0s 09:01, Ali Sherief <= a...@notatether.com> escr= eveu:
Hi all,

I = am aware that there are tons of raw transactions that can be used for testi= ng 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 debu= gging the transaction signing such as the preimage or private key is missin= g.
2) The transactions were using OpenSSL to create the signature= s, which results in them being non-deterministic and useless for tests. As = opposed to using libsecp256k1.

So I am just wondering if anybody kno= ws 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 &= quot;Bitcoin Development Mailing List" group.
To unsubscribe from this group and stop receiving emails from it, send an e= mail to bitcoindev+...@googlegro= ups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/bitcoindev/b165f262-e733-46c1-a6f3-= 328fc8b13288n%40googlegroups.com.


--
Edil

--
You received this message because you are subscribed to the Google Groups &= quot;Bitcoin Development Mailing List" group.
To unsubscribe from this group and stop receiving emails from it, send an e= mail to bitcoind= ev+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msg= id/bitcoindev/987e5090-63c3-4db3-bcd2-03e74a17b226n%40googlegroups.com.=
------=_Part_51290_857222038.1714645782614-- ------=_Part_51289_1618634159.1714645782614--