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 ) 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 ; 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 To: Bitcoin Development Mailing List Message-Id: <51e7808a-45a6-4813-8a42-92c0489fd994n@googlegroups.com> In-Reply-To: References: <9FAA7EEC-BD22-491E-B21B-732AEA15F556@sprovoost.nl> <7c28f8e9-d221-4633-8b71-53b4db07fa78@schildbach.de> 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: X-Google-Group-Id: 786775582512 List-Post: , List-Help: , List-Archive: , List-Unsubscribe: , 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 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.

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.

= So, if you create some app, which will use significantly different exchange= rate, then it will be quickly abused.

poniedzia=C5=82ek, 31 marca 2025 o= =C2=A022:41:55 UTC+2 Melvin Carvalho napisa=C5=82(a):
=

p=C3=A1 14. 3. 2025 v=C2=A014:01 odes=C3=ADlatel 'Andreas Schildbac= h' via Bitcoin Development Mailing List <bitco...@googlegroups.com> napsal:
Hi Sjors,

thanks for asking.

Bitcoinj has just started to implement testnet4, but it's not finished =
yet. And the next version 0.18 will probably not be released within 12
months, maybe longer.

By the way, testnet3 works great for us (for testing). I consider block storms a feature, because it tests our code in rough conditions. We had planned to support both testnets in the forseeable future.

https://gith= ub.com/bitcoinj/bitcoinj/

Then, there is btc-rpc-explorer, a self-hostable block explorer. It
doesn't yet support testnet4. I'm not affiliated to it, I'm jus= t a user.

https://github.com/janoside/btc-rpc-explorer

Main issue w= ith testnet3 is getting coins for developers to use it, especially with hig= h fees.

A neat idea might be to make an app to swa= p between testnet3 and testnet4 coins.=C2=A0 Or even an AMM.

=
If there's a decent amount of interest in this, I could give= it a go.
=C2=A0


Cheers,
Andreas


On 14/03/2025 09.52, Sjors Provoost wrote:
> Dear list,
>
> Testnet 4 was proposed last year in BIP94 [0] and is supported by Bitc= oin Core since v28.
>
> 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].
>
> The network itself can't be deleted, so anyone willing to maintain= node software themselves can keep using testnet3 until the end of time. >
> 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.
>
> 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]
>
> 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.
>
> 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.
>
> 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.
>
> - Sjors
>
> [0] https://github.com/bitcoin/bi= ps/blob/master/bip-0094.mediawiki
> [1] https://bitcoincore.org/en/lifecycle/#m= aintenance-period
> [2] https://github.com/bitcoin/bips/blob/master/bip-0325.mediawiki#specificati= on
> [3] https://github.com/bitcoin/bitcoin/issues/31975
>

--
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.

--
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 visit https://groups.google.com/d/msgid/bitcoind= ev/51e7808a-45a6-4813-8a42-92c0489fd994n%40googlegroups.com.
------=_Part_23025_452505784.1743486983666-- ------=_Part_23024_1964751891.1743486983666--