From: "Jorge Timón" <jtimon@jtimon•cc>
To: Jacob Eliosoff <jacob.eliosoff@gmail•com>
Cc: Bitcoin Dev <bitcoin-dev@lists•linuxfoundation.org>
Subject: Re: [bitcoin-dev] The BIP148 chain split may be inevitable
Date: Sun, 11 Jun 2017 17:06:01 +0200 [thread overview]
Message-ID: <CABm2gDoS0eiiabxbfQc4Cc7Jqk-XfDDL6QdGhDn-TzrDpd8Hfw@mail.gmail.com> (raw)
In-Reply-To: <CAAUaCyiwnspvJ9HY41GK8tMsA4ezpFPR1Ka9upik6UwsYBASnQ@mail.gmail.com>
> I believe that means 80% of hashrate would need to be running BIP91 (signaling bit 4) by ~June 30 (so BIP91 locks in ~July 13, activates ~July 27), not "a few days ago" as I claimed. So, tight timing, but not impossible.
This is not needed, if segwit is locked in by aug 1 (with or without
bip91), no split will happen even if segwit is not active yet.
So the hashrate majority could avoid the split that way (or adopting bip148).
But it doesn't seem like they are planning to do this (with or without
bip91), the last thing I've heard, it's they will wait until
"immediately" before they signal sw (but there must be some language
barrier here, perhaps "immediately" and "inmediatamente" are false
friends). The reason why they will wait until "immediately" instead of
just starting to signal sw today, it's still unclear to me.
The other way to prevent the split is if bip148 users abort bip148
deployment, but unfortunately that seems increasingly unlikely.
next prev parent reply other threads:[~2017-06-11 15:06 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-09 4:40 Jacob Eliosoff
2017-06-09 5:23 ` Jacob Eliosoff
2017-06-10 18:04 ` Jacob Eliosoff
2017-06-11 15:06 ` Jorge Timón [this message]
2017-06-11 17:11 ` Jorge Timón
2017-06-11 17:12 ` 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=CABm2gDoS0eiiabxbfQc4Cc7Jqk-XfDDL6QdGhDn-TzrDpd8Hfw@mail.gmail.com \
--to=jtimon@jtimon$(echo .)cc \
--cc=bitcoin-dev@lists$(echo .)linuxfoundation.org \
--cc=jacob.eliosoff@gmail$(echo .)com \
/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