From: Tom Zander <tomz@freedommail•ch>
To: bitcoin-dev@lists•linuxfoundation.org, Luke Dashjr <luke@dashjr•org>
Subject: Re: [bitcoin-dev] BIP proposal: Generalized version bits voting (bip-genvbvoting)
Date: Wed, 05 Apr 2017 12:08:51 +0200 [thread overview]
Message-ID: <2796215.bJP4rN4KYZ@strawberry> (raw)
In-Reply-To: <201704041801.51655.luke@dashjr.org>
On Tuesday, 4 April 2017 20:01:51 CEST Luke Dashjr via bitcoin-dev wrote:
> BIP 9 provides a mechanism for having
> miners coordinate softforks because they can make the upgrade process
> smoother this way. But the same is not true of hardforks: miners are
> essentially irrelevant to them, and cannot make the process any smoother.
Can you explain how miners are irrelevant if the upgrade is not a soft fork?
--
Tom Zander
Blog: https://zander.github.io
Vlog: https://vimeo.com/channels/tomscryptochannel
next prev parent reply other threads:[~2017-04-05 10:08 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-03 9:06 Sancho Panza
2017-04-04 11:16 ` Tom Zander
2017-04-04 16:41 ` Sancho Panza
2017-04-04 16:49 ` Sancho Panza
2017-04-04 18:01 ` Luke Dashjr
2017-04-04 19:28 ` Sancho Panza
2017-04-05 10:08 ` Tom Zander [this message]
2017-04-05 14:09 ` Thomas Kerin
2017-04-08 21:58 ` Sancho Panza
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=2796215.bJP4rN4KYZ@strawberry \
--to=tomz@freedommail$(echo .)ch \
--cc=bitcoin-dev@lists$(echo .)linuxfoundation.org \
--cc=luke@dashjr$(echo .)org \
/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