Delivery-date: Mon, 01 Apr 2024 13:03:31 -0700 Received: from mail-yb1-f192.google.com ([209.85.219.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 1rrNsQ-0004Ev-QF for bitcoindev@gnusha.org; Mon, 01 Apr 2024 13:03:31 -0700 Received: by mail-yb1-f192.google.com with SMTP id 3f1490d57ef6-dc6b26783b4sf4879118276.0 for ; Mon, 01 Apr 2024 13:03:30 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlegroups.com; s=20230601; t=1712001804; x=1712606604; 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=Kr0FuTPRT9ZvRj4FzIxVoszThsuIsnVxyVhicXgI+LY=; b=XKNL3o21W7NqgAaYrPyUc50MGUFZ/1cgCHvdcYkIaj/nuyCIl9bldDpEM9QHvFMQD9 cLhWxLjVwyUbelGVv3q39jg/n6eYs6rg9H1UrhmJE5Ryt1VUzLSj5MemPdr2ADMVQfhK MZR9HQLEpYKJ2sb22KLI3cTEZsBcV7luS5zEQxawGHWqLI0vqUab4Cw0wpbVnwweVDXi c+U+dW1OkwZSUSEQGIWYVsxyPu2okK0vDLzIJAJNjCTRDxiFt45aeywjLLFZ7SQn1qLi T6+nuOGJm2T0+pR6KFkJ6NDw/8W9CQ/fdLDxh3NgWP6ZU4HwmTkqx3h7tYgBWS2AdcLr eKqg== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=emsit.sk; s=google; t=1712001804; x=1712606604; 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=Kr0FuTPRT9ZvRj4FzIxVoszThsuIsnVxyVhicXgI+LY=; b=AMCSF99v1Ne0XMsAzUUgWh+nH0xWB2OdIFYOI3bW0tQOzB8llP6wImwFGaZ4DXCXfe MPkAvgWbsjji00qXhVx2709qQIyEL2ElQdKClArFefWfDHSZL1LSLB4JoUaDWWn9wMJC YImjh5aTkFUhNKXll10E666bXqEvcKvAI1qu3PW0IU/l1vbAHWc1hlulZogBNITWWskj Pe18Y+pAIJRXV/1WkydAAsNz2R/VPKNftBdbzdjGR/FCToaYReH1d2ruT6fKxwA3PsiN Sgx4bptZ5lEhkQPH/MlbFtfwqU9CLOQ/6wUQ34Y4Z6yhR9vHHIR93Fq287JUvCKG+DzH 2Aug== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1712001804; x=1712606604; 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=Kr0FuTPRT9ZvRj4FzIxVoszThsuIsnVxyVhicXgI+LY=; b=dTeoGXVBeFTqCsJo0g+toPpyAcfOhlrwqrns8QfeGoR5jEvS8uaRiKGShQkf9q0cQD 3LEnGy6tjB3YydwmF1gDkKu2Tpb7fOIiyobsg9jTpRu8bw/s1Yqji6HsO03FuXYc1KcW qorJ+ilVwkNBgHvUa2MUjNDQMLdnpdIWShQ2PtS7beiY+2q/HWY4YHAmwZq7t52VptFG wCBWIbfqMW3eTBvFY5QC22rztZ2DQiWfZPjkXYrH5sWfVzN8msbq+Ftw0d7GTrrROZtQ trgsN5+XEdLKIgsM0EW+AwaAjpEIFaVWKzHSpJyAcmr4AmZfB/XYPLLzKQvpfizESeQW 9tDQ== Sender: bitcoindev@googlegroups.com X-Forwarded-Encrypted: i=1; AJvYcCUkCO107cWvGKU0vKMD4S57NrX/9LZT1DHkToD2hvC8WLCyZBRtPhdWI0DFAAAfku3sxk2bQCkURUOhvmTLb71FuyurX18= X-Gm-Message-State: AOJu0YysNG0SfBGdHfjNUrf3t+4RIim8K9dcygppcagpcw6fRs7K/rf6 3cg7hbYMnMxHt1C6yoAuEVwEeydzlyb0W7qOL71P8KRZCFn9Nonm X-Google-Smtp-Source: AGHT+IEl0STflVQygLI/6qxvLYEJKYMipHWnKUIYzv4cnGGwKnpnHubW3xc1fE6Od/B2+zM1MoqN1g== X-Received: by 2002:a25:3a04:0:b0:dcf:c299:2467 with SMTP id h4-20020a253a04000000b00dcfc2992467mr7870300yba.5.1712001804427; Mon, 01 Apr 2024 13:03:24 -0700 (PDT) X-BeenThere: bitcoindev@googlegroups.com Received: by 2002:a25:c3:0:b0:dcb:b370:7d13 with SMTP id 186-20020a2500c3000000b00dcbb3707d13ls2793848yba.2.-pod-prod-04-us; Mon, 01 Apr 2024 13:03:23 -0700 (PDT) X-Received: by 2002:a05:690c:f0a:b0:614:94ef:5027 with SMTP id dc10-20020a05690c0f0a00b0061494ef5027mr1515833ywb.10.1712001803141; Mon, 01 Apr 2024 13:03:23 -0700 (PDT) Received: by 2002:a05:690c:3:b0:611:9f18:9d1 with SMTP id 00721157ae682-61431553f96ms7b3; Mon, 1 Apr 2024 12:22:33 -0700 (PDT) X-Received: by 2002:a81:9282:0:b0:615:1414:7886 with SMTP id j124-20020a819282000000b0061514147886mr178615ywg.0.1711999352262; Mon, 01 Apr 2024 12:22:32 -0700 (PDT) Date: Mon, 1 Apr 2024 12:22:31 -0700 (PDT) From: emsit To: Bitcoin Development Mailing List Message-Id: In-Reply-To: References: Subject: [bitcoindev] Re: The Future of Bitcoin Testnet MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="----=_Part_417874_463838249.1711999351821" X-Original-Sender: emsit@emsit.sk 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_417874_463838249.1711999351821 Content-Type: multipart/alternative; boundary="----=_Part_417875_1545869895.1711999351821" ------=_Part_417875_1545869895.1711999351821 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable I had to get involved because when I saw the pull request to reset=20 testnet3, I was horrified. Resetting testnet3 without considering the impact after 13 years of use=20 seems like a very bad and drastic step. As you wrote, testnet3 has been=20 here for 13 years, it's not possible to kill it overnight. It will require a transitional phase and announcement so that developers=20 have enough time to react. So the BTC client will have the option of both= =20 testnet3 and testnet4. Yes, mining is demanding, it's a pity it went so far... People won't want= =20 to give up their testnet3 coins, including me!!! How will new users earn testnet4? Will they launch a full node and buy an= =20 ASIC miner? Faucets will stop working for a while, and most faucets will=20 cease to exist. As long as obtaining testnet coins is not easy and in=20 sufficient quantity, there will always be a small market. Or will it simply= =20 deviate from the mainnet, and the reward be more generous? (I lean towards= =20 this idea, to keep the block reward from decreasing and having an unlimited= =20 amount, when there is a lot of it, it will not be rare and will not have=20 value. Or will it reset every year or two so it doesn't have enough time to= =20 become valuable?) D=C3=A1tum: nede=C4=BEa 31. marca 2024, =C4=8Das: 15:24:34 UTC+2, odosielat= e=C4=BE: Jameson Lopp > Hi all, > > I'd like to open a discussion about testnet3 to put out some feelers on= =20 > potential changes to it. First, a few facts: > > 1. Testnet3 has been running for 13 years. It's on block 2.5 million=20 > something and the block reward is down to ~0.014 TBTC, so mining is not= =20 > doing a great job at distributing testnet coins any more. > > 2. The reason the block height is insanely high is due to a rather amusin= g=20 > edge case bug that causes the difficulty to regularly get reset to 1, whi= ch=20 > causes a bit of havoc. If you want a deep dive into the quirk:=20 > https://blog.lopp.net/the-block-storms-of-bitcoins-testnet/ > > 3. Testnet3 is being actively used for scammy airdrops; those of us who= =20 > tend to be generous with our testnet coins are getting hounded by=20 > non-developers chasing cheap gains. > > 4. As a result, TBTC is being actively bought and sold; one could argue= =20 > that the fundamental principle of testnet coins having no value has been= =20 > broken. > > This leads me to ponder the following questions, for which I'm soliciting= =20 > feedback. > > 1. Should we plan for a reset of testnet? If so, given how long it has=20 > been since the last reset and how many production systems will need to be= =20 > updated, would a reset need to be done with a great deal of notice? > > 2. Is there interest in fixing the difficulty reset bug? It should be a= =20 > one liner fix, and I'd argue it could be done sooner rather than later, a= nd=20 > orthogonal to the network reset question. Would such a change, which woul= d=20 > technically be a hard fork (but also arguably a self resolving fork due t= o=20 > the difficulty dynamics) necessitate a BIP or could we just YOLO it? > > 3. Is all of the above a waste of time and we should instead deprecate=20 > testnet in favor of signet? > > - Jameson > --=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/e9c98c9c-6a61-4cc6-9efb-9ea2ca9a76f0n%40googlegroups.com. ------=_Part_417875_1545869895.1711999351821 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable I had to get involved because when I saw the pull request to reset testnet3= , I was horrified.
Resetting testnet3 without considering the impact a= fter 13 years of use seems like a very bad and drastic step. As you wrote, = testnet3 has been here for 13 years, it's not possible to kill it overnight= .
It will require a transitional phase and announcement so that develo= pers have enough time to react. So the BTC client will have the option of b= oth testnet3 and testnet4.
Yes, mining is demanding, it's a pity it we= nt so far... People won't want to give up their testnet3 coins, including m= e!!!

How will new users earn testnet4? Will they launch a full n= ode and buy an ASIC miner? Faucets will stop working for a while, and most = faucets will cease to exist. As long as obtaining testnet coins is not easy= and in sufficient quantity, there will always be a small market. Or will i= t simply deviate from the mainnet, and the reward be more generous? (I lean= towards this idea, to keep the block reward from decreasing and having an = unlimited amount, when there is a lot of it, it will not be rare and will n= ot have value. Or will it reset every year or two so it doesn't have enough= time to become valuable?)

D=C3=A1tum: nede=C4=BEa 31. marca 2024, =C4= =8Das: 15:24:34 UTC+2, odosielate=C4=BE: Jameson Lopp
Hi all,

<= /div>
I'd like to open a discussion about testnet3 to put out some = feelers on potential changes to it. First, a few facts:

1. Testnet3 has been running for 13 years. It's on block 2.5 mill= ion something and the block reward is down to ~0.014 TBTC, so mining is not= doing a great job at distributing testnet coins any more.

2. The reason the block height is insanely high is due to a rather= amusing edge case bug that causes the difficulty to regularly get reset to= 1, which causes a bit of havoc. If you want a deep dive into the quirk:=C2= =A0https://blog.lopp.net/the-block-storms-of-bitcoins-t= estnet/

3. Testnet3 is being actively used for= scammy airdrops; those of us who tend to be generous with our testnet coin= s are getting hounded by non-developers chasing cheap gains.

=
4. As a result, TBTC is being actively bought and sold; one coul= d argue that the fundamental principle of testnet=C2=A0coins having no valu= e has been broken.

This leads me to ponder the fol= lowing questions, for which I'm soliciting feedback.

1. Should we plan for a reset of testnet? If so, given how long it h= as been since the last reset and how many production systems will need to b= e updated, would a reset need to be done with a great deal of notice?
=

2. Is there interest in fixing the difficulty reset bug= ? It should be a one liner fix, and I'd argue it could be done sooner r= ather than later, and orthogonal to the network reset question. Would such = a change, which would technically be a hard fork (but also arguably a self = resolving fork due to the difficulty dynamics) necessitate a BIP or could w= e just YOLO it?

3. Is all of the above a waste of = time and we should instead deprecate testnet in favor of signet?
=
- Jameson

--
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/e9c98c9c-6a61-4cc6-9efb-9ea2ca9a76f0n%40googlegroups.com.=
------=_Part_417875_1545869895.1711999351821-- ------=_Part_417874_463838249.1711999351821--