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
|
Return-Path: <pieter.wuille@gmail.com>
Received: from smtp1.linuxfoundation.org (smtp1.linux-foundation.org
[172.17.192.35])
by mail.linuxfoundation.org (Postfix) with ESMTPS id 33104B0B
for <bitcoin-dev@lists.linuxfoundation.org>;
Tue, 28 Mar 2017 20:16:06 +0000 (UTC)
X-Greylist: whitelisted by SQLgrey-1.7.6
Received: from mail-wr0-f176.google.com (mail-wr0-f176.google.com
[209.85.128.176])
by smtp1.linuxfoundation.org (Postfix) with ESMTPS id 86A5ACB
for <bitcoin-dev@lists.linuxfoundation.org>;
Tue, 28 Mar 2017 20:16:05 +0000 (UTC)
Received: by mail-wr0-f176.google.com with SMTP id w11so95666552wrc.3
for <bitcoin-dev@lists.linuxfoundation.org>;
Tue, 28 Mar 2017 13:16:05 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;
h=mime-version:in-reply-to:references:from:date:message-id:subject:to;
bh=THpmODLT5/f7twzqPJrR40T+nuo4qJa2ySCJFsOH6qs=;
b=JvfcneRvnVjEjk93eTJek2fYurl9lSYa9dCQ6OgG6b5jrBYYgGS9XkBvyN1vvzwyMm
NguxXAxcuwTKyEyXebFI1ci9L0arDs4yVqkoPaRY3mczlKi2mv1S+bhnERUECDo7XLHh
1YI8ZswygOpcGAx7N6uQG2u+7WtT1954RuNm3WkDT/je+o5wqbYsctLtsV2AV7DK4a+0
Wvj3KCwdNMQyvcIG4ZoNaOlK0/QkmBka3oe4OHTpL30pYuMZCCmIaMx2ZZBEWEO9DxlR
R1l5by7cTh6jV5eVxGIruJkpoOzFaTS3QqBnZ414nyDB/ns+aGp3VhqunPdPVrsOlfz7
OEcQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
d=1e100.net; s=20161025;
h=x-gm-message-state:mime-version:in-reply-to:references:from:date
:message-id:subject:to;
bh=THpmODLT5/f7twzqPJrR40T+nuo4qJa2ySCJFsOH6qs=;
b=FE7H0bGfRN2h7cQbSH0s+iILjec2oA3zAsF6XfTYUm2PvGBOsyK++ZFvNd0vwwq9fU
mQU4L+keb2qrVu/T1n6HcoJ1Y5G2N9YVzKSzbaoaq2TjDPA8c9SbSRSBpXP6Y+85Mjcc
PfPjbLhgTkeoP3gBGSJwyuRwVl6pl6yCaEIma6HlFtAtlthpCN3iud3rB7bhgxO/W9M2
Sb4ACsj/LpgomRj7MuyOV87Tw4nA8hOHIkUADqPF2QCsy4k4ORI0CQ7opzJZXoiFlln+
2XQvMsUs6qdvXSjEfdM0Z0gYK62e4NgDVjXTsh2CtFZB7hdjKbDoWiv4k9fn5o+zSBeS
x8Uw==
X-Gm-Message-State: AFeK/H1XQpNyc61sN7+ZYNjypMLRVoMsJ+I0XvwgEDtiVEGlzkZkrgtXSdkdyEAJLbCL2hha3lbxR25/GsRCKw==
X-Received: by 10.223.165.29 with SMTP id i29mr5148660wrb.43.1490732164208;
Tue, 28 Mar 2017 13:16:04 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.80.135.5 with HTTP; Tue, 28 Mar 2017 13:16:03 -0700 (PDT)
In-Reply-To: <CAAeo5+jSfp5XWj=EYJ_i-XS+=RjxfY-co7+b7iu3Gd=WWHbHzQ@mail.gmail.com>
References: <CAAeo5+jSfp5XWj=EYJ_i-XS+=RjxfY-co7+b7iu3Gd=WWHbHzQ@mail.gmail.com>
From: Pieter Wuille <pieter.wuille@gmail.com>
Date: Tue, 28 Mar 2017 13:16:03 -0700
Message-ID: <CAPg+sBgy6CTjgc-kjAdYSUXgDm4WfRbAzxwd_Csj1mWhCOSQMA@mail.gmail.com>
To: Paul Iverson <piverson1024@gmail.com>,
Bitcoin Protocol Discussion <bitcoin-dev@lists.linuxfoundation.org>
Content-Type: text/plain; charset=UTF-8
X-Spam-Status: No, score=-2.0 required=5.0 tests=BAYES_00,DKIM_SIGNED,
DKIM_VALID, DKIM_VALID_AU, FREEMAIL_FROM,
RCVD_IN_DNSWL_NONE autolearn=ham version=3.3.1
X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on
smtp1.linux-foundation.org
Subject: Re: [bitcoin-dev] Hard fork proposal from last week's meeting
X-BeenThere: bitcoin-dev@lists.linuxfoundation.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Bitcoin Protocol 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: Tue, 28 Mar 2017 20:16:06 -0000
On Tue, Mar 28, 2017 at 12:56 PM, Paul Iverson via bitcoin-dev
<bitcoin-dev@lists.linuxfoundation.org> wrote:
> So I think Core can't decide on hard forks like this. It must be left up to
> the users. I think only choice is for Core to add a run-time option to allow
> node operators to increase block size limit, so that this very controversial
> decision is not coming from Core. It must come from the community.
Bitcoin Core's (nor any other software's) maintainers can already not
decide on a hard fork, and I keep being confused by the focus on Core
in this topic. Even if a hard forking change (or lack thereof) was
included into a new release, it is still up to the community to choose
to run the new software. Bitcoin Core has very intentionally no
auto-update feature, as the choice for what network rules to implement
must come from node operators, not developers. Ask yourself this: if a
new Bitcoin Core release would include a new rule that blacklists
<random famous person>'s coins. What do you think would happen? I hope
that people would refuse to update, and choose to run different full
node software.
Core is not special. It is one of many pieces of software that
implement today's Bitcoin consensus rules. If a hardfork is to take
place in a way that does not result in two currencies, it must be
clear that the entire ecosystem will adopt it. Bitcoin Core will not
merge any consensus changes that do not clearly satisfy that
criterion.
--
Pieter
|
