From: shaolinfry <shaolinfry@protonmail•ch>
To: Gregory Maxwell <greg@xiph•org>
Cc: Bitcoin Dev <bitcoin-dev@lists•linuxfoundation.org>
Subject: Re: [bitcoin-dev] BIP149 timeout-- why so far in the future?
Date: Fri, 26 May 2017 03:28:09 -0400 [thread overview]
Message-ID: <Lt8SJ3RgeodxsMVAVCQzbmruavXSCuDgYbS2hdqZ_vIVAcmvQpH0SgrhkVI51zK5YcNQIAXQD9YBVxcnpDmpGyvgkk5AsvaSrmtZl6a4_Zc=@protonmail.ch> (raw)
In-Reply-To: <CAAS2fgQNPvEuta0KubeDetgYxGhWvdGK10jig0y4ayv0EvZPLw@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1150 bytes --]
I agree the date can be brought forward. FWIW, I originally set the date far out enough that people wouldn't immediately fixate on the date and rather look at the meat of the proposal instead.
Given that we saw around 70% of nodes upgrade to BIP141 in around 5/6 months, I dont see any reason why we cant reduce the date to being 6 months or less from Nov. Given people are starving for segwit to the point of running BIP148, there is good evidence the community will upgrade in record time to BIP149.
Sent from [ProtonMail](https://protonmail.com), Swiss-based encrypted email.
-------- Original Message --------
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.
(If it were a different proposal and not segwit where we already have
seen what network penetration looks like-- that would be another
matter.)
_______________________________________________
bitcoin-dev mailing list
bitcoin-dev@lists•linuxfoundation.org
https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev
[-- Attachment #2: Type: text/html, Size: 1711 bytes --]
next prev parent reply other threads:[~2017-05-26 7:28 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
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 [this message]
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='Lt8SJ3RgeodxsMVAVCQzbmruavXSCuDgYbS2hdqZ_vIVAcmvQpH0SgrhkVI51zK5YcNQIAXQD9YBVxcnpDmpGyvgkk5AsvaSrmtZl6a4_Zc=@protonmail.ch' \
--to=shaolinfry@protonmail$(echo .)ch \
--cc=bitcoin-dev@lists$(echo .)linuxfoundation.org \
--cc=greg@xiph$(echo .)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