From: Jeremy <jlrubin@mit•edu>
To: Anthony Towns <aj@erisian•com.au>
Cc: Bitcoin Protocol Discussion <bitcoin-dev@lists•linuxfoundation.org>
Subject: Re: [bitcoin-dev] March 23rd 2021 Taproot Activation Meeting Notes
Date: Thu, 25 Mar 2021 07:30:52 -0700 [thread overview]
Message-ID: <CAD5xwhjRsNhL32cONwCTms-a8FGv+FiK3k1ihU8y5a3G1WMb9A@mail.gmail.com> (raw)
In-Reply-To: <20210325070204.GA10937@erisian.com.au>
[-- Attachment #1: Type: text/plain, Size: 2972 bytes --]
I think it's fine to move the dates back two weeks in that case; it was
unclear from the meeting transcript if people thought release would be may
1st or startheight, but via parameter flexibility we can shift everything
back 2 weeks if we want.
W.r.t. the selection of MTP there's no funny business I just estimated a
mid period MTP. I don't think midnight utc is sacred, it's 5 o'clock
somewhere.
We can adjust the parameters at your preference -- a little more or less
time shouldn't hurt, but that is also the point of picking mid period MTP
that it makes drift not matter much.
On Thu, Mar 25, 2021, 12:02 AM Anthony Towns <aj@erisian•com.au> wrote:
> On Tue, Mar 23, 2021 at 08:46:54PM -0700, Jeremy via bitcoin-dev wrote:
> > 3. Parameter Selection
> > - There is broad agreement that we should target something like a May 1st
> > release, with 1 week from rc1 starttime/startheight,
> > and 3 months + delta stoptime/stopheight (6 retargetting periods), and
> an
> > activation time of around Nov 15th.
>
> I'd thought the idea was to release mid-late April, targetting a starttime
> of May 1st.
>
> > - If we select heights, it looks like the first signalling period would
> be
> > 683424, the stop height would be 695520.
>
> > - If we select times, we should target a mid-period MTP. We can shift
> this
> > closer to release, but currently it looks like a 1300 UTC May 7th start
> time and stop time would be 1300 UTC August 13th.
>
> We've traditionally done starttime/timeout at midnight UTC, seems weird
> to change. Oh, or is it a Friday-the-13th, lets have 13s everywhere
> thing?
>
> Anyway, block 695520 is about 19440 blocks away, which we'd expect to be
> 135 days, but over the past two years, 19440 blocks prior to a retarget
> boundary has been between 127 (-8) days and 137 (+2) days, and in the
> last four years, it's been between 121 (-14) days and 139 (+4) days. [0]
>
> So given block 676080 had mediantime 1616578564, I think picking a
> mediantime no later than ~139 days later, ie 1628640000 (00:00 UTC
> 11 Aug) would be the most likely to result in MTP logic matching the
> height parameters above, and a day or two earlier still might be better.
> (It will match provided MTP passes the timeout at any block in the range
> [695520, 697535])
>
> > (please check my math, if anyone is superstitious we can add a day to
> times...)
>
> It looks to me like blocks are more likely to arrive earlier than later
> (which is what we'd expect with increasing hashrate), fwiw, so adding
> days would be more likely to cause MTP to have more signalling periods
> than height-based, rather than avoid having fewer.
>
> Cheers,
> aj
>
> [0] $ for b in `seq 201600 2016 676000`; do a=$(($b-19440)); echo $((
> $(bitcoin-cli getblockheader $(bitcoin-cli getblockhash $b) | grep
> mediantime | cut -d\ -f4 | tr -d ,) - $(bitcoin-cli getblockheader
> $(bitcoin-cli getblockhash $a) | grep mediantime | cut -d\ -f4 | tr -d ,)
> )); done
>
[-- Attachment #2: Type: text/html, Size: 3529 bytes --]
next prev parent reply other threads:[~2021-03-25 14:31 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-24 3:46 Jeremy
2021-03-25 7:02 ` Anthony Towns
2021-03-25 14:30 ` Jeremy [this message]
2021-04-06 4:25 ` Rusty Russell
2021-04-07 1:20 ` Ryan Grant
2021-04-07 5:01 ` Rusty Russell
2021-04-07 13:42 ` Claus Ehrenberg
2021-04-07 15:25 ` eric
2021-04-07 17:13 ` Matt Corallo
2021-04-08 11:11 ` Anthony Towns
2021-03-24 11:23 Michael Folkson
2021-03-24 18:10 ` Jeremy
2021-03-24 19:14 ` Michael Folkson
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=CAD5xwhjRsNhL32cONwCTms-a8FGv+FiK3k1ihU8y5a3G1WMb9A@mail.gmail.com \
--to=jlrubin@mit$(echo .)edu \
--cc=aj@erisian$(echo .)com.au \
--cc=bitcoin-dev@lists$(echo .)linuxfoundation.org \
/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