1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
|
Delivery-date: Tue, 30 Apr 2024 05:01:46 -0700
Received: from mail-yb1-f191.google.com ([209.85.219.191])
by mail.fairlystable.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256
(Exim 4.94.2)
(envelope-from <bitcoindev+bncBCQ6HM7U3YGRBIN3YOYQMGQEGC6EEIY@googlegroups.com>)
id 1s1mB7-0005Id-KS
for bitcoindev@gnusha.org; Tue, 30 Apr 2024 05:01:45 -0700
Received: by mail-yb1-f191.google.com with SMTP id 3f1490d57ef6-dcc0bcf9256sf9169014276.3
for <bitcoindev@gnusha.org>; Tue, 30 Apr 2024 05:01:45 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
d=googlegroups.com; s=20230601; t=1714478499; x=1715083299; 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:message-id:to:from:date:sender:from:to:cc:subject:date
:message-id:reply-to;
bh=rcpx4otvQDUQ+ScTRlWHNZ5GIjtEz4n4/c4V8MZnYJk=;
b=WFH5/QUBzame/9PZprr34W8e1bsN0HDmShfQ42XHv1CC6MhdvJiaHzrop37hTekhx+
wmrX+0sxpfF/Zsw8ofGSJw6Ze8pvw0zAiMLmCkRxllz7qQWMHn68vQmnzpP5ncMlleX2
XiHnkciEDPNTeXtV3HgYdsxMHcz5zpSVWfBwB+YyN2BCWFBpdv+sEVGV3eJLQ5VexT4H
Ew3VI5gJfms8ylXvrwwPVtDYPYBAxmUxw6TJIBMt+S+vOi9lc3GUN/voOzwc3x+0nkxQ
gAWFbneLLKdVbDDFsbUiSUWrcWrv5dzyR+io47rBcbnz/ldTmFDDIVz3Pp6t9eFD96Dv
BwJQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
d=1e100.net; s=20230601; t=1714478499; x=1715083299;
h=list-unsubscribe:list-subscribe:list-archive:list-help:list-post
:list-id:mailing-list:precedence:x-original-sender:mime-version
:subject:message-id:to:from:date:x-beenthere:x-gm-message-state
:sender:from:to:cc:subject:date:message-id:reply-to;
bh=rcpx4otvQDUQ+ScTRlWHNZ5GIjtEz4n4/c4V8MZnYJk=;
b=ZEoqv9mgfWm/79JeqjrviQfwfJDDTFwnC4nIHvBrtyW26xNTy2vF4xF2w8DTg+czHh
vchHzMHmjyfQD1GKtwfOO5gP8POiUAcIh6PBmM8/fimu8k7VTyype6Mf/UKJ6Ue5jnhH
ZKjANR9vUjkW0YnFt8Hvzc4VjeYtWKbMXG9iVW3UpMKBOBMibKW60tv9QkZFgEnWYVx1
+BE1+upsbi0+WOWJfdMcbSpocrxi2SUoLG1L/sFhN2A3iYsnalfxI4pxkccPnro/JbIh
SgNS2on0Vgr8bTUqFf4hqz4vi8Y0ZDtK15Rb2aZPpXSuDKDP1C8PGsId5s9iwieg6GLc
fLLg==
Sender: bitcoindev@googlegroups.com
X-Forwarded-Encrypted: i=1; AJvYcCVSYCy9bpPcrOS2fT1zAwa0vadjxEtGRSYAdmVPli/S77H9v4Q8VS72eb7cbwGmoW7USrcM0Q2bgGHDjeylBTDd1vXc1vA=
X-Gm-Message-State: AOJu0Yz0TsgVUnMlNL9pPVvVR+HqMTW16YLErNRp85UnU0Dis1jark2O
ugyHpdCJIqZdq9+AY4Ywmztbf3vqbndFoF3X6spAR/FH8p3H3uSU
X-Google-Smtp-Source: AGHT+IFWUXA3Ufuv8Xv4xG5AbCwCyURHksTb9zOdVA1u9eFLl4xqWxCtrAAZ6JvJVMF0ylk0T86Luw==
X-Received: by 2002:a25:b327:0:b0:db9:9134:bb28 with SMTP id l39-20020a25b327000000b00db99134bb28mr2717429ybj.4.1714478499211;
Tue, 30 Apr 2024 05:01:39 -0700 (PDT)
X-BeenThere: bitcoindev@googlegroups.com
Received: by 2002:a25:2cc:0:b0:de5:9f2c:c194 with SMTP id 3f1490d57ef6-de59f2cc380ls360016276.1.-pod-prod-05-us;
Tue, 30 Apr 2024 05:01:37 -0700 (PDT)
X-Received: by 2002:a0d:cc8e:0:b0:61b:ec62:e713 with SMTP id o136-20020a0dcc8e000000b0061bec62e713mr321029ywd.10.1714478497328;
Tue, 30 Apr 2024 05:01:37 -0700 (PDT)
Received: by 2002:a05:690c:f89:b0:611:2a20:d0cc with SMTP id 00721157ae682-61ba91b2cd9ms7b3;
Tue, 30 Apr 2024 04:43:50 -0700 (PDT)
X-Received: by 2002:a05:6902:110e:b0:de4:c54c:6754 with SMTP id o14-20020a056902110e00b00de4c54c6754mr4057450ybu.3.1714477429501;
Tue, 30 Apr 2024 04:43:49 -0700 (PDT)
Date: Tue, 30 Apr 2024 04:43:49 -0700 (PDT)
From: Ali Sherief <ali@notatether.com>
To: Bitcoin Development Mailing List <bitcoindev@googlegroups.com>
Message-Id: <b165f262-e733-46c1-a6f3-328fc8b13288n@googlegroups.com>
Subject: [bitcoindev] Test cases for signing legacy inputs in transactions
MIME-Version: 1.0
Content-Type: multipart/mixed;
boundary="----=_Part_41394_1124310358.1714477429167"
X-Original-Sender: ali@notatether.com
Precedence: list
Mailing-list: list bitcoindev@googlegroups.com; contact bitcoindev+owners@googlegroups.com
List-ID: <bitcoindev.googlegroups.com>
X-Google-Group-Id: 786775582512
List-Post: <https://groups.google.com/group/bitcoindev/post>, <mailto:bitcoindev@googlegroups.com>
List-Help: <https://groups.google.com/support/>, <mailto:bitcoindev+help@googlegroups.com>
List-Archive: <https://groups.google.com/group/bitcoindev
List-Subscribe: <https://groups.google.com/group/bitcoindev/subscribe>, <mailto:bitcoindev+subscribe@googlegroups.com>
List-Unsubscribe: <mailto:googlegroups-manage+786775582512+unsubscribe@googlegroups.com>,
<https://groups.google.com/group/bitcoindev/subscribe>
X-Spam-Score: -0.7 (/)
------=_Part_41394_1124310358.1714477429167
Content-Type: multipart/alternative;
boundary="----=_Part_41395_1519470858.1714477429167"
------=_Part_41395_1519470858.1714477429167
Content-Type: text/plain; charset="UTF-8"
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.
------=_Part_41395_1519470858.1714477429167
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Hi all,<div><br /></div><div>I am aware that there are tons of raw transact=
ions that can be used for testing Segwit transaction constructors in BIP143=
and also in the tests/ folder of the codebase somewhere.</div><div><br /><=
/div><div>However, I am having a hard time finding reproducible legacy tran=
sactions. This is usually for one of two reasons:</div><div><br /></div><di=
v>1) Important information for debugging the transaction signing such as th=
e preimage or private key is missing.</div><div>2) The transactions were us=
ing OpenSSL to create the signatures, which results in them being non-deter=
ministic and useless for tests. As opposed to using libsecp256k1.<br /><br =
/>So I am just wondering if anybody knows if there is a place where I can f=
ind a bunch of raw legacy transactions, together with private keys, to test=
my software with.<br /><br />-Ali</div>
<p></p>
-- <br />
You received this message because you are subscribed to the Google Groups &=
quot;Bitcoin Development Mailing List" group.<br />
To unsubscribe from this group and stop receiving emails from it, send an e=
mail to <a href=3D"mailto:bitcoindev+unsubscribe@googlegroups.com">bitcoind=
ev+unsubscribe@googlegroups.com</a>.<br />
To view this discussion on the web visit <a href=3D"https://groups.google.c=
om/d/msgid/bitcoindev/b165f262-e733-46c1-a6f3-328fc8b13288n%40googlegroups.=
com?utm_medium=3Demail&utm_source=3Dfooter">https://groups.google.com/d/msg=
id/bitcoindev/b165f262-e733-46c1-a6f3-328fc8b13288n%40googlegroups.com</a>.=
<br />
------=_Part_41395_1519470858.1714477429167--
------=_Part_41394_1124310358.1714477429167--
|
