[bitcoin-dev] BIP149 timeout-- why so far in the future?

Matt Corallo lf-lists at mattcorallo.com
Fri May 26 20:04:58 UTC 2017


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 at 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 at lists.linuxfoundation.org
> https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev
> 


More information about the bitcoin-dev mailing list