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
|
Return-Path: <tomz@freedommail.ch>
Received: from smtp1.linuxfoundation.org (smtp1.linux-foundation.org
[172.17.192.35])
by mail.linuxfoundation.org (Postfix) with ESMTPS id C66E440D
for <bitcoin-dev@lists.linuxfoundation.org>;
Sat, 7 Jan 2017 23:07:31 +0000 (UTC)
X-Greylist: from auto-whitelisted by SQLgrey-1.7.6
Received: from mx-out03.mykolab.com (mx.kolabnow.com [95.128.36.1])
by smtp1.linuxfoundation.org (Postfix) with ESMTPS id 9C55510A
for <bitcoin-dev@lists.linuxfoundation.org>;
Sat, 7 Jan 2017 23:07:30 +0000 (UTC)
X-Virus-Scanned: amavisd-new at kolabnow.com
X-Spam-Score: -2.9
X-Spam-Level:
X-Spam-Status: No, score=-2.6 required=5.0 tests=BAYES_00,RCVD_IN_DNSWL_LOW
autolearn=ham version=3.3.1
Received: from mx03.mykolab.com (mx03.mykolab.com [10.20.7.101])
by mx-out03.mykolab.com (Postfix) with ESMTPS id 9AD492141F
for <bitcoin-dev@lists.linuxfoundation.org>;
Sun, 8 Jan 2017 00:07:27 +0100 (CET)
From: Tom Zander <tomz@freedommail.ch>
To: bitcoin-dev@lists.linuxfoundation.org
Date: Sun, 08 Jan 2017 00:08:29 +0100
Message-ID: <10846872.WfBIm3d0e7@cherry>
In-Reply-To: <CADJgMzvsizuxPCRKcVKA+SHxK0Dp92Bnw1xag+oUFLrvU6Lw7A@mail.gmail.com>
References: <7169224.bI6Cz5OEL8@cherry>
<CAAcC9ysBJcSyMoTAuyFL+1D4m=-LZOgQF_pb4AFC5vpv-yMAHQ@mail.gmail.com>
<CADJgMzvsizuxPCRKcVKA+SHxK0Dp92Bnw1xag+oUFLrvU6Lw7A@mail.gmail.com>
MIME-Version: 1.0
Content-Transfer-Encoding: 7Bit
Content-Type: text/plain; charset="us-ascii"
X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on
smtp1.linux-foundation.org
X-Mailman-Approved-At: Sat, 07 Jan 2017 23:17:29 +0000
Subject: Re: [bitcoin-dev] Bitcoin Classic 1.2.0 released
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: Sat, 07 Jan 2017 23:07:31 -0000
On Saturday, 7 January 2017 21:15:11 CET Btc Drak via bitcoin-dev wrote:
> There actually isn't an activation threshold in Bitcoin Classic.
Thats partly correct.
There is just not a formal one, there very much is an informal and practical
threshold.
I, and I'm not alone in this, think that a formal vote or an algorithm to
decide something will happen or not reeks too much like central planning and
more importantly that it is too inflexible for real world use.
Its fine for simple upgrades, and we have seen lots of success there.
It would be a mistake to think that miners can just start mining with
Classic and make something that Core doesn't understand. That would have
negative effects and thus won't happen. Less social people will ask why and
maybe ask how we avoid this. They misunderstand the social and economic
parts of Bitcoin.
The block size is an ongoing debate.
I find it very hard to believe that all the people replying in outrage to my
release announcement completely missed this.
I see no point in bringing it up in a BIP or on this list as some central
cabal that can make decisions for or against. It is in actual fact being
decided in the real world, out of yours and my control.
Classic is a tool to that end. No more. No less.
--
Tom Zander
Blog: https://zander.github.io
Vlog: https://vimeo.com/channels/tomscryptochannel
|
