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
|
Return-Path: <s7r@sky-ip.org>
Received: from smtp1.linuxfoundation.org (smtp1.linux-foundation.org
[172.17.192.35])
by mail.linuxfoundation.org (Postfix) with ESMTPS id EC411140E
for <bitcoin-dev@lists.linuxfoundation.org>;
Tue, 1 Sep 2015 22:06:52 +0000 (UTC)
X-Greylist: from auto-whitelisted by SQLgrey-1.7.6
Received: from outbound.mailhostbox.com (outbound.mailhostbox.com
[162.222.225.22])
by smtp1.linuxfoundation.org (Postfix) with ESMTP id 9C9F515E
for <bitcoin-dev@lists.linuxfoundation.org>;
Tue, 1 Sep 2015 22:06:44 +0000 (UTC)
Received: from [0.0.0.0] (manning1.torservers.net [96.44.189.100])
(using TLSv1 with cipher DHE-RSA-AES128-SHA (128/128 bits))
(No client certificate requested)
(Authenticated sender: s7r@sky-ip.org)
by outbound.mailhostbox.com (Postfix) with ESMTPSA id A4C15784AE5;
Tue, 1 Sep 2015 22:06:39 +0000 (GMT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sky-ip.org;
s=20110108; t=1441145202;
bh=frzxE0801XuiwqGpJRFn3JIeUjG47Z7f7+7bXi0FJdg=;
h=Reply-To:Subject:References:To:Cc:From:Date:In-Reply-To;
b=LIRrTFxPgMEdVY+fIFY+I88DccKxHaeypm6wjDF7pcbsB75upmuYme5uOrswNCfq5
hikNHbgprjC+uxiQZONUeQMdGT25uwNAeGGmgRngOjZKX/KMYhyL8PWJxnewNzgxgY
YhgPeMzcFpxXlXA40b/j150EIHx6GkNHP+gkiyqo=
Reply-To: s7r@sky-ip.org
References: <602b978abcedd92fbed85f305d9d7bfe@cock.li>
<55E4B8C9.5030606@openbitcoinprivacyproject.org>
<e786da226b8e9cfaad335454b299ffd5@cock.li>
<CAJfRnm4kwHkBLUUOmfzViUwsdAf3LYSTruvHw9+-RbgxSMHLRg@mail.gmail.com>
<5A3D7824-F1E3-421B-A32A-0EF21DD215BD@gmx.com>
<55E4E7AA.6010905@sky-ip.org>
<CC252814-9AF6-4A28-926E-EE83C517E440@gmx.com>
To: Peter R <peter_r@gmx.com>
From: s7r <s7r@sky-ip.org>
X-Enigmail-Draft-Status: N1110
Message-ID: <55E6216B.8080803@sky-ip.org>
Date: Wed, 2 Sep 2015 01:06:35 +0300
User-Agent: Mozilla/5.0 (Windows NT 6.3; WOW64; rv:38.0) Gecko/20100101
Thunderbird/38.2.0
MIME-Version: 1.0
In-Reply-To: <CC252814-9AF6-4A28-926E-EE83C517E440@gmx.com>
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: 8bit
X-CMAE-Score: 0
X-CMAE-Analysis: v=2.1 cv=IYN6Ijea c=1 sm=1 tr=0
a=s8xZHfdCR1WDCFMteBX5PQ==:117 a=s8xZHfdCR1WDCFMteBX5PQ==:17
a=N659UExz7-8A:10 a=O7_YbJL8sSE6xpMSzOQA:9 a=pILNOxqGKmIA:10
X-Spam-Status: No, score=-0.3 required=5.0 tests=BAYES_00,DKIM_SIGNED,
DKIM_VALID,DKIM_VALID_AU,URIBL_BLACK autolearn=no version=3.3.1
X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on
smtp1.linux-foundation.org
Cc: bitcoin-dev@lists.linuxfoundation.org
Subject: Re: [bitcoin-dev] Let's kill Bitcoin Core and allow the green
shoots of a garden of new implementations to grow from its fertile ashes
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: Tue, 01 Sep 2015 22:06:53 -0000
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
That would be very wrong and cause a lot of problems and 'political
chaos' without solving at least one (technical) problem in exchange.
Bitcoin Core is a good quality code. It is open source and free.
Anyone can contribute and submit small changes, improvements.
Controversial changes are not easily merged not because the
maintainers do not want, but because they represent a threat to the
entire ecosystem, one way or the other. We have to very carefully
balance the gains and the risks. If we try to never reach a consensus
on purpose, this will only cause instability, and a possible result
could be that we will end up having many more weaker implementations
running in the network, decreasing the security overall and for everyone.
While I do agree with some of your points of view and I am happy to
see you advocate for 'more decentralization', please let me point you
in a better direction (I think): there is a much bigger problem than >
~90% of the full nodes running Bitcoin Core software - it is
*centralized mining (e.g. a lot of hashing power behind a single full
mining node)*.
On 9/1/2015 5:16 AM, Peter R wrote:
> I agree, s7r, that Bitcoin Core represents the most stable code
> base. To create multiple implementations, other groups would fork
> Bitcoin Core similar to what Bitcoin XT did. We could have:
>
> - Bitcoin-A (XT) - Bitcoin-B (Blockstream) - Bitcoin-C (promoting
> BIP100) - Bitcoin-D - etc.
>
> Innovation from any development group would be freely integrated by
> any other development group, if desired. Of course, each group
> would have a very strong incentive to remain fork-wise compatible
> with the other implementations.
>
> In fact, this just gave me a great idea! Since Wladimir has stated
> that he will not integrate a forking change into Core without Core
> Dev consensus, *I suggest we work together to never reach consensus
> with Bitcoin Core. *This will provide impetus for new
> implementations to fork from Core (like XT did) and implement
> whatever scaling solution they deem best. The users will then
> select the winning solution simply based on the code they choose to
> run. The other implementations will then rush to make compatible
> changes in order to keep their dwindling user bases.
>
> This is the decentralized spirit of Bitcoin in action. Creative
> destruction. Consensus formed simply by the code that gets run.
>
> *Let's kill Bitcoin Core and allow the green shoots of a garden of
> new implementations to grow from its fertile ashes. *
>
> Sincerely, Peter R
>
>
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.22 (MingW32)
iQEcBAEBCAAGBQJV5iFqAAoJEIN/pSyBJlsRMvIH/RiE8BhlXPbNOQW01HBJTBOD
3H4bgaZoXuxSq2B1F4zKa/FvKJKtq7BGR3hLEj5tascqZTE2YsksRqmEednFNvbL
XOliCjees6nI/oz/aYFuz9rFoKH4cxA7bJmbvieqGSOqDt7rtClaO2JzBycilngS
F5pVGjKlprprTn4XUS8R40rfYVFbYyxaMnWBOnkgEpEAbtEvNRcASSW4HQoxuGRL
6E8mzp8f23zAv6ENxKEfQoIf5SBBfYf8v2xV+YY9JcFjwh4MAQ7zFazsChh83D42
eI01jfuh58f0DS6qGmjb++N+a/mbgmQhIC4yV4iRZKiIHp9o2xKlSv4NyEJIHlM=
=JnYI
-----END PGP SIGNATURE-----
|
