From: Matt Corallo <lf-lists@mattcorallo•com>
To: Rusty Russell <rusty@rustcorp•com.au>,
Gregory Maxwell <greg@xiph•org>,
Bitcoin Dev <bitcoin-dev@lists•linuxfoundation.org>
Subject: Re: [bitcoin-dev] BIP149 timeout-- why so far in the future?
Date: Fri, 26 May 2017 20:04:58 +0000 [thread overview]
Message-ID: <63d03825-da9b-328d-56b8-0d062f3e0c62@mattcorallo.com> (raw)
In-Reply-To: <87r2ze2833.fsf@rustcorp.com.au>
A more important consideration than segwit's timeout is when code can be
released, which will no doubt be several months after SegWit's current
timeout.
Greg's proposed 6 months seems much more reasonable to me, assuming its
still many months after the formal release of code implementing it.
Matt
On 05/24/17 04:26, Rusty Russell via bitcoin-dev wrote:
> Gregory Maxwell via bitcoin-dev <bitcoin-dev@lists•linuxfoundation.org>
> writes:
>> Based on how fast we saw segwit adoption, why is the BIP149 timeout so
>> far in the future?
>>
>> It seems to me that it could be six months after release and hit the
>> kind of density required to make a stable transition.
>
> Agreed, I would suggest 16th December, 2017 (otherwise, it should be
> 16th January 2018; during EOY holidays seems a bad idea).
>
> This means this whole debacle has delayed segwit exactly 1 (2) month(s)
> beyond what we'd have if it used BIP8 in the first place.
>
> Cheers,
> Rusty.
> _______________________________________________
> bitcoin-dev mailing list
> bitcoin-dev@lists•linuxfoundation.org
> https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev
>
next prev parent reply other threads:[~2017-05-26 20:05 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-23 17:50 Gregory Maxwell
2017-05-24 4:26 ` Rusty Russell
2017-05-26 20:04 ` Matt Corallo [this message]
2017-05-27 1:19 ` Rusty Russell
2017-06-11 5:48 ` Ryan Grant
2017-06-11 13:17 ` Jorge Timón
2017-05-26 7:28 ` shaolinfry
2017-06-11 13:44 Martijn Meijering
2017-06-11 14:29 ` Jorge Timón
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=63d03825-da9b-328d-56b8-0d062f3e0c62@mattcorallo.com \
--to=lf-lists@mattcorallo$(echo .)com \
--cc=bitcoin-dev@lists$(echo .)linuxfoundation.org \
--cc=greg@xiph$(echo .)org \
--cc=rusty@rustcorp$(echo .)com.au \
/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