From: Gregory Maxwell <greg@xiph•org>
To: "Hampus Sjöberg" <hampus.sjoberg@gmail•com>
Cc: Bitcoin Protocol Discussion <bitcoin-dev@lists•linuxfoundation.org>
Subject: Re: [bitcoin-dev] Miners forced to run non-core code in order to get segwit activated
Date: Tue, 20 Jun 2017 22:34:29 +0000 [thread overview]
Message-ID: <CAAS2fgQKrFCTL-=qREOjNrwjDqhgdPZQUSgpXHUKyG4+NAo26g@mail.gmail.com> (raw)
In-Reply-To: <CAFMkqK_73RrpaS2oJQ-0o6oC29m6a1h411_P7HmVcAyX712Sgw@mail.gmail.com>
On Tue, Jun 20, 2017 at 10:15 PM, Hampus Sjöberg
<hampus.sjoberg@gmail•com> wrote:
> Segwit2x/BIP91/BIP148 will orphan miners that do not run a Segwit2x (or
> BIP148) node, because they wouldn't have the new consensus rule of requiring
> all blocks to signal for segwit.
All versions of Bitcoin Core since 0.13.1 signal segwit, 0.14.1+ even
when downstream mining software doesn't support it.
I think it would be useful for there to exist a useful and trivial
patch against current (0.14.2) software to engage in the BIP91-like
orphaning, like people have provided for BIP148-- but right now I
don't see any specification of the behavior so it's unclear to me
_exactly_ what it would need to implement to be consistent.
next prev parent reply other threads:[~2017-06-20 22:34 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-20 15:44 Erik Aronesty
2017-06-20 16:49 ` Hampus Sjöberg
2017-06-20 17:22 ` Mark Friedenbach
2017-06-20 21:49 ` Gregory Maxwell
2017-06-20 22:15 ` Hampus Sjöberg
2017-06-20 22:29 ` Jacob Eliosoff
2017-06-20 22:48 ` Mark Friedenbach
2017-06-20 22:57 ` Jacob Eliosoff
2017-06-20 23:01 ` Jacob Eliosoff
2017-06-21 1:36 ` Erik Aronesty
2017-06-21 2:11 ` Mark Friedenbach
2017-06-21 4:05 ` Jacob Eliosoff
2017-06-27 15:42 ` Sergio Demian Lerner
2017-06-27 16:31 ` Jorge Timón
2017-06-27 19:26 ` Erik Aronesty
2017-06-20 22:34 ` Gregory Maxwell [this message]
2017-06-20 22:53 ` Hampus Sjöberg
2017-06-20 19:49 Ryan J Martin
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='CAAS2fgQKrFCTL-=qREOjNrwjDqhgdPZQUSgpXHUKyG4+NAo26g@mail.gmail.com' \
--to=greg@xiph$(echo .)org \
--cc=bitcoin-dev@lists$(echo .)linuxfoundation.org \
--cc=hampus.sjoberg@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