public inbox for bitcoindev@googlegroups.com
 help / color / mirror / Atom feed
From: "Edil Guimarães de Medeiros" <jose.edil@gmail.com>
To: Antoine Poinsot <darosior@protonmail.com>
Cc: Pol Espinasa <polespinasa@protonmail.com>, bitcoindev@googlegroups.com
Subject: Re: [bitcoindev] [BIP Draft] Testnet 5
Date: Wed, 3 Jun 2026 18:55:22 -0300	[thread overview]
Message-ID: <CANJiN3KUW8K5mAyoekzYFyBf3jtnsTxW8LfwvUq7K5FDs-XR7Q@mail.gmail.com> (raw)
In-Reply-To: <5e9rybLioivQv7knRGX4xCLZffObV0RGjf2DP0-0wC-K9BRTfjV2GsWUjUlYnOw7EYRDVGA4ERPqoCGynGmNQXNLRy_mhvwdITuBR2t1rJs=@protonmail.com>

[-- Attachment #1: Type: text/plain, Size: 1289 bytes --]

Hi Antoine,


> However a risk that the network becomes temporarily unusable does not
> justify introducing yet another band-aid that would inevitably make it
> permanently unusable.
>

Agree.


> Moreover, i think we are in a better position nowadays to deal with such a
> situation than we were 15 years ago when that happened on testnet1.
>

Yes, I expect some people to contribute some hash rate to unstuck a
testnet5 chain (I would be willing to contribute), but I'm not so sure that
will be enough.
Anyhow, I gave this scenario some thought and came to the conclusion that
the odds of it happening (big miner increasing difficulty on purpose and
leaving) would be pretty low.

Yet, it doesn't address the problem of coins getting value (which I still
think is unsolvable given a pretty stable network).
Not the biggest concern to me, just that this will be an argument anytime
soon.

-- 
Edil

-- 
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/CANJiN3KUW8K5mAyoekzYFyBf3jtnsTxW8LfwvUq7K5FDs-XR7Q%40mail.gmail.com.

[-- Attachment #2: Type: text/html, Size: 2653 bytes --]

  parent reply	other threads:[~2026-06-03 21:57 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-06-02 11:24 [bitcoindev] [BIP Draft] Testnet 5 'Pol Espinasa' via Bitcoin Development Mailing List
2026-06-02 14:25 ` José Edil Guimarães de Medeiros
     [not found]   ` <5e9rybLioivQv7knRGX4xCLZffObV0RGjf2DP0-0wC-K9BRTfjV2GsWUjUlYnOw7EYRDVGA4ERPqoCGynGmNQXNLRy_mhvwdITuBR2t1rJs=@protonmail.com>
2026-06-03 21:55     ` Edil Guimarães de Medeiros [this message]
2026-06-02 15:02 ` Saint Wenhao
2026-06-02 15:29   ` 'Antoine Poinsot' via Bitcoin Development Mailing List
2026-06-02 16:22   ` Garlo Nicon
2026-06-02 16:48     ` 'Pol Espinasa' via Bitcoin Development Mailing List
2026-06-02 16:37   ` 'Pol Espinasa' via Bitcoin Development Mailing List
2026-06-05  9:35 ` Anthony Towns
2026-06-07 21:52   ` 'Fabian' via Bitcoin Development Mailing List
2026-06-09 21:53     ` Murch

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=CANJiN3KUW8K5mAyoekzYFyBf3jtnsTxW8LfwvUq7K5FDs-XR7Q@mail.gmail.com \
    --to=jose.edil@gmail.com \
    --cc=bitcoindev@googlegroups.com \
    --cc=darosior@protonmail.com \
    --cc=polespinasa@protonmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
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