From: "Jorge Timón" <jtimon@jtimon.cc>
To: Ryan Grant <bitcoin-dev@rgrant.org>
Cc: Bitcoin Dev <bitcoin-dev@lists.linuxfoundation.org>
Subject: Re: [bitcoin-dev] BIP149 timeout-- why so far in the future?
Date: Sun, 11 Jun 2017 15:17:43 +0200 [thread overview]
Message-ID: <CABm2gDqr=SHgva4H1sBtW_k8-5RxupSzq+zanmz21e=X2P=6Gg@mail.gmail.com> (raw)
In-Reply-To: <CAMnpzfqqmTFkf_HKPb18ijm-bYja_MpRofBYNXd3TkqVLsJhNw@mail.gmail.com>
The current proposal assumes that bip149 would only be merged and
released after nov15, so there's not time in one day.
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).
I was slowly modifying shaolinfry's code to try to code that, but I'm
currently not working on it because there doesn't seem there's a lot
of interest in releasing bip149 before nov15...
https://github.com/jtimon/bitcoin/commits/b15-shaolinfry-bip149
On Sun, Jun 11, 2017 at 7:48 AM, Ryan Grant via bitcoin-dev
<bitcoin-dev@lists.linuxfoundation.org> wrote:
> Is there any reason that BIP149 activation on November 16th would
> cause a problem?
> _______________________________________________
> bitcoin-dev mailing list
> bitcoin-dev@lists.linuxfoundation.org
> https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev
next prev parent reply other threads:[~2017-06-11 13:17 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-23 17:50 [bitcoin-dev] BIP149 timeout-- why so far in the future? 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 [this message]
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='CABm2gDqr=SHgva4H1sBtW_k8-5RxupSzq+zanmz21e=X2P=6Gg@mail.gmail.com' \
--to=jtimon@jtimon.cc \
--cc=bitcoin-dev@lists.linuxfoundation.org \
--cc=bitcoin-dev@rgrant.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