Date: Tue, 6 Apr 2021 11:31:23 -1000
From: "David A. Harding" <dave@dtrt.org>
To: Anthony Towns <aj@erisian.com.au>
Message-ID: <20210406213123.l3b2zqecxxc4h2ls@ganymede>
References: <CAD5xwhgTKLhA82=PsF9EXrhvmx6zcA=ffOvHD4qt4q1sAqzhng@mail.gmail.com>
 <20210405103452.GA15866@erisian.com.au>
 <CAMZUoKk39YNFVgGQ2krFSx4GNHN0rO_M2j91ETMGSO01SHYEcw@mail.gmail.com>
 <20210406162216.k34aplxwznh5z25v@ganymede>
 <CAMZUoKkxMudxUsOqA3varpjiqeVv+e-QD6RB8JzEfhjSMLJqeg@mail.gmail.com>
 <CAMZUoKnjjhYbYABL+iw5VivQfKTn64vV0ereOtz5VFEb6g0xvw@mail.gmail.com>
 <20210406194819.GA29761@erisian.com.au>
MIME-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha512;
 protocol="application/pgp-signature"; boundary="o64y3m3ixdbxytli"
Content-Disposition: inline
In-Reply-To: <20210406194819.GA29761@erisian.com.au>
User-Agent: NeoMutt/20180716
Cc: Bitcoin Protocol Discussion <bitcoin-dev@lists.linuxfoundation.org>
Subject: Re: [bitcoin-dev] Taproot Activation Meeting Reminder: April 6th
 19:00 UTC bitcoin/bitcoin-dev
Precedence: list


--o64y3m3ixdbxytli
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

(Replies to multiple emails)

On Tue, Apr 06, 2021 at 12:27:34PM -0400, Russell O'Connor wrote:
> It isn't  "$MIN_LOCKIN_TIME + $((10 * 2016)) minutes". It's
> "$MIN_LOCKIN_TIME + time until next retargeting period + $((10 * 2016))
> minutes".

Ah, drat, I forgot about that.  Thank you for correcting my oversight!

> That doesn't seem like a particularly important design goal to me? Having
> a last minute two week delay seems easy to deal with

=46rom my perspective, that of a person focused on communicating
information that affects Bitcoin users and recommending infrastructure
adjustments that should be made to accomodate those changes, I'd find
having a predictable activation date to be of significant benefit.
Given that, an activation scheme that could provide a tight timeline
(only delayable, not accellerable, by miner shenanegeans) would be
something I'd consider an advantage of that method.

That said, it's probably not worth making the activation state machine
more complicated for when the simplicity of the machine for height-based
activations is it's chief touted benefit.

Thanks,

-Dave

--o64y3m3ixdbxytli
Content-Type: application/pgp-signature; name="signature.asc"

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

iQIzBAEBCgAdFiEEgxUkqkMp0LnoXjCr2dtBqWwiadMFAmBs0ysACgkQ2dtBqWwi
adN3vBAAs9ZUsAHtpM9pCP4Dfdt51wlHNOFs1tBD96ZpoBZZdZUC8RscWujlan0Z
SUHJl4t7VIZ25PX6EvFCRCxWYdRL1gXrwOnYQxzdzPhbLugTIOgYWgTLWlKe687I
8goRhZVo22uZPyzanbD7L1yxNaYAAsbT+/xAoYnkmW0NcfcQvt/4t9hxc8iXFFsC
avSOWhSzTSxe+rygIbgoehpYAJiIzCobZOWfeCaTi7hMKhC6xiczx9gO+1NGNFY0
F+alKA5qkS7/XbX6iRX78R72WxEvq2W30yDE0rwvZS2rSqSUf2tmJimE+8Le3Psp
rCgGUthxPf732mDkVbbOphdgLJCGzlOhIY1KnfkDglzR3jXOOHUGmA10VSExMarh
qE9LGV80t8nNo7GBaCGbKrB6U0tZ1bIwz8R01gZqLebOr5e741bbwIIHkUHfr/YI
ukSfoVxp2o/k5KCJIKgF1OAn2Wnf7+K8CsGb3lO+v0zAZbKSu7LhNETGzy3LwRUK
CkRtwhAp3a7dLhqwaITo7dMUqJvR6y229Ml0zW7bbiVNfWUEHqAYhGmyRUs7S+d2
VM34WzUkGH2VycSZdL26aH9+pcOsZkIFzQSYf0/TBNAv2+mZFrGxy9Ja7zGKuyIE
j+6SWDUDpnuSa+CTFYxvwNtKWulYLYRRKltCYpmE+/hotaQWSyM=
=ea1W
-----END PGP SIGNATURE-----

--o64y3m3ixdbxytli--