1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
|
Return-Path: <jtimon@jtimon.cc>
Received: from smtp1.linuxfoundation.org (smtp1.linux-foundation.org
[172.17.192.35])
by mail.linuxfoundation.org (Postfix) with ESMTPS id 31418C4A
for <bitcoin-dev@lists.linuxfoundation.org>;
Thu, 10 Mar 2016 15:46:59 +0000 (UTC)
X-Greylist: whitelisted by SQLgrey-1.7.6
Received: from mail-vk0-f46.google.com (mail-vk0-f46.google.com
[209.85.213.46])
by smtp1.linuxfoundation.org (Postfix) with ESMTPS id 7E28A13F
for <bitcoin-dev@lists.linuxfoundation.org>;
Thu, 10 Mar 2016 15:46:58 +0000 (UTC)
Received: by mail-vk0-f46.google.com with SMTP id e185so100097460vkb.1
for <bitcoin-dev@lists.linuxfoundation.org>;
Thu, 10 Mar 2016 07:46:58 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
d=jtimon-cc.20150623.gappssmtp.com; s=20150623;
h=mime-version:in-reply-to:references:date:message-id:subject:from:to
:cc; bh=igYIOb8PkFzUCbRP+imi+qydelG8pbVxpt008yZp70g=;
b=qoN/d90HRqLRWGbLBOxecZPAFTNSq6Eun8k2FVBqOD3bT9CX7rUnZ9+K50AIK6LCxo
j5kRsspwEzQSfxYKzUCSy8BbXXWtuCqvzI9WRKjSpDWDBvce4z8DdGdg0McPmKJUNn0Z
pgqgE8qGqjdKp2LJkNaB8JkG8yD6MDPHYvO+TptA/LNBD1zAix1A9xNgqFa2xezLpiWo
tOSCEKTZtIdrtW4I8sF+CofTFYtDdjhiXBxaHJ2gGIpPFrhwnVB7yR5DgN6rNCo+DuhO
5O32d1hdzCdnXw6tjYW5YNV82TX8nCsPmulT5fz726flFxP/iPNUFL66uHrutSNr/wCY
TblQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
d=1e100.net; s=20130820;
h=x-gm-message-state:mime-version:in-reply-to:references:date
:message-id:subject:from:to:cc;
bh=igYIOb8PkFzUCbRP+imi+qydelG8pbVxpt008yZp70g=;
b=eDoZYFNCl4FTQxke1MQBclXB//DA4PNSwL0YhVpeZa95QpW0/RL+Kvg1ApuAuIoJAG
jJWbxXQxsZRYyhmR358qeWdfQAef8UKcumY/fWPuShC6FKgybNH/9mRMrgmcWx2tWUVv
Xe7Szvnzser3jpFhKGiYaKZIZfWCxUYPoMWs0emxbB7LBuAOFGNJNHkvClNL8hupbTs2
Zs03gV1UsrnKj9MvBlePVAn1xXVy8BAyMVgCFWNpeVWG8WKvxZ/YBX4h+9V0nPIyvT7d
zZFpVHp0ENT3isvAf3Y7bUN8TCOMJtqicjPRhsmjeYnaehAF4LEoJDMVtDzEWt5p/MxR
/YWw==
X-Gm-Message-State: AD7BkJK6IKXIdgz2pdGCavQcnpj6krURHTS6ryQxvvs2E1s0B3eIQ4kXShZ1HSOrt/wCbf9jvT9+5+PpjGPAFA==
MIME-Version: 1.0
X-Received: by 10.31.1.138 with SMTP id 132mr4155264vkb.140.1457624817676;
Thu, 10 Mar 2016 07:46:57 -0800 (PST)
Received: by 10.31.141.73 with HTTP; Thu, 10 Mar 2016 07:46:57 -0800 (PST)
Received: by 10.31.141.73 with HTTP; Thu, 10 Mar 2016 07:46:57 -0800 (PST)
In-Reply-To: <56E0C197.7040708@musalbas.com>
References: <201603081904.28687.luke@dashjr.org>
<56E0C197.7040708@musalbas.com>
Date: Thu, 10 Mar 2016 16:46:57 +0100
Message-ID: <CABm2gDo5eLgr5DhESWp9Bg4JLAq9TS+PX8=PepKAi0tC+bxWSw@mail.gmail.com>
From: =?UTF-8?B?Sm9yZ2UgVGltw7Nu?= <jtimon@jtimon.cc>
To: Mustafa Al-Bassam <mus@musalbas.com>
Content-Type: multipart/alternative; boundary=001a113da7dc794dbf052db3b952
X-Spam-Status: No, score=-2.6 required=5.0 tests=BAYES_00,DKIM_SIGNED,
DKIM_VALID,HTML_MESSAGE,RCVD_IN_DNSWL_LOW autolearn=ham version=3.3.1
X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on
smtp1.linux-foundation.org
X-Mailman-Approved-At: Thu, 10 Mar 2016 15:51:49 +0000
Cc: Bitcoin Dev <bitcoin-dev@lists.linuxfoundation.org>
Subject: Re: [bitcoin-dev] BIP 2 promotion to Final
X-BeenThere: bitcoin-dev@lists.linuxfoundation.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Bitcoin Development Discussion <bitcoin-dev.lists.linuxfoundation.org>
List-Unsubscribe: <https://lists.linuxfoundation.org/mailman/options/bitcoin-dev>,
<mailto:bitcoin-dev-request@lists.linuxfoundation.org?subject=unsubscribe>
List-Archive: <http://lists.linuxfoundation.org/pipermail/bitcoin-dev/>
List-Post: <mailto:bitcoin-dev@lists.linuxfoundation.org>
List-Help: <mailto:bitcoin-dev-request@lists.linuxfoundation.org?subject=help>
List-Subscribe: <https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev>,
<mailto:bitcoin-dev-request@lists.linuxfoundation.org?subject=subscribe>
X-List-Received-Date: Thu, 10 Mar 2016 15:46:59 -0000
--001a113da7dc794dbf052db3b952
Content-Type: text/plain; charset=UTF-8
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.
--001a113da7dc794dbf052db3b952
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
<p dir=3D"ltr"><br>
On Mar 10, 2016 02:04, "Mustafa Al-Bassam via bitcoin-dev" <<a=
href=3D"mailto:bitcoin-dev@lists.linuxfoundation.org">bitcoin-dev@lists.li=
nuxfoundation.org</a>> wrote:<br>
><br>
> >A hard-fork BIP requires adoption from the entire Bitcoin economy,=
<br>
> particularly including those selling desirable goods and services in<b=
r>
> exchange for bitcoin payments, as well as Bitcoin holders who wish to<=
br>
> spend or would spend their bitcoins (including selling for other<br>
> currencies) differently in the event of such a hard-fork.<br>
> What if one shop owner, for example, out of thousands, doesn't ada=
pt the<br>
> hard-fork? It is expected, and should perhaps be encouraged, for a sma=
ll<br>
> minority to not accept a hard fork, but by the wording of the BIP<br>
> ("entire Bitcoin economy"), one shop owner can veto a hard-f=
ork.</p>
<p dir=3D"ltr">No, the hardfork can still happen, but if a small group rema=
ins 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 usin=
g the old chain, a hardfork BIP shouldn't become final if I understood =
BIP2 correctly. </p>
<p dir=3D"ltr">In other words,=C2=A0 uncontroversial hardfork bips can make=
it to the final state once deployed, controversial hardforks may never bec=
ome universally deployed.</p>
--001a113da7dc794dbf052db3b952--
|
