From: Martijn Meijering <martijn.meijering@mevs.nl>
To: bitcoin-dev@lists.linuxfoundation.org
Subject: [bitcoin-dev] BIP149 timeout-- why so far in the future?
Date: Sun, 11 Jun 2017 15:44:17 +0200 [thread overview]
Message-ID: <CAODYVYc7x-C5nLxtTHYh9iJuCgv0B7XADCS7DeSW8O8VMuGvbQ@mail.gmail.com> (raw)
Jorge Timón wrote:
"My preference would be a bip149 proposal that could be merged and
released now, but some people complain that would require more
testing, because *if you deploy bip149 and then sw gets activated pre
nov15, then you want bip149 nodes to use the old service bit for
segwit*, not the new one (you would use that one if it activates post
nov15, so that pre-bip149 nodes don't get confused)."
(emphasis added)
Why not just make sure BIP 149 will never activate unless BIP 141 has
expired unsuccessfully? If BIP 141 should unexpectly activate, then
BIP 149 nodes would notice and act as pre-SegWit nodes indefinitely,
but remain in consensus with BIP 141 nodes.
It might be slightly less convenient for BIP 149 users to upgrade
again, but then at least we could start deploying BIP 149 sooner.
next reply other threads:[~2017-06-11 13:44 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-11 13:44 Martijn Meijering [this message]
2017-06-11 14:29 ` [bitcoin-dev] BIP149 timeout-- why so far in the future? Jorge Timón
-- strict thread matches above, loose matches on Subject: below --
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
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=CAODYVYc7x-C5nLxtTHYh9iJuCgv0B7XADCS7DeSW8O8VMuGvbQ@mail.gmail.com \
--to=martijn.meijering@mevs.nl \
--cc=bitcoin-dev@lists.linuxfoundation.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
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