From: Erik Aronesty <erik@q32.com>
To: Bitcoin Protocol Discussion <bitcoin-dev@lists.linuxfoundation.org>
Subject: [bitcoin-dev] Miners forced to run non-core code in order to get segwit activated
Date: Tue, 20 Jun 2017 11:44:36 -0400 [thread overview]
Message-ID: <CAJowKgLtu-HUDuakk4DDU53nyChbQk_zY=f5OO2j1Za95PdL7w@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 353 bytes --]
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
[-- Attachment #2: Type: text/html, Size: 401 bytes --]
next reply other threads:[~2017-06-20 15:44 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-20 15:44 Erik Aronesty [this message]
2017-06-20 16:49 ` [bitcoin-dev] Miners forced to run non-core code in order to get segwit activated 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
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='CAJowKgLtu-HUDuakk4DDU53nyChbQk_zY=f5OO2j1Za95PdL7w@mail.gmail.com' \
--to=erik@q32.com \
--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