From: "Hampus Sjöberg" <hampus.sjoberg@gmail•com>
To: Erik Aronesty <erik@q32•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 18:49:38 +0200 [thread overview]
Message-ID: <CAFMkqK_OtZ=S5LFqERCYwSQCkbxdnWJq+wN-YM3CVkKWJx2SBA@mail.gmail.com> (raw)
In-Reply-To: <CAJowKgLtu-HUDuakk4DDU53nyChbQk_zY=f5OO2j1Za95PdL7w@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 883 bytes --]
I don't think it's a huge deal if the miners need to run a non-Core node
once the BIP91 deployment of Segwit2x happens. The shift will most likely
be temporary.
I agree that the "-bip148"-option should be merged, though.
2017-06-20 17:44 GMT+02:00 Erik Aronesty via bitcoin-dev <
bitcoin-dev@lists•linuxfoundation.org>:
> Are we going to merge BIP91 or a -BIP148 option to core for inclusion in
> the next release or so?
>
> Because a large percentage of miners are indifferent, right now miners
> have to choose between BIP148 and Segwit2x if they want to activate Segwit.
>
>
> Should we be forcing miners to choose to run non-core code in order to
> activate a popular feature?
>
> - Erik
>
> _______________________________________________
> bitcoin-dev mailing list
> bitcoin-dev@lists•linuxfoundation.org
> https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev
>
>
[-- Attachment #2: Type: text/html, Size: 1522 bytes --]
next prev parent reply other threads:[~2017-06-20 16:49 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 [this message]
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
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='CAFMkqK_OtZ=S5LFqERCYwSQCkbxdnWJq+wN-YM3CVkKWJx2SBA@mail.gmail.com' \
--to=hampus.sjoberg@gmail$(echo .)com \
--cc=bitcoin-dev@lists$(echo .)linuxfoundation.org \
--cc=erik@q32$(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