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
|
Return-Path: <nxtchg@hush.com>
Received: from smtp1.linuxfoundation.org (smtp1.linux-foundation.org
[172.17.192.35])
by mail.linuxfoundation.org (Postfix) with ESMTPS id 4ACBDBBC
for <bitcoin-dev@lists.linuxfoundation.org>;
Wed, 1 Jul 2015 08:45:13 +0000 (UTC)
X-Greylist: from auto-whitelisted by SQLgrey-1.7.6
Received: from smtp1.hushmail.com (smtp1.hushmail.com [65.39.178.135])
by smtp1.linuxfoundation.org (Postfix) with ESMTPS id E9BDE164
for <bitcoin-dev@lists.linuxfoundation.org>;
Wed, 1 Jul 2015 08:45:12 +0000 (UTC)
Received: from smtp1.hushmail.com (localhost [127.0.0.1])
by smtp1.hushmail.com (Postfix) with SMTP id 7A57840114
for <bitcoin-dev@lists.linuxfoundation.org>;
Wed, 1 Jul 2015 08:45:12 +0000 (UTC)
Received: from smtp.hushmail.com (w7.hushmail.com [65.39.178.32])
by smtp1.hushmail.com (Postfix) with ESMTP
for <bitcoin-dev@lists.linuxfoundation.org>;
Wed, 1 Jul 2015 08:45:12 +0000 (UTC)
Received: by smtp.hushmail.com (Postfix, from userid 99)
id 5924041A40; Wed, 1 Jul 2015 08:45:12 +0000 (UTC)
MIME-Version: 1.0
Date: Wed, 01 Jul 2015 11:45:12 +0300
To: "bitcoin-dev" <bitcoin-dev@lists.linuxfoundation.org>
From: "NxtChg" <nxtchg@hush.com>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="UTF-8"
Message-Id: <20150701084512.5924041A40@smtp.hushmail.com>
X-Spam-Status: No, score=-0.7 required=5.0 tests=BAYES_40,FREEMAIL_FROM,
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
Subject: [bitcoin-dev] Bitcoin governance
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: Wed, 01 Jul 2015 08:45:13 -0000
(sorry for the long post, I tried)
I've been thinking about how we could build an effective Bitcoin governance, but couldn't come up with anything remotely plausible.
It seems we might go a different way, though, with Core and XT continue co-existing in parallel, mostly in a compatible state, out of the need that "there can be only one".
Both having the same technical protocol, but different people, structure, processes and political standing; serving as a kind of two-party system and keeping each other in check.
Their respective power will be determined by the number of Core vs XT nodes running and people/businesses on board. They will have to negotiate any significant change at the risk of yet another full fork.
And occasionally the full forks will still happen and the minority will have to concede and change their protocol to match the winning side.
Can there be any other way? Can you really control a decentralized system with a centralized governance, like Core Devs or TBF?
----
In this view, what's happening is a step _towards_ decentralization, not away from it. It proves that Bitcoin is indeed a decentralized system and that minority cannot impose its will.
For the sides to agree now would actually be a bad thing, because that would mean kicking the governance problem down the road.
And we _need_ to go through this painful split at least once. The block size issue is perfect: controversial enough to push the split, but not controversial enough so one side couldn't win.
----
If this is where we're heading then both sides should probably start thinking of themselves as opposition parties, instead of whatever they think of themselves now.
People and businesses ultimately decide and they need a way to cast a Yes/No vote on proposed changes. Hence the two-party system.
If the split in power is, say, 60/40 and the leading party introduces an unpopular change, it can quickly lose its advantage.
We already have the "democratic party" on the left with Gavin and Mike representing the wish of the majority and the "conservative party" on the right, who would prefer things to stay the way they are.
----
Finally, I propose to improve the voting mechanism of Bitcoin to serve this new reality better.
Using the upcoming fork as an opportunity, we could add something like 8-byte votes into blocks:
* first 4 bytes: fork/party ID, like 'CORE' or 'XT'
* second 4 bytes: proposition number
(or at least add the ID somewhere so the parties wouldn't have to negotiate block version numbers).
Miners are in the business of mining coins, so they are good "sensors" of where the economic majority will be.
We will have a representative democracy, with miners serving as 'hubs', collecting all the noise and chatter and casting it into a vote.
This is not perfect, but nothing ever is.
|