public inbox for bitcoindev@googlegroups.com
 help / color / mirror / Atom feed
From: Saint Wenhao <saintwenhao@gmail•com>
To: Bitcoin Development Mailing List <bitcoindev@googlegroups.com>
Subject: Re: [bitcoindev] The Future of Bitcoin Testnet
Date: Fri, 25 Apr 2025 10:19:00 -0700 (PDT)	[thread overview]
Message-ID: <daecbe84-30e7-4ba8-aa60-596cb7c1658bn@googlegroups.com> (raw)
In-Reply-To: <f4c7991c-b053-481c-83ff-d37f9aad6d66n@googlegroups.com>


[-- Attachment #1.1: Type: text/plain, Size: 2883 bytes --]

> Should we plan for a reset of testnet?

Surprisingly, it is a very good question. However, replacing testnet3 with 
testnet4, by just dropping support for the old network, should not be 
called "reset", but rather "abandon". So, the question is: should we mine a 
new Genesis Block, at height one, on top of the current Genesis Block from 
testnet3, and trigger the biggest possible chain reorganization, where the 
whole chain is reorged in a backward-compatible way?

Also I wonder, if that method of introducing testnet5, by doing it on top 
of testnet4's Genesis Block is worth considering. Because then, some 
planned changes, like entirely dropping the difficulty reset, could be 
potentially turned from hard-fork into just a regular soft-fork, supported 
by hashrate majority.

And of course, reorging everything is an edge case, that we may want to see 
on any testnet first, before anyone will succeed with that on the main 
network, if SHA-256 will ever be broken, and if re-hashing the whole chain 
will be needed.

poniedziałek, 31 marca 2025 o 22:41:20 UTC+2 Garlo Nicon napisał(a):

> > 4. As a result, TBTC is being actively bought and sold; one could argue 
> that the fundamental principle of testnet coins having no value has been 
> broken.
>
> Now, some time passed, so we can look at the history, and get some 
> conclusions. In case of testnet4, the same thing happened. And some people 
> consider testnets as altcoins: 
> https://bitcointalk.org/index.php?topic=5536825.0
> Which means, that if new testnets will be released in a similar way, then 
> none of them will be worthless.
>
> niedziela, 5 maja 2024 o 15:12:08 UTC+2 Peter Todd napisał(a):
>
> On Tue, Apr 30, 2024 at 11:46:59AM -0700, Matthew Bagazinski wrote: 
> > 
> > 
> > Unfortunately, the current form of Testnet is doomed to have value, just 
> > like BTC. Its scarcity makes it a valuable asset. And no reset will 
> change 
> > that. It will only result in repeated resets, multiple versions of 
> testnet, 
> > and people never learning. 
>
> The scarcity of testnet BTC isn't the only valuable asset in testnet; 
> testnet 
> blockchain space itself is a scarce, valuable, asset. It's an asset that 
> we 
> can't easily make worthless, even through testnet resets, as there are 
> usecases 
> (including scams) where the long-term persistence of the data doesn't 
> matter. 
>
> -- 
> https://petertodd.org 'peter'[:-1]@petertodd.org 
>
>

-- 
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 visit https://groups.google.com/d/msgid/bitcoindev/daecbe84-30e7-4ba8-aa60-596cb7c1658bn%40googlegroups.com.

[-- Attachment #1.2: Type: text/html, Size: 4272 bytes --]

  reply	other threads:[~2025-04-29 14:15 UTC|newest]

Thread overview: 42+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-31 13:19 Jameson Lopp
2024-03-31 14:33 ` Luke Dashjr
2024-03-31 14:57   ` Jameson Lopp
2024-03-31 17:21     ` Eric Voskuil
2024-04-09 18:28   ` Garlo Nicon
2024-03-31 16:02 ` Peter Todd
2024-03-31 21:01   ` Nagaev Boris
2024-03-31 21:29     ` Peter Todd
2024-04-01 12:54       ` Jameson Lopp
2024-04-01 13:37         ` Pieter Wuille
2024-04-01 14:20           ` Andrew Poelstra
2024-04-01 22:01             ` 'Fabian' via Bitcoin Development Mailing List
2024-04-02 11:53               ` Jameson Lopp
2024-04-02 18:36                 ` Lukáš Kráľ
2024-04-02 19:46                   ` Jameson Lopp
2024-04-03  4:19           ` Anthony Towns
2024-04-03 18:18             ` emsit
2024-04-03 19:35               ` Andrew Poelstra
2024-04-30 18:46               ` Matthew Bagazinski
2024-05-01 15:30                 ` Garlo Nicon
2024-05-04 17:13                 ` Peter Todd
2025-03-31 10:48                   ` Garlo Nicon
2025-04-25 17:19                     ` Saint Wenhao [this message]
2024-04-10  6:57       ` Garlo Nicon
2024-04-22  4:33         ` Ali Sherief
2024-04-01 13:25 ` Andrew Poelstra
2024-04-01 13:32   ` 'Fabian' via Bitcoin Development Mailing List
2024-04-01 14:28 ` Warren Togami
2024-04-01 19:22 ` [bitcoindev] " emsit
2024-04-04  8:14 ` Calvin Kim
2024-04-04 12:47   ` Jameson Lopp
2024-04-05  4:30     ` Calvin Kim
2024-04-06 23:04       ` David A. Harding
2024-04-09 16:48         ` Peter Todd
2024-04-16 17:30           ` [bitcoindev] " 'Sjors Provoost' via Bitcoin Development Mailing List
2024-04-07  7:20   ` [bitcoindev] " Christian Decker
2024-04-07  8:09     ` K Calvin
2024-04-08 19:11 ` Garlo Nicon
2024-04-09  4:29   ` coinableS
2024-04-28 13:45 ` [bitcoindev] " Matt Corallo
2024-05-02  7:10   ` Ali Sherief
2024-05-04 17:08     ` Peter Todd

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=daecbe84-30e7-4ba8-aa60-596cb7c1658bn@googlegroups.com \
    --to=saintwenhao@gmail$(echo .)com \
    --cc=bitcoindev@googlegroups.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox