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
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
|
Return-Path: <david.vorick@gmail.com>
Received: from smtp1.linuxfoundation.org (smtp1.linux-foundation.org
[172.17.192.35])
by mail.linuxfoundation.org (Postfix) with ESMTPS id ADC3D98C
for <bitcoin-dev@lists.linuxfoundation.org>;
Thu, 6 Apr 2017 12:04:19 +0000 (UTC)
X-Greylist: whitelisted by SQLgrey-1.7.6
Received: from mail-wr0-f171.google.com (mail-wr0-f171.google.com
[209.85.128.171])
by smtp1.linuxfoundation.org (Postfix) with ESMTPS id 99F0FA4
for <bitcoin-dev@lists.linuxfoundation.org>;
Thu, 6 Apr 2017 12:04:18 +0000 (UTC)
Received: by mail-wr0-f171.google.com with SMTP id t20so58438109wra.1
for <bitcoin-dev@lists.linuxfoundation.org>;
Thu, 06 Apr 2017 05:04:18 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;
h=mime-version:in-reply-to:references:from:date:message-id:subject:to;
bh=CnC/X97TnhFdhUSrk7gEQVEmsq6t+UN5lLU0vsqfxps=;
b=VTweuY+TDHnD+6u2FV3Jn74Kr6au+tiHF/tkwGo1ybR1ByOUpv5kr7xe585GmqSosQ
R97ZdcciNb1/ajVx83xVm/M2UQUXwbny0OlF5VcJgfwaA+ETqWHoEteGXWFu3lEuYiIP
v+wcBCc6/3MLb073i4RWFvcNH0RqT1ojmDqk4cRkTvRqW7RcZiuNbd615y8ABuIYWhg2
DSG02YOTObW8+aRkhIWk0eN1gToP5m3JayUC5djqQbjomZ3R/uM9DDoTGC9GbS9CQ9ML
Y4Segj3ZLG7w4+pdUB6TDYc5C2ne6IrRsGyXQfT1ZCoS94F8QD9S9YXyQldmFjmqoj4v
4Img==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
d=1e100.net; s=20161025;
h=x-gm-message-state:mime-version:in-reply-to:references:from:date
:message-id:subject:to;
bh=CnC/X97TnhFdhUSrk7gEQVEmsq6t+UN5lLU0vsqfxps=;
b=BQi5dn6TcIIJCTjfAHYdCHnhEarcTzBWgQu+iIwE/OHfhgcUjYVqG1O3vUXh/icO1Y
QRKAZPFW2bCbNzrpv0XkaLQHAdR40+koS1EuJLjzbg5/DhPzeQmX+zQpRQf60SfGfl5I
D/n1nBCOSTpO2OZ0G4bB2kkVu4v0Wl8yvn3WzLrK+NDj7ci1Hh74l1/SiKEfiEEJFv+d
WY3pjnXKW7Cefu9vFxpD9oqKUjD0z/hBGiQVkk2e23p3lqdk9DWQUTVHFYIFNaPxy2PZ
pTKh8wEo7crsrKuoACawg0MDpAtCWqLDtIMgELQ63KKwBS5btrMG4JmEb7qD0+Eqrnqw
m/MA==
X-Gm-Message-State: AFeK/H1pQgkPDYA4slXqam7qZXuk1rBajuvBwoqC26W3Z5IuTgIQ3QDP
/C5+19ggi4j54NU9cmykKT5lNfBdBWjn
X-Received: by 10.28.146.207 with SMTP id u198mr23502856wmd.103.1491480256910;
Thu, 06 Apr 2017 05:04:16 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.28.55.9 with HTTP; Thu, 6 Apr 2017 05:04:16 -0700 (PDT)
In-Reply-To: <F5F02B94-E094-4C16-80B6-8B0876E423E4@toom.im>
References: <CAAS2fgR84898xD0nyq7ykJnB7qkdoCJYnFg6z5WZEUu0+-=mMA@mail.gmail.com>
<20170406023123.GA1071@savin.petertodd.org>
<CA+KqGkqSxeAUZFVFqM_QkEWcGFHgZXwGuOE==7HpXp1+D_Tj3Q@mail.gmail.com>
<20170406024910.GA1271@savin.petertodd.org>
<CAFVRnyrqiNY_JOqhv2ysm2WsBMYsU3tTAASAtHzMbA68_9Yx8g@mail.gmail.com>
<F5F02B94-E094-4C16-80B6-8B0876E423E4@toom.im>
From: David Vorick <david.vorick@gmail.com>
Date: Thu, 6 Apr 2017 08:04:16 -0400
Message-ID: <CAFVRnyrmWvCJ2B9LjLwL6GoqkVJNaMpxD+3Nv9JMCXW3DRE-tg@mail.gmail.com>
To: Jonathan Toomim <j@toom.im>,
Bitcoin Protocol Discussion <bitcoin-dev@lists.linuxfoundation.org>
Content-Type: multipart/alternative; boundary=001a11442ae0e72917054c7e4e22
X-Spam-Status: No, score=-2.0 required=5.0 tests=BAYES_00,DKIM_SIGNED,
DKIM_VALID, DKIM_VALID_AU, FREEMAIL_FROM, HTML_MESSAGE,
RCVD_IN_DNSWL_NONE 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] BIP proposal: Inhibiting a covert attack on the
Bitcoin POW function
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: Thu, 06 Apr 2017 12:04:20 -0000
--001a11442ae0e72917054c7e4e22
Content-Type: text/plain; charset=UTF-8
On Thu, Apr 6, 2017 at 2:24 AM, Jonathan Toomim via bitcoin-dev <
bitcoin-dev@lists.linuxfoundation.org> wrote:
> Ethically, this situation has some similarities to the DAO fork. We have
> an entity who closely examined the code, found an unintended characteristic
> of that code, and made use of that characteristic in order to gain tens of
> millions of dollars. Now that developers are aware of it, they want to
> modify the code in order to negate as much of the gains as possible.
>
> There are differences, too, of course: the DAO attacker was explicitly
> malicious and stole Ether from others, whereas Bitmain is just optimizing
> their hardware better than anyone else and better than some of us think
> they should be allowed to.
>
> In both cases, developers are proposing that the developers and a majority
> of users collude to reduce the wealth of a single entity by altering the
> blockchain rules.
>
> In the case of the DAO fork, users were stealing back stolen funds, but
> that justification doesn't apply in this case. On the other hand, in this
> case we're talking about causing someone a loss by reducing the value of
> hardware investments rather than forcibly taking back their coins, which is
> less direct and maybe more justifiable.
>
> While I don't like patented mining algorithms, I also don't like the idea
> of playing Calvin Ball on the blockchain. Rule changes should not be
> employed as a means of disempowering and empoverishing particular entities
> without very good reason. Whether patenting a mining optimization qualifies
> as good reason is questionable.
>
Bitmain is blocking protocol upgrades to preserve their mining advantage.
This is quite distinct from someone taking advantage of a visibly broken
and highly toxic smart contract to net themselves tens of millions of
dollars. Further, Bitmain is performing a patented hardware optimization.
The patents mean that other miners are unable to capitalize on these
optimizations. These optimizations are to the tune of 30%. If you give one
player in the mining industry a permanent 30% cost advantage they will
eventually own everything. It's an industry where margins tend towards zero.
The asicboost patent is a direct threat to the health of the Bitcoin
ecosystem, and now we have visible proof. The war against segwit and the
strife with Bitcoin Unlimited was very damaging to the ecosystem, damaging
to the price, and holding back significant improvements and upgrades to the
Bitcoin protocol. I interpret this as a direct attack on the Bitcoin
ecosystem.
I don't know if changing the rules to nullify asicboost is the right move.
I'm sure this won't be the last patent that causes damage to the ecosystem.
But you need to recognize that the issue is not that Bitmain ran a hardware
optimization. It's that hardware optimizations exist which directly inhibit
upgrading the protocol. And it's that hardware optimizations exist
encumbered by patents enough to give one party a decisive advantage in
mining, decisive enough for them to build a single, centralized monopoly.
Each problem is separate, and each problem is significant, and each problem
is fundamental. The DAO attack was a one-time bout of stupidity that
threatened a fixed amount of money. asicboost is an ongoing status that
directly damages Bitcoin's ability to upgrade, and directly damage
Bitcoin's ability to retain any modicum of decentralization in the
hashrate. The DAO issue did neither of these things for ethereum.
--001a11442ae0e72917054c7e4e22
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
<div dir=3D"ltr">On Thu, Apr 6, 2017 at 2:24 AM, Jonathan Toomim via bitcoi=
n-dev <span dir=3D"ltr"><<a target=3D"_blank" href=3D"mailto:bitcoin-dev=
@lists.linuxfoundation.org">bitcoin-dev@lists.linuxfoundation.org</a>></=
span> wrote:<br><div class=3D"gmail_extra"><div class=3D"gmail_quote"><bloc=
kquote style=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,=
204);padding-left:1ex" class=3D"gmail_quote">Ethically, this situation has =
some similarities to the DAO fork. We have an entity who closely examined t=
he code, found an unintended characteristic of that code, and made use of t=
hat characteristic in order to gain tens of millions of dollars. Now that d=
evelopers are aware of it, they want to modify the code in order to negate =
as much of the gains as possible.<br>
<br>
There are differences, too, of course: the DAO attacker was explicitly mali=
cious and stole Ether from others, whereas Bitmain is just optimizing their=
hardware better than anyone else and better than some of us think they sho=
uld be allowed to.<br>
<br>
In both cases, developers are proposing that the developers and a majority =
of users collude to reduce the wealth of a single entity by altering the bl=
ockchain rules.<br>
<br>
In the case of the DAO fork, users were stealing back stolen funds, but tha=
t justification doesn't apply in this case. On the other hand, in this =
case we're talking about causing someone a loss by reducing the value o=
f hardware investments rather than forcibly taking back their coins, which =
is less direct and maybe more justifiable.<br>
<br>
While I don't like patented mining algorithms, I also don't like th=
e idea of playing Calvin Ball on the blockchain. Rule changes should not be=
employed as a means of disempowering and empoverishing particular entities=
without very good reason. Whether patenting a mining optimization qualifie=
s as good reason is questionable.<br></blockquote><div><br>Bitmain is block=
ing protocol upgrades to=20
preserve their mining advantage. This is quite distinct from someone=20
taking advantage of a visibly broken and highly toxic smart contract to=20
net themselves tens of millions of dollars. Further, Bitmain is=20
performing a patented hardware optimization. The patents mean that other
miners are unable to capitalize on these optimizations. These=20
optimizations are to the tune of 30%. If you give one player in the=20
mining industry a permanent 30% cost advantage they will eventually own=20
everything. It's an industry where margins tend towards zero.<br><br>Th=
e
asicboost patent is a direct threat to the health of the Bitcoin=20
ecosystem, and now we have visible proof. The war against segwit and the
strife with Bitcoin Unlimited was very damaging to the ecosystem,=20
damaging to the price, and holding back significant improvements and=20
upgrades to the Bitcoin protocol. I interpret this as a direct attack on
the Bitcoin ecosystem.<br><br>I don't know if changing the rules=20
to nullify asicboost is the right move. I'm sure this won't be the =
last=20
patent that causes damage to the ecosystem. But you need to recognize=20
that the issue is not that Bitmain ran a hardware optimization. It's th=
at hardware optimizations exist which directly inhibit upgrading the protoc=
ol. And it's that hardware optimizations exist encumbered by patents en=
ough to give one party a decisive advantage in mining, decisive enough for =
them to build a single, centralized monopoly.<br><br></div><div>Each proble=
m is separate, and each problem is significant, and each problem is fundame=
ntal. The DAO attack was a one-time bout of stupidity that threatened a fix=
ed amount of money. asicboost is an ongoing status that directly damages Bi=
tcoin's ability to upgrade, and directly damage Bitcoin's ability t=
o retain any modicum of decentralization in the hashrate. The DAO issue did=
neither of these things for ethereum.<br></div></div></div></div>
--001a11442ae0e72917054c7e4e22--
|
