Delivery-date: Mon, 01 Apr 2024 07:21:40 -0700
Sender: bitcoindev@googlegroups.com
Received-SPF: pass (google.com: domain of apoelstra@wpsoftware.net designates 66.183.0.205 as permitted sender) client-ip=66.183.0.205;
Date: Mon, 1 Apr 2024 14:20:53 +0000
From: Andrew Poelstra <apoelstra@wpsoftware.net>
To: bitcoindev@googlegroups.com
Subject: Re: [bitcoindev] The Future of Bitcoin Testnet
Message-ID: <ZgrCxWxMkiAt2Tg2@camus>
References: <CADL_X_eXjbRFROuJU0b336vPVy5Q2RJvhcx64NSNPH-3fDCUfw@mail.gmail.com>
 <ZgmJFfXnQddkTQVq@petertodd.org>
 <CAFC_Vt7zKvMEfQLzWHQ6t_9bgv1iqt4Ah8N883CuoSfmLUKdMA@mail.gmail.com>
 <ZgnVtJHn2ikLfwa9@petertodd.org>
 <CADL_X_cmcXxHke089OD_45VRJy5aR+9uj-18bSjXBE7FKwR-Jw@mail.gmail.com>
 <wKrcm6SEjcG_7UmxByP-rDDVajB7-oYJRF9p_BjLe5XVzxVV9nCB8RsTAXcD5vF_rWxUmLK4HOM7zV7U4-kZSUO9Ccj4jEehsbbb7FD45GQ=@wuille.net>
MIME-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha256;
	protocol="application/pgp-signature"; boundary="C/AxekDA4/AqNTHA"
Content-Disposition: inline
In-Reply-To: <wKrcm6SEjcG_7UmxByP-rDDVajB7-oYJRF9p_BjLe5XVzxVV9nCB8RsTAXcD5vF_rWxUmLK4HOM7zV7U4-kZSUO9Ccj4jEehsbbb7FD45GQ=@wuille.net>
Precedence: list
Mailing-list: list bitcoindev@googlegroups.com; contact bitcoindev+owners@googlegroups.com


--C/AxekDA4/AqNTHA
Content-Type: text/plain; charset="UTF-8"
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Mon, Apr 01, 2024 at 01:37:59PM +0000, Pieter Wuille wrote:
>=20
> As for using other measures to prevent too large difficulty variations...=
 I'm not sure that's desirable, because it always cuts both ways (nicely de=
monstrated by the "allow difficulty 1 rule" on testnet3 backfiring and enab=
ling block storms!). For applications that actually need very predictable b=
lock rate, there is signet. For others, just the normal mainnet rules are p=
robably not too terrible. I would be ok with having a somewhat reduced bloc=
k interval (say a few days instead of 2 weeks) if that's not deemed to comp=
lex to implement across the ecosystem, but I don't think it's that importan=
t.
>

I really like this. For my part (rust-bitcoin) this would be as simple
as adding an extra parameter to my blockparams structure. Possibly one
already exists, I'd have to check.

This would be much easier than the existing situation where we have
special-case logic for testnet the difficulty-1 target.

It would also limit the amount of bikeshedding possible, since there
aren't too many conflicting goals regarding the retargeting window...
unlike tweaking the existing logic where there's a tradeoff between
"we should make this never happen" and "it should happen often enough
that it doesn't break people's code" and "it should happen if blocks
slow down to like, 1/50th their normal rate even if they are still
technically being produced" and "it shouldn't be possible to trigger
it within the 2-hour timestamp-faking window" etc. And questions
about whether we should fix/redesign the interaction between the reset
rule and the normal difficulty retarget.


OTOH, since we already have the special logic, I'd also be happy with
tweaking the existing rule. My specific proposal (after reading Jameson's
post, which has some nice graphs of difficulty) would be

* increase the reset threshold from 20 minutes to 6 hours, which is
  (a) well outside the 2-hour window in which miners can easily fake
  timestamps, and (b) will basically never be hit by accident
* increase the reset difficulty from 1 to 1MM, which is an rough lower
  bound on the "normal" testnet difficulty seen historically

Which puts us in the "this rule would never be triggered unless
literally everyone stopped mining" corner of the design space.


--=20
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

--=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/ZgrCxWxMkiAt2Tg2%40camus.

--C/AxekDA4/AqNTHA
Content-Type: application/pgp-signature; name="signature.asc"

-----BEGIN PGP SIGNATURE-----

iQEzBAEBCAAdFiEEkPnKPD7Je+ki35VexYjWPOQbl8EFAmYKwsQACgkQxYjWPOQb
l8F37Af/eKhN/8c40ez2uDx8/jUtklkrvnyzK9tD9Exlqg8seQ8f3kanK6opkcie
dA2ZiI5PbWnTujNHwyi0Aa9quJbJg3ostQCWzYu8wASNAprQelCI5jP5fAZAp9h6
JyqUsrvjzWSBYPNaa596qYaMOKcup2kPZ5zxzmU0wueycaBaRQoevxQx9xAWlyFU
IKUiAWwi0Ep5eNrADYGEs0gxDp4E6XmCER7CM35fkvLzUr2WSeHFjpQOQI3dVExY
jUWWUTtX3obRYT1UOMcpX5ueHgabf6t01p6dqBZ5Rf9PWwILLGu2yUvZMcCssVD5
ZDmiU8yC52XRvFoZz6xrKKeWP0b5Zw==
=jegM
-----END PGP SIGNATURE-----

--C/AxekDA4/AqNTHA--