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
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388
389
390
391
392
393
394
395
396
397
398
399
400
401
402
403
404
|
Delivery-date: Tue, 01 Apr 2025 01:51:45 -0700
Received: from mail-yw1-f192.google.com ([209.85.128.192])
by mail.fairlystable.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256
(Exim 4.94.2)
(envelope-from <bitcoindev+bncBCY3VBMZVAMRBFWSV27QMGQELUYC3XA@googlegroups.com>)
id 1tzXLU-0000XO-Hc
for bitcoindev@gnusha.org; Tue, 01 Apr 2025 01:51:45 -0700
Received: by mail-yw1-f192.google.com with SMTP id 00721157ae682-702537c13fcsf36456427b3.0
for <bitcoindev@gnusha.org>; Tue, 01 Apr 2025 01:51:44 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
d=googlegroups.com; s=20230601; t=1743497498; x=1744102298; 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=5uBTRvqiWIPkIuSjCWFm/mQtY+Mc9qXlDkecF2u7kGA=;
b=PzRve+LslJ/ghEdB0F4R85I46OEztfkrxRCm0ymA0AHBQzgVh/JXzBf0vyC7n4pTtp
cGp9jTuADOmooZXRvwV3LuGJwQrK9Wd7rzPGPehY4b+DEf/Ck9OLA4NiJsYplEAOBJrs
ttdAZdOd6DqOD41DyWtboqSGt2lhMyfYy9V5I0+mRvRTMeN6ZMClDSGRZnLBobHRxxJg
1/Qz13fuYanlKH3dcTC+CZFx89rjaW05BWhrpNeiSlvwfGpk1TCVRuXSTlrw3sOWR0yu
NiEcW6qXTh2H/epnJoPzG+jb0Bq4IiJs2ZxwDBGE+GoDB8UG2qur4EMcGALXIkk/9LN/
sn9g==
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
d=gmail.com; s=20230601; t=1743497498; x=1744102298; 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:from:to:cc
:subject:date:message-id:reply-to;
bh=5uBTRvqiWIPkIuSjCWFm/mQtY+Mc9qXlDkecF2u7kGA=;
b=E4yEeWQyUIM9olsMPN6CiH41bq8QJXFa7pKWhupW4e7L45RtTL9i71lm+G+2PPm5ss
7F2mW4X3RYAQi08C5Xg/ocr8tyiR594xQ5A0DMudmbiF6H/KPKFF8MiEwzssOFVA2DUb
BcsQn5TONwk9Cpauqb5Izozfbvf0XwUHfa0PTDQv1akz2iZW+yTgHimDSK51hpUialnY
HYItXrkD87w8xYb5MX2uVbx7riFR81pNdapT/6WBcfdctGVb570v7nxXurLluHJAAp8G
rpVMogdK90YBO1eQP53KrLpH4K5hfdKFOfsy6ZhRcG2aDhrfClj1AXIaAQyclJWJ7Id+
G2gA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
d=1e100.net; s=20230601; t=1743497498; x=1744102298;
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=5uBTRvqiWIPkIuSjCWFm/mQtY+Mc9qXlDkecF2u7kGA=;
b=Onr5YyyCKXSwLZOhhsMMAIiDJu/R/Bm00Hqv2olJK+VIu6K6KG0u+Kao0uUbkYlzVJ
i+8kbp6IgfTg0F/yBkzJ3ASBMbBWvmptZYML3GErTPenecLKkvq+PeNfQxEhWxyxM9MN
kzb72T0gDrRZCFxxrYq6oQtMCPxur/C4CJZKnP9Cz7TPZ6uidVP51jgu3DJRD1BS1a3R
/WNysoA/6ftLZu9VjE807c27z4fbk+ZBp9tK8ouYofREgF3b42gVqkud6wxM4OcyZ0Ve
RXPWEtxR+qCGBIQ+CM0dFS2yVpKxGjrAT8GSS/67fLgwjNTmHXD6uHaG1TAIAb13Vuav
jO1Q==
Sender: bitcoindev@googlegroups.com
X-Forwarded-Encrypted: i=1; AJvYcCUX7M8JazF0RzZ56KVNaz7gshhu75IykyTi90AyC6woJq9vV0qQwci2lCGbOUVuZ3nJoA35Kt2HCmoh@gnusha.org
X-Gm-Message-State: AOJu0YxFotvz7H8WvxQCPeMHuDRyd04mwY9airIyXoz27bFpoD8d8i/6
xuFnd6s33XtBDqYKEa3Uw6kH2tqC/AUnP3EWoyjYYsh20fbuIUzN
X-Google-Smtp-Source: AGHT+IGxIlAS7nsKrrwQvp97BwilQHrmXzFO1bA/xyhyA82MRWP5vVEQOLSpQHhf391xu7JD392WHg==
X-Received: by 2002:a05:6902:2788:b0:e63:326a:3acb with SMTP id 3f1490d57ef6-e6b83a96291mr14839475276.40.1743497498386;
Tue, 01 Apr 2025 01:51:38 -0700 (PDT)
X-BeenThere: bitcoindev@googlegroups.com; h=ARLLPALXNw2hY7b48PqTPD4rQyqqEV9QHsDc/2IhBHUd6GxNbQ==
Received: by 2002:a25:701:0:b0:e5d:bf60:53db with SMTP id 3f1490d57ef6-e6942b9bba7ls1884462276.0.-pod-prod-04-us;
Tue, 01 Apr 2025 01:51:34 -0700 (PDT)
X-Received: by 2002:a05:690c:3811:b0:6fb:91a9:94d9 with SMTP id 00721157ae682-702570d55a3mr168694017b3.2.1743497494473;
Tue, 01 Apr 2025 01:51:34 -0700 (PDT)
Received: by 2002:a05:690c:9a05:b0:6ef:590d:3213 with SMTP id 00721157ae682-70210946374ms7b3;
Mon, 31 Mar 2025 22:56:25 -0700 (PDT)
X-Received: by 2002:a05:690c:4c0c:b0:6f9:a53b:2a84 with SMTP id 00721157ae682-7025730342amr161931977b3.36.1743486984155;
Mon, 31 Mar 2025 22:56:24 -0700 (PDT)
Date: Mon, 31 Mar 2025 22:56:23 -0700 (PDT)
From: Garlo Nicon <garlonicon@gmail.com>
To: Bitcoin Development Mailing List <bitcoindev@googlegroups.com>
Message-Id: <51e7808a-45a6-4813-8a42-92c0489fd994n@googlegroups.com>
In-Reply-To: <CAKaEYhLuQDMKXaVhbQ2BrwHdHg7zPBiO-NgH6GhACufoqR2T4A@mail.gmail.com>
References: <9FAA7EEC-BD22-491E-B21B-732AEA15F556@sprovoost.nl>
<7c28f8e9-d221-4633-8b71-53b4db07fa78@schildbach.de>
<CAKaEYhLuQDMKXaVhbQ2BrwHdHg7zPBiO-NgH6GhACufoqR2T4A@mail.gmail.com>
Subject: Re: [bitcoindev] Does anyone still need testnet3?
MIME-Version: 1.0
Content-Type: multipart/mixed;
boundary="----=_Part_23024_1964751891.1743486983666"
X-Original-Sender: garlonicon@gmail.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.5 (/)
------=_Part_23024_1964751891.1743486983666
Content-Type: multipart/alternative;
boundary="----=_Part_23025_452505784.1743486983666"
------=_Part_23025_452505784.1743486983666
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
> A neat idea might be to make an app to swap between testnet3 and testnet4=
=20
coins. Or even an AMM.
With 1:1 ratio? Because now, on centralized exchanges, you have 300=20
satoshis per 1 tBTC3, and 25 satoshis per 1 tBTC4. Which means, that 1=20
tBTC3 would be worth 12 tBTC4.
So, if you create some app, which will use significantly different exchange=
=20
rate, then it will be quickly abused.
poniedzia=C5=82ek, 31 marca 2025 o 22:41:55 UTC+2 Melvin Carvalho napisa=C5=
=82(a):
>
>
> p=C3=A1 14. 3. 2025 v 14:01 odes=C3=ADlatel 'Andreas Schildbach' via Bitc=
oin=20
> Development Mailing List <bitco...@googlegroups.com> napsal:
>
>> Hi Sjors,
>>
>> thanks for asking.
>>
>> Bitcoinj has just started to implement testnet4, but it's not finished=
=20
>> yet. And the next version 0.18 will probably not be released within 12=
=20
>> months, maybe longer.
>>
>> By the way, testnet3 works great for us (for testing). I consider block=
=20
>> storms a feature, because it tests our code in rough conditions. We had=
=20
>> planned to support both testnets in the forseeable future.
>>
>> https://github.com/bitcoinj/bitcoinj/
>>
>> Then, there is btc-rpc-explorer, a self-hostable block explorer. It=20
>> doesn't yet support testnet4. I'm not affiliated to it, I'm just a user.
>>
>> https://github.com/janoside/btc-rpc-explorer
>
>
> Main issue with testnet3 is getting coins for developers to use it,=20
> especially with high fees.
>
> A neat idea might be to make an app to swap between testnet3 and testnet4=
=20
> coins. Or even an AMM.
>
> If there's a decent amount of interest in this, I could give it a go.
> =20
>
>>
>>
>> Cheers,
>> Andreas
>>
>>
>> On 14/03/2025 09.52, Sjors Provoost wrote:
>> > Dear list,
>> >=20
>> > Testnet 4 was proposed last year in BIP94 [0] and is supported by=20
>> Bitcoin Core since v28.
>> >=20
>> > To make Bitcoin Core easier to maintain we would like to drop support=
=20
>> for Testnet3 in a future release. This will happen no earlier than v30 t=
his=20
>> fall. The upcoming v29 release still supports it, and will throughout it=
s=20
>> maintenance period [1].
>> >=20
>> > The network itself can't be deleted, so anyone willing to maintain nod=
e=20
>> software themselves can keep using testnet3 until the end of time.
>> >=20
>> > One of the motivations for introducing testnet4 was that testnet3=20
>> became increasing impractical to use due to block storms. So perhaps=20
>> everyone already moved on to using testnet4 or a signet.
>> >=20
>> > As an aside, it's possible to create a pure proof-of-work=20
>> permissionless signet without any signatures, by setting the challenge t=
o=20
>> OP_TRUE. [2]
>> >=20
>> > However, if anyone is still using testnet3 and needs more time to move=
=20
>> away from it, please let us know. E.g. as a reply to the list or a comme=
nt=20
>> on the Github issue [3]. This could include libraries, staging=20
>> environments, testnet wallets, etc.
>> >=20
>> > Although the v29 maintenance window will last for a few years, it's=20
>> also important to know if dropping testnet3 would prevent you from=20
>> upgrading to the next major node version. In other words, if migrating a=
way=20
>> from testnet3 would take you longer than all of 2025.
>> >=20
>> > Although "I don't feel like it" isn't a great technical argument, it's=
=20
>> still useful to know what to expect and perhaps others can help.
>> >=20
>> > - Sjors
>> >=20
>> > [0] https://github.com/bitcoin/bips/blob/master/bip-0094.mediawiki
>> > [1] https://bitcoincore.org/en/lifecycle/#maintenance-period
>> > [2]=20
>> https://github.com/bitcoin/bips/blob/master/bip-0325.mediawiki#specifica=
tion
>> > [3] https://github.com/bitcoin/bitcoin/issues/31975
>> >=20
>>
>> --=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 visit=20
>> https://groups.google.com/d/msgid/bitcoindev/7c28f8e9-d221-4633-8b71-53b=
4db07fa78%40schildbach.de
>> .
>>
>
--=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 visit https://groups.google.com/d/msgid/bitcoindev/=
51e7808a-45a6-4813-8a42-92c0489fd994n%40googlegroups.com.
------=_Part_23025_452505784.1743486983666
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
> A neat idea might be to make an app to swap between testnet3 and testn=
et4 coins. =C2=A0Or even an AMM.<br /><br />With 1:1 ratio? Because now, on=
centralized exchanges, you have 300 satoshis per 1 tBTC3, and 25 satoshis =
per 1 tBTC4. Which means, that 1 tBTC3 would be worth 12 tBTC4.<br /><br />=
So, if you create some app, which will use significantly different exchange=
rate, then it will be quickly abused.<br /><br /><div class=3D"gmail_quote=
"><div dir=3D"auto" class=3D"gmail_attr">poniedzia=C5=82ek, 31 marca 2025 o=
=C2=A022:41:55 UTC+2 Melvin Carvalho napisa=C5=82(a):<br/></div><blockquote=
class=3D"gmail_quote" style=3D"margin: 0 0 0 0.8ex; border-left: 1px solid=
rgb(204, 204, 204); padding-left: 1ex;"><div dir=3D"ltr"><div dir=3D"ltr">=
<br></div><br><div class=3D"gmail_quote"><div dir=3D"ltr" class=3D"gmail_at=
tr">p=C3=A1 14. 3. 2025 v=C2=A014:01 odes=C3=ADlatel 'Andreas Schildbac=
h' via Bitcoin Development Mailing List <<a href data-email-masked r=
el=3D"nofollow">bitco...@googlegroups.com</a>> napsal:<br></div></div></=
div><div dir=3D"ltr"><div class=3D"gmail_quote"><blockquote class=3D"gmail_=
quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,=
204);padding-left:1ex">Hi Sjors,<br>
<br>
thanks for asking.<br>
<br>
Bitcoinj has just started to implement testnet4, but it's not finished =
<br>
yet. And the next version 0.18 will probably not be released within 12 <br>
months, maybe longer.<br>
<br>
By the way, testnet3 works great for us (for testing). I consider block <br=
>
storms a feature, because it tests our code in rough conditions. We had <br=
>
planned to support both testnets in the forseeable future.<br>
<br>
<a href=3D"https://github.com/bitcoinj/bitcoinj/" rel=3D"noreferrer nofollo=
w" target=3D"_blank" data-saferedirecturl=3D"https://www.google.com/url?hl=
=3Dpl&q=3Dhttps://github.com/bitcoinj/bitcoinj/&source=3Dgmail&=
ust=3D1743573352196000&usg=3DAOvVaw1Pszt2fWUvatnHKypU50R6">https://gith=
ub.com/bitcoinj/bitcoinj/</a><br>
<br>
Then, there is btc-rpc-explorer, a self-hostable block explorer. It <br>
doesn't yet support testnet4. I'm not affiliated to it, I'm jus=
t a user.<br>
<br>
<a href=3D"https://github.com/janoside/btc-rpc-explorer" rel=3D"noreferrer =
nofollow" target=3D"_blank" data-saferedirecturl=3D"https://www.google.com/=
url?hl=3Dpl&q=3Dhttps://github.com/janoside/btc-rpc-explorer&source=
=3Dgmail&ust=3D1743573352196000&usg=3DAOvVaw0xymHRouQtZm4QJTXdETyK"=
>https://github.com/janoside/btc-rpc-explorer</a></blockquote><div><br></di=
v></div></div><div dir=3D"ltr"><div class=3D"gmail_quote"><div>Main issue w=
ith testnet3 is getting coins for developers to use it, especially with hig=
h fees.</div><div><br></div><div>A neat idea might be to make an app to swa=
p between testnet3 and testnet4 coins.=C2=A0 Or even an AMM.</div><div><br>=
</div><div>If there's a decent amount of interest in this, I could give=
it a go.</div><div>=C2=A0</div><blockquote class=3D"gmail_quote" style=3D"=
margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-lef=
t:1ex"></blockquote></div></div><div dir=3D"ltr"><div class=3D"gmail_quote"=
><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border=
-left:1px solid rgb(204,204,204);padding-left:1ex"><br>
<br>
Cheers,<br>
Andreas<br>
<br>
<br>
On 14/03/2025 09.52, Sjors Provoost wrote:<br>
> Dear list,<br>
> <br>
> Testnet 4 was proposed last year in BIP94 [0] and is supported by Bitc=
oin Core since v28.<br>
> <br>
> To make Bitcoin Core easier to maintain we would like to drop support =
for Testnet3 in a future release. This will happen no earlier than v30 this=
fall. The upcoming v29 release still supports it, and will throughout its =
maintenance period [1].<br>
> <br>
> The network itself can't be deleted, so anyone willing to maintain=
node software themselves can keep using testnet3 until the end of time.<br=
>
> <br>
> One of the motivations for introducing testnet4 was that testnet3 beca=
me increasing impractical to use due to block storms. So perhaps everyone a=
lready moved on to using testnet4 or a signet.<br>
> <br>
> As an aside, it's possible to create a pure proof-of-work permissi=
onless signet without any signatures, by setting the challenge to OP_TRUE. =
[2]<br>
> <br>
> However, if anyone is still using testnet3 and needs more time to move=
away from it, please let us know. E.g. as a reply to the list or a comment=
on the Github issue [3]. This could include libraries, staging environment=
s, testnet wallets, etc.<br>
> <br>
> Although the v29 maintenance window will last for a few years, it'=
s also important to know if dropping testnet3 would prevent you from upgrad=
ing to the next major node version. In other words, if migrating away from =
testnet3 would take you longer than all of 2025.<br>
> <br>
> Although "I don't feel like it" isn't a great techni=
cal argument, it's still useful to know what to expect and perhaps othe=
rs can help.<br>
> <br>
> - Sjors<br>
> <br>
> [0] <a href=3D"https://github.com/bitcoin/bips/blob/master/bip-0094.me=
diawiki" rel=3D"noreferrer nofollow" target=3D"_blank" data-saferedirecturl=
=3D"https://www.google.com/url?hl=3Dpl&q=3Dhttps://github.com/bitcoin/b=
ips/blob/master/bip-0094.mediawiki&source=3Dgmail&ust=3D17435733521=
96000&usg=3DAOvVaw0f8V8T2MHGVl7RteTfLqEJ">https://github.com/bitcoin/bi=
ps/blob/master/bip-0094.mediawiki</a><br>
> [1] <a href=3D"https://bitcoincore.org/en/lifecycle/#maintenance-perio=
d" rel=3D"noreferrer nofollow" target=3D"_blank" data-saferedirecturl=3D"ht=
tps://www.google.com/url?hl=3Dpl&q=3Dhttps://bitcoincore.org/en/lifecyc=
le/%23maintenance-period&source=3Dgmail&ust=3D1743573352196000&=
usg=3DAOvVaw0LbUp0DideKBbdIVqldNwQ">https://bitcoincore.org/en/lifecycle/#m=
aintenance-period</a><br>
> [2] <a href=3D"https://github.com/bitcoin/bips/blob/master/bip-0325.me=
diawiki#specification" rel=3D"noreferrer nofollow" target=3D"_blank" data-s=
aferedirecturl=3D"https://www.google.com/url?hl=3Dpl&q=3Dhttps://github=
.com/bitcoin/bips/blob/master/bip-0325.mediawiki%23specification&source=
=3Dgmail&ust=3D1743573352196000&usg=3DAOvVaw3O9lol259JQHkbS1M7n5Yj"=
>https://github.com/bitcoin/bips/blob/master/bip-0325.mediawiki#specificati=
on</a><br>
> [3] <a href=3D"https://github.com/bitcoin/bitcoin/issues/31975" rel=3D=
"noreferrer nofollow" target=3D"_blank" data-saferedirecturl=3D"https://www=
.google.com/url?hl=3Dpl&q=3Dhttps://github.com/bitcoin/bitcoin/issues/3=
1975&source=3Dgmail&ust=3D1743573352196000&usg=3DAOvVaw3-SARRp4=
Yz0e4oz1tKqRuu">https://github.com/bitcoin/bitcoin/issues/31975</a><br>
> <br>
<br></blockquote></div></div><div dir=3D"ltr"><div class=3D"gmail_quote"><b=
lockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-le=
ft:1px solid rgb(204,204,204);padding-left:1ex">
-- <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 data-email-masked rel=3D"nofollow">bitcoindev+...@googlegro=
ups.com</a>.<br></blockquote></div></div><div dir=3D"ltr"><div class=3D"gma=
il_quote"><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8=
ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
To view this discussion visit <a href=3D"https://groups.google.com/d/msgid/=
bitcoindev/7c28f8e9-d221-4633-8b71-53b4db07fa78%40schildbach.de" rel=3D"nor=
eferrer nofollow" target=3D"_blank" data-saferedirecturl=3D"https://www.goo=
gle.com/url?hl=3Dpl&q=3Dhttps://groups.google.com/d/msgid/bitcoindev/7c=
28f8e9-d221-4633-8b71-53b4db07fa78%2540schildbach.de&source=3Dgmail&=
;ust=3D1743573352196000&usg=3DAOvVaw11dXUyiDb9Jj6Av-9HQdP-">https://gro=
ups.google.com/d/msgid/bitcoindev/7c28f8e9-d221-4633-8b71-53b4db07fa78%40sc=
hildbach.de</a>.<br>
</blockquote></div></div>
</blockquote></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 visit <a href=3D"https://groups.google.com/d/msgid/=
bitcoindev/51e7808a-45a6-4813-8a42-92c0489fd994n%40googlegroups.com?utm_med=
ium=3Demail&utm_source=3Dfooter">https://groups.google.com/d/msgid/bitcoind=
ev/51e7808a-45a6-4813-8a42-92c0489fd994n%40googlegroups.com</a>.<br />
------=_Part_23025_452505784.1743486983666--
------=_Part_23024_1964751891.1743486983666--
|