From: "Jorge Timón" <jtimon@jtimon•cc>
To: Mustafa Al-Bassam <mus@musalbas•com>
Cc: Bitcoin Dev <bitcoin-dev@lists•linuxfoundation.org>
Subject: Re: [bitcoin-dev] BIP 2 promotion to Final
Date: Thu, 10 Mar 2016 16:46:57 +0100 [thread overview]
Message-ID: <CABm2gDo5eLgr5DhESWp9Bg4JLAq9TS+PX8=PepKAi0tC+bxWSw@mail.gmail.com> (raw)
In-Reply-To: <56E0C197.7040708@musalbas.com>
[-- Attachment #1: Type: text/plain, Size: 1256 bytes --]
On Mar 10, 2016 02:04, "Mustafa Al-Bassam via bitcoin-dev" <
bitcoin-dev@lists•linuxfoundation.org> wrote:
>
> >A hard-fork BIP requires adoption from the entire Bitcoin economy,
> particularly including those selling desirable goods and services in
> exchange for bitcoin payments, as well as Bitcoin holders who wish to
> spend or would spend their bitcoins (including selling for other
> currencies) differently in the event of such a hard-fork.
> What if one shop owner, for example, out of thousands, doesn't adapt the
> hard-fork? It is expected, and should perhaps be encouraged, for a small
> minority to not accept a hard fork, but by the wording of the BIP
> ("entire Bitcoin economy"), one shop owner can veto a hard-fork.
No, the hardfork can still happen, but if a small group remains using the
old chain (a single person will likely abandon it very soon), then it
cannot be said that deployment was universal and thus the hardfork BIP
doesn't move to the final state. As long as there's users using the old
chain, a hardfork BIP shouldn't become final if I understood BIP2
correctly.
In other words, uncontroversial hardfork bips can make it to the final
state once deployed, controversial hardforks may never become universally
deployed.
[-- Attachment #2: Type: text/html, Size: 1499 bytes --]
next prev parent reply other threads:[~2016-03-10 15:46 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-08 19:04 Luke Dashjr
2016-03-10 0:36 ` Mustafa Al-Bassam
2016-03-10 15:46 ` Jorge Timón [this message]
[not found] ` <56E0BFDC.5070604@musalbas.com>
[not found] ` <201603100053.43822.luke@dashjr.org>
2016-03-10 14:02 ` Mustafa Al-Bassam
2016-03-10 15:59 ` Jorge Timón
2016-03-10 16:28 ` Mustafa Al-Bassam
2016-03-10 16:33 ` Mustafa Al-Bassam
2016-03-10 18:30 ` Jorge Timón
2016-03-10 16:43 ` Luke Dashjr
2016-03-16 20:43 ` Btc Drak
2016-03-16 22:24 ` Luke Dashjr
2016-03-18 9:42 ` Btc Drak
2016-03-18 19:34 ` Luke Dashjr
2016-03-18 22:52 ` David A. Harding
2016-03-18 11:59 ` Tom
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='CABm2gDo5eLgr5DhESWp9Bg4JLAq9TS+PX8=PepKAi0tC+bxWSw@mail.gmail.com' \
--to=jtimon@jtimon$(echo .)cc \
--cc=bitcoin-dev@lists$(echo .)linuxfoundation.org \
--cc=mus@musalbas$(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