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
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
|
Return-Path: <eric@voskuil.org>
Received: from smtp1.linuxfoundation.org (smtp1.linux-foundation.org
[172.17.192.35])
by mail.linuxfoundation.org (Postfix) with ESMTPS id 149729C
for <bitcoin-dev@lists.linuxfoundation.org>;
Sun, 16 Aug 2015 20:29:45 +0000 (UTC)
X-Greylist: whitelisted by SQLgrey-1.7.6
Received: from mail-pa0-f49.google.com (mail-pa0-f49.google.com
[209.85.220.49])
by smtp1.linuxfoundation.org (Postfix) with ESMTPS id 76AE2118
for <bitcoin-dev@lists.linuxfoundation.org>;
Sun, 16 Aug 2015 20:29:43 +0000 (UTC)
Received: by pabyb7 with SMTP id yb7so93278079pab.0
for <bitcoin-dev@lists.linuxfoundation.org>;
Sun, 16 Aug 2015 13:29:43 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
d=1e100.net; s=20130820;
h=x-gm-message-state:message-id:date:from:user-agent:mime-version:to
:subject:references:in-reply-to:content-type;
bh=cnSR8ZJ4YCQ2HwCm3TMxXERFWj6aynhmgycNTcn9n7g=;
b=EnJKAp1+kjLmKGtsG9zDwKyG3du7fbfdhNoyaE2Ok17nKpmLrYJdwaQUMO9y2OHx7D
RivcL0mLEAp7KVc5PN3EZMv2NZrx1bN3xjL6+dR1dfSUTjwR28dNXTZfxgGEucJsIf33
HE5pFFBxbYgEALOP3f6QecZdY1SvPDIsOSdSo8jkLYdzA3d2G9XebxbdYzOLUN9aHhZ6
artOv1sVDloLofyePqqR3tYzFKArQggJjFO8Mmyz0a1Q859r7Sm8J/thSZexiOyOS/3F
VBW8C/n5l1xxemP78R+OrrcUQiagr7/SmtobCeDy2x6Xnl6/W3UqI+atWDU8junmeund
D/7A==
X-Gm-Message-State: ALoCoQkoHVv5DmhByqTnzkhwCn7BA9ahwXXDx1rK6YY/s3G16f7iLYCGwqRuBH7RQ9m7rifD9UwD
X-Received: by 10.68.95.4 with SMTP id dg4mr111126143pbb.132.1439756983171;
Sun, 16 Aug 2015 13:29:43 -0700 (PDT)
Received: from [10.0.1.13] (c-73-225-134-208.hsd1.wa.comcast.net.
[73.225.134.208]) by smtp.googlemail.com with ESMTPSA id
hb1sm12197838pbd.36.2015.08.16.13.29.42
(version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128);
Sun, 16 Aug 2015 13:29:42 -0700 (PDT)
Message-ID: <55D0F23D.8030302@voskuil.org>
Date: Sun, 16 Aug 2015 13:27:41 -0700
From: Eric Voskuil <eric@voskuil.org>
User-Agent: Mozilla/5.0 (X11; Linux x86_64;
rv:31.0) Gecko/20100101 Thunderbird/31.2.0
MIME-Version: 1.0
To: Bitcoin Dev <bitcoin-dev@lists.linuxfoundation.org>,
Libbitcoin <libbitcoin@lists.dyne.org>
References: <CA+w+GKT7t5OahS-+P=QAmOyFzPnOs4J6KSo+mhSrC0YggmMupg@mail.gmail.com>
In-Reply-To: <CA+w+GKT7t5OahS-+P=QAmOyFzPnOs4J6KSo+mhSrC0YggmMupg@mail.gmail.com>
Content-Type: multipart/signed; micalg=pgp-sha1;
protocol="application/pgp-signature";
boundary="3kc3Brv7BRDRm4oejmrUQ6g5eaxTQtod5"
X-Spam-Status: No, score=-2.6 required=5.0 tests=BAYES_00,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: Re: [bitcoin-dev] Bitcoin XT 0.11A
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: Sun, 16 Aug 2015 20:29:45 -0000
This is an OpenPGP/MIME signed message (RFC 4880 and 3156)
--3kc3Brv7BRDRm4oejmrUQ6g5eaxTQtod5
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: quoted-printable
[cross-posted to libbitcoin]
I applaud this effort not for the merits of the hard fork but on the
effects of the code fork. We have been witnessing the self-destruction
of Bitcoin's central authority. This is a necessary outcome.
Understandably, many are concerned that if consensus settles on a larger
block size Bitcoin will suffer greater centralization. The point of
Bitcoin however is that nobody is in control of consensus. If a
consensus decision leads to centralization, the consensus will move.
Yes, when this happens people who bet on the losing fork will lose
money. This is how Bitcoin works. One bets not on personal desires but
on what others will accept. That is how consensus is built.
Some fret that if this process evolves Bitcoin will suffer a
catastrophic loss of "value" and not recover. This may come to pass, but
there is no avoiding the possibility.
The ease with which consensus can move when it wants to is important. In
other words, friction is weakness and a single overly complex codebase
is high friction.
Amir saw this coming before most. While we are posting manifestos, I
thought it more than appropriate to quote from the libbitcoin manifesto:
> If development is too centralised, with a small core infrastructure,
> then businesses will put real pressure to have features that destroy
> the integrity of the Bitcoin network.
> ...
> The possible malicious scenarios are endless....At the other end of
> the spectrum, is putting development effort into diversifying the
> ecosystem to protect against censorship... That's where developers
> who believe in Bitcoin should devote time to.
> ...
> A diversified Bitcoin of many wallets and implementations is a strong
> and pure Bitcoin. To protect the integrity of the network, we need to
> eliminate single points of failure. An inbred Bitcoin with the same
> software code everywhere shares the same weaknesses, and is
> susceptible to the same attacks...
>
> The implications of a diversified Bitcoin is a Bitcoin difficult to
> control. It also sets the protocol in stone, as nobody has sole power
> over the standard. Consensus from many parties is the way forwards.
>...
> Viewed over a longer time period, extra or unnecessary features seem
> to creep into the system beyond the initial goals and the small code
> of 15,000 lines set by Satoshi. The result will be a Bitcoin that
> becomes increasingly difficult to understand or implement without a
> huge initial investment of resources, time and people. No single
> person will fully understand Bitcoin anymore, and development
> monopolies will be further enforced.
http://libbitcoin.dyne.org/libbitcoin-manifesto.pdf
e
On 08/15/2015 10:02 AM, Mike Hearn via bitcoin-dev wrote:
> Hello,
>=20
> As promised, we have released Bitcoin XT 0.11A which includes the bigge=
r
> blocks patch set. You can get it from
>=20
> https://bitcoinxt.software/
>=20
> I feel sad that it's come to this, but there is no other way. The
> Bitcoin Core project has drifted so far from the principles myself and
> many others feel are important, that a fork is the only way to fix thin=
gs.
>=20
> Forking is a natural thing in the open source community, Bitcoin is not=
> the first and won't be the last project to go through this. Often in
> forks, people say there was insufficient communication. So to ensure
> everything is crystal clear I've written a blog post and a kind of
> "manifesto" to describe why this is happening and how XT plans to be
> different from Core (assuming adoption, of course).
>=20
> The article is here:
>=20
> https://medium.com/@octskyward/why-is-bitcoin-forking-d647312d22c1
>=20
> It makes no attempt to be neutral: this explains things from our point
> of view.
>=20
> The manifesto is on the website.
>=20
> I say to all developers on this list: if you also feel that Core is no
> longer serving the interests of Bitcoin users, come join us. We don't b=
ite.
> ________________________________________
> bitcoin-dev mailing list
> bitcoin-dev@lists.linuxfoundation.org
> https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev
>=20
--3kc3Brv7BRDRm4oejmrUQ6g5eaxTQtod5
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1
iQEcBAEBAgAGBQJV0PI9AAoJEDzYwH8LXOFOxxcH/0K2K5PINapfqJiLS8uReoBd
ql31HlK8jthecUlA60AkCI8hQtx6B6lttafBts0BKVWdcfwOV9tlV9b1zz2Vtj3i
ZiWIvvBJlCaAedIh8uJfHVIk2yv4+gVI68JG3ivygG4LN98AyUKnCb4BnpamAvM0
V4GoU+LIm97Tz1gudzTCtz80aGGlWQu4mLGZuYaYEpp9hzp3x2SkMuI2AgN7CeZJ
0+bfxEmz7+InnFUQdf92JlV9Z2+dKxle/oWoNvZ59iadICfhjzNYaj5KHfm+Hb0B
WtjMHdwEYPe+ccP7ikSjRJ5VHmBEIhoPrQD/p3mtVoOTDFJPVgEloaD+/sjJvh8=
=Oi8L
-----END PGP SIGNATURE-----
--3kc3Brv7BRDRm4oejmrUQ6g5eaxTQtod5--
|
