From: Andrew Poelstra <apoelstra@wpsoftware•net>
To: emsit <emsit@emsit•sk>
Cc: Bitcoin Development Mailing List <bitcoindev@googlegroups.com>
Subject: Re: [bitcoindev] The Future of Bitcoin Testnet
Date: Wed, 3 Apr 2024 19:35:29 +0000 [thread overview]
Message-ID: <Zg2vgUurs3w1LKqc@camus> (raw)
In-Reply-To: <7a67edd1-0182-4170-90f4-998d12431024n@googlegroups.com>
[-- Attachment #1: Type: text/plain, Size: 3271 bytes --]
On Wed, Apr 03, 2024 at 11:18:49AM -0700, emsit 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.
>
> When I imagine what I would have to go through to mine testnet BTC, how
> much time and money to invest (buying/renting ASIC - CPU mining is a thing
> of the past), and someone offered me a simpler alternative, to just buy it,
> I probably wouldn't hesitate and would just buy it. Many people HODL
> testnet coins precisely because it's difficult to obtain them and they
> don't want to give them up, regardless of their economic value. People have
> learned, CRYPTO = HODL.
>
> In my opinion, it's more important to address the issue so that testnet
> doesn't need to be reset. Because it angers people, even those who aren't
> responsible and want to use it as intended. I'm afraid that after the
> reset, mining will be very difficult, expensive, and impossible for most
> people. Not everyone has an ASIC at home, and CPU mining is out of the
> question. And faucets won't work. I'm also afraid that whales will emerge
> who will mine it from the beginning while the reward is high, for worse
> times.
>
> I have a faucet myself and I know how my users behave, they always want
> more, and most people HODL it. Only a negligible amount comes back to my
> faucet. So, the idea of freely sharing is nice but unrealistic.
>
> A reset of testnet that will be "the same" as the old one doesn't make
> sense to me. Wouldn't it be possible to pre-mine all the coins and
> distribute them via faucet? Or generate more than 21M? If there are a large
> number of them, there will be enough for everyone and they will be
> worthless.
>
The dystopia you describe is not impossible, but I think it's pretty
unlikely. It's true that most users will not be able to mine, and that
nobody will be able to CPU-mine the way you could with testnet3.
But to get from there to "the only miners will be people who are
hoarding coins to somehow force a positive price" and "there will be no
faucets at all" feels like a stretch. Especially if we had a stated
intention to reset the network every 4 or 8 years or whetever the reward
got too low. Fixed supply or not, I don't see how a network slated to be
abandoned would have a sustainable market value.
Certainly, we could try launching testnet4, and if this happens, we
could switch to testnet5 which would need some further protection.
Perhaps, as you say, it would need to be premined by somebody willing to
run a faucet, for example.
--
Andrew Poelstra
Director of Research, Blockstream
Email: apoelstra at wpsoftware.net
Web: https://www.wpsoftware.net/andrew
The sun is always shining in space
-Justin Lewis-Webster
--
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/Zg2vgUurs3w1LKqc%40camus.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2024-04-03 19:37 UTC|newest]
Thread overview: 40+ 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 [this message]
2024-04-30 18:46 ` Matthew Bagazinski
2024-05-01 15:30 ` Garlo Nicon
2024-05-04 17:13 ` Peter Todd
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=Zg2vgUurs3w1LKqc@camus \
--to=apoelstra@wpsoftware$(echo .)net \
--cc=bitcoindev@googlegroups.com \
--cc=emsit@emsit$(echo .)sk \
/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