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
|
Return-Path: <jl2012@xbt.hk>
Received: from smtp1.linuxfoundation.org (smtp1.linux-foundation.org
[172.17.192.35])
by mail.linuxfoundation.org (Postfix) with ESMTPS id EBDD194B
for <bitcoin-dev@lists.linuxfoundation.org>;
Wed, 19 Aug 2015 15:22:45 +0000 (UTC)
X-Greylist: from auto-whitelisted by SQLgrey-1.7.6
Received: from s47.web-hosting.com (s47.web-hosting.com [199.188.200.16])
by smtp1.linuxfoundation.org (Postfix) with ESMTPS id 70090240
for <bitcoin-dev@lists.linuxfoundation.org>;
Wed, 19 Aug 2015 15:22:45 +0000 (UTC)
Received: from localhost ([::1]:57196 helo=server47.web-hosting.com)
by server47.web-hosting.com with esmtpa (Exim 4.85)
(envelope-from <jl2012@xbt.hk>)
id 1ZS5CN-003Iwn-Gx; Wed, 19 Aug 2015 11:22:43 -0400
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8;
format=flowed
Content-Transfer-Encoding: 8bit
Date: Wed, 19 Aug 2015 11:22:43 -0400
From: jl2012@xbt.hk
To: odinn <odinn.cyberguerrilla@riseup.net>
In-Reply-To: <55D467AF.5030203@riseup.net>
References: <d17549688c0c747b2077c1f6f96b6445@xbt.hk>
<CAJN5wHV-qyOcEw5spQc74nT7_b29WMiDTmi4Jj0ri_rGCQz2ng@mail.gmail.com>
<E9543641-9D73-4A00-9CB3-FAB62BFB490E@gmail.com>
<CAJN5wHXRwQZ6YmiZiCE9Gx4d-3FTzy1Zv7i2noia0mwtRwVL+w@mail.gmail.com>
<CABm2gDp69g8H4Was2qzixPq3qwQ_smzzeFpE+y2GYEK6F4kUrw@mail.gmail.com>
<55D45715.4010107@riseup.net>
<CABm2gDr2o82O5jtpv=MovAcsvf9xV5u54d4oFajuvuz1QuKZoA@mail.gmail.com>
<55D467AF.5030203@riseup.net>
Message-ID: <46e6bf2dbd8e08745f1c0dbd9f62bc7d@xbt.hk>
X-Sender: jl2012@xbt.hk
User-Agent: Roundcube Webmail/1.0.5
X-AntiAbuse: This header was added to track abuse,
please include it with any abuse report
X-AntiAbuse: Primary Hostname - server47.web-hosting.com
X-AntiAbuse: Original Domain - lists.linuxfoundation.org
X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12]
X-AntiAbuse: Sender Address Domain - xbt.hk
X-Get-Message-Sender-Via: server47.web-hosting.com: authenticated_id:
jl2012@xbt.hk
X-Source:
X-Source-Args:
X-Source-Dir:
X-From-Rewrite: unmodified, already matched
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
Cc: Bitcoin Dev <bitcoin-dev@lists.linuxfoundation.org>
Subject: Re: [bitcoin-dev]
=?utf-8?q?Bitcoin_is_an_experiment=2E_Why_don=27t_w?=
=?utf-8?q?e_have_an_experimental_hardfork=3F?=
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, 19 Aug 2015 15:22:46 -0000
odinn via bitcoin-dev 於 2015-08-19 07:25 寫到:
> The big problem is
>> BIP101 being deployed as a Schism hardfork.
>
> This is certainly a problem.
>
No, BitcoinXT won't become a Schism hardfork, or may be just for a few
days, at most.
There is one, and only one scenario that BitcoinXT will win: it is
supported by major exchanges, merchants, and investors, and they request
miners to support it. When BIP101 is activated, these exchanges will
refuse to accept or exchange tokens from the old chain. Miners in the
old chain can't sell their newly generated coins and can't pay the
electricity bill. They will soon realize that they are mining fool's
gold and will be forced to switch to the new chain or sell their ASIC.
The old chain will be abandoned and has no hope to revive without a
hardfork to decrease the difficulty. The dust will settle in days if not
hours.
Will the adoption of BitcoinXT lead by miners? No, it won't. Actually,
Chinese miners who control 60% of the network has already said that they
would not adopt XT. So they must not be the leader in this revolution.
Again, miners need to make sure they could sell their bitcoin in a good
price, and that's not possible without support of exchanges and
investors.
What about that Not-Bitcoin-XT? The creator of the spoof client may stay
anonymous, but the miners cannot. 95% of the blocks come from known
entities and they have to be responsible to their actions. And again,
they have real money in stake. If bitcoin is destroyed, their ASIC
serves at best as very inefficient heaters.
So Bitcoin-XT is basically in a win-all-or-lose-all position. It all
relies on one condition: the support of major exchanges, merchants, and
investors. Their consensus is what really matters. With their consensus,
that could not be a Schism hardfork. Without their consensus, nothing
will happen.
-------
Or let me analyse in a different angle. BitcoinXT is in no way similar
to your examples of Schism hardforks. All of your examples, "ASIC-reset
hardfork", "Anti-Block-creator hardfork", and "Anti-cabal hardfork", are
hostile to the current biggest miners and will destroy their investment.
These miners have no choice but stick to the original protocol so 2
chains MUST coexist. However, BIP101 has no such effect at all and
miners may freely switch between the forks. They will always choose the
most valuable fork, so only one fork will survive.
|
