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
|
Return-Path: <gmaxwell@gmail.com>
Received: from smtp1.linuxfoundation.org (smtp1.linux-foundation.org
[172.17.192.35])
by mail.linuxfoundation.org (Postfix) with ESMTPS id 12FA45AE
for <bitcoin-dev@lists.linuxfoundation.org>;
Wed, 11 May 2016 22:58:51 +0000 (UTC)
X-Greylist: whitelisted by SQLgrey-1.7.6
Received: from mail-lf0-f41.google.com (mail-lf0-f41.google.com
[209.85.215.41])
by smtp1.linuxfoundation.org (Postfix) with ESMTPS id 48D7313D
for <bitcoin-dev@lists.linuxfoundation.org>;
Wed, 11 May 2016 22:58:50 +0000 (UTC)
Received: by mail-lf0-f41.google.com with SMTP id j8so62161294lfd.2
for <bitcoin-dev@lists.linuxfoundation.org>;
Wed, 11 May 2016 15:58:50 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;
h=mime-version:sender:in-reply-to:references:date:message-id:subject
:from:to:cc; bh=qQt5dF38+wLLAOzjQNYwKPtijIJl5ZFyknISfpmFOTU=;
b=a2IK1idNbmeS0ZHE39mXxax/1wVe9VrBnjQGdDhcMlbs3Mxakr3QZ7E994nEi5D0tl
dVwTxE8hAphK/ozIiwHiyJ3Nzi8aSGka2nHfiMJ3bKXttctWeGnCbmYobYrINUhBYddA
rleIc1qyScbxvrVpeJfSsaTxr3cVdK+xPGByZFuvmb04ApGMrljkrcL1xtRW3ekpiUO5
xHMk1AM1JOCrCl+wlP+RUbWd3sdETCJF9j8QjfHGWWWN8UqbRZTUULxWvVpKKJGXkypp
3VCW7p5IdBG/DD1sjsb/zmgvsVOilYhe6uSZghWIoXVyfLg1fMxxmn5+SAkxEoz75mgm
6RMA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
d=1e100.net; s=20130820;
h=x-gm-message-state:mime-version:sender:in-reply-to:references:date
:message-id:subject:from:to:cc;
bh=qQt5dF38+wLLAOzjQNYwKPtijIJl5ZFyknISfpmFOTU=;
b=L39VayobGqptu+3sTd6V8LNDMLMngLeL37u+C24It7cDwIqaRe41kXJ+0TSK+W1fW8
zdwU2SzvZCR95YOtoWekNBnKhXmNI9X7RIarmM59mlToeUt7Io27vRlIUdF2ZNpUzven
qsNYNxFmkets9DwQRJubJa4IxZ9xDhG/lD1GcoDG+4QMQBp8ne0pbmHFT0Rc5mh7QlQG
uKj3ZIp4m0jLUwTspwycO3SxK1IT87h0FygbtuqtXdU6K3RIKI3PgIcx/q2toR/+OJ1T
bApKUQzO1PEm/RlMhBAEepd3rkp1sgvoDFAtgMrHbL4F2OipA0yWtjyEsiVtpDeCvR3K
DwgA==
X-Gm-Message-State: AOPr4FUBLDmhLakcO+F++X1TRebko+4mUqXyL07V2SaUJt0lbGhn5oOUrJkwh5Dp/+L4FDe8QTxHqRlVGuQW0A==
MIME-Version: 1.0
X-Received: by 10.25.26.81 with SMTP id a78mr2852377lfa.6.1463007528786; Wed,
11 May 2016 15:58:48 -0700 (PDT)
Sender: gmaxwell@gmail.com
Received: by 10.112.65.108 with HTTP; Wed, 11 May 2016 15:58:48 -0700 (PDT)
In-Reply-To: <CAH6h1LuemHi1Z8REhZRywghaLjAzy1e1LeHxVdA7iBifGnLnJA@mail.gmail.com>
References: <20160510185728.GA1149@fedora-21-dvm>
<CAH6h1Ls_Dh_oBo-fUMoBtwCQ=U3XgBLhbuHvH+ra78bjHYNyXQ@mail.gmail.com>
<CABeL=0iSvOTqQ-JRuhQfc7spKaXi1eBMMm0D-ahVm3GwztQQ_w@mail.gmail.com>
<20160511103601.GC2439@banane.informatik.uni-ulm.de>
<CABeL=0ih+BB+AKO6uJRCDGZoVo5is4+GBUfQAJkE48Pd_4vzOQ@mail.gmail.com>
<CAH6h1LuemHi1Z8REhZRywghaLjAzy1e1LeHxVdA7iBifGnLnJA@mail.gmail.com>
Date: Wed, 11 May 2016 22:58:48 +0000
X-Google-Sender-Auth: 8H2uKG-ncjvlhM-1ijg0uWd0dCg
Message-ID: <CAAS2fgR3Tyk+RkNQS0Y2kpRp5bzaQJURQq4br9sQCuGoRQ7Ydg@mail.gmail.com>
From: Gregory Maxwell <greg@xiph.org>
To: Timo Hanke <timo.hanke@web.de>,
Bitcoin Protocol Discussion <bitcoin-dev@lists.linuxfoundation.org>
Content-Type: text/plain; charset=UTF-8
X-Spam-Status: No, score=-2.6 required=5.0 tests=BAYES_00,DKIM_SIGNED,
DKIM_VALID, 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: Re: [bitcoin-dev] Making AsicBoost irrelevant
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: Wed, 11 May 2016 22:58:51 -0000
On Wed, May 11, 2016 at 10:42 PM, Timo Hanke via bitcoin-dev
<bitcoin-dev@lists.linuxfoundation.org> wrote:
> This is what I meant. If existing hardware gets forked-out it will
> inevitably lead to the creation of an altcoin. Simply because the hardware
> exists and can't be used for anything else both chains will survive. I was
> only comparing the situation to a contentious hardfork that does not fork
> out any hardware. If the latter one is suspected to lead to the permanent
> existence of two chains then a hardfork that forks out hardware is even more
> likely to do so (I claim it's guaranteed).
There are already many altcoins out there, we could not prevent that
even if we wanted to. New ones are created all the time.
A 20% inherent advantage, in perfect competition, is likely to lead to
an eventual monopoly of mining if monopoly patent right prohibit
competitions-- if mining profits go are under the level of that
enhancement everyone without it would be operating at a loss.
Preserving a vulnerability that will ultimately harm the system's
decentralization for just the betterment of some miners does not seem
like a rational decision for the users of Bitcoin-- no more than it
would reasonable to add a rule that all blocks must be signed by a
particular private key.
As an altcoin the "asicboost" altcoin would be one of the least
interesting altcoins ever created... after all, no other altcoin has
ever been created that required licensing in order to mine.
I don't know if forking it out is the best move here and now, but I'm
happy some people are thinking carefully about what it would take to
do that.
|
