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
|
Return-Path: <marek@palatinus.cz>
Received: from smtp1.linuxfoundation.org (smtp1.linux-foundation.org
[172.17.192.35])
by mail.linuxfoundation.org (Postfix) with ESMTPS id 028B4BF1
for <bitcoin-dev@lists.linuxfoundation.org>;
Wed, 6 Apr 2016 11:58:03 +0000 (UTC)
X-Greylist: whitelisted by SQLgrey-1.7.6
Received: from mail-wm0-f53.google.com (mail-wm0-f53.google.com [74.125.82.53])
by smtp1.linuxfoundation.org (Postfix) with ESMTPS id E98B0162
for <bitcoin-dev@lists.linuxfoundation.org>;
Wed, 6 Apr 2016 11:58:01 +0000 (UTC)
Received: by mail-wm0-f53.google.com with SMTP id n3so59600789wmn.0
for <bitcoin-dev@lists.linuxfoundation.org>;
Wed, 06 Apr 2016 04:58:01 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
d=palatinus-cz.20150623.gappssmtp.com; s=20150623;
h=mime-version:in-reply-to:references:from:date:message-id:subject:to
:cc; bh=GEPfzkOsvOJktBbfEgqf8W65JMX3Xc1tBTxzcZ9VlhY=;
b=ap/7eJUw+oAIxCONT0U7WaZRDFlj1qhiGZ2nwJLOHxW3dgam1rVUuxL0qIcisJP1Ac
4qk1Csxechfp+1rUI6MLn5ieorpj/xmqTaWH1KxWxJ36a6iXHcVeRaqSOP6j1gkgD4SF
nMmHbJoR7LF6jGhBwBX3K8ViRwybKN1lkdY5qEOn9blkfwtQQSzD6VLziLJMnldXiAMG
ARGz0okhI4v4krwxuE3OuEJWUC+sxT6UBWMvasxBovuJfy/VcadUAszFZU8rJbr9W8dL
a17cTjVdCM0pLkZkO5PQVxxuSp6CpSDzJSky8Vpk/K58wU4ZzF9eMFpV/tz3ymiThVpE
+gfQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
d=1e100.net; s=20130820;
h=x-gm-message-state:mime-version:in-reply-to:references:from:date
:message-id:subject:to:cc;
bh=GEPfzkOsvOJktBbfEgqf8W65JMX3Xc1tBTxzcZ9VlhY=;
b=PYzj2Zzrj4/TQq7a3ZKZL55Yvg2BngRb7eS9RAFE68BuyyG3oW8gTlbReRBJIy+MlI
G1igQWD2Ktjdmma+Uh9M1ClKI8/anbjTs7tjoGj9duoWroWtFX4FCHPR80I6udQK2ea/
VWwSSnl+Mb56vpID+ofgxo8wq7FJMyy6QaawVrcKoApURtAbZoInklMK+w41+kY+HXcB
vtANu0tnSpcrdRB7xO3CAvCqkk3QmMseZtLjW0m2Mj+0z+OyZ4crOUrat30x3G9qLJXc
iR1A9Wo6dQWs9lKWZUcz6Ii6B6pKYAVM5ae90RtixrIx5obGC1IAEv98dVMqQ1fVcfsS
uSow==
X-Gm-Message-State: AD7BkJL0JDlQlrg4gmJ0xzO4PxexQFsYUVzIP2Sbzeyk/D5F/83pJg+OzeRJZxQ7FBLgJwBvRjgiEGi9C4cguA==
X-Received: by 10.28.147.8 with SMTP id v8mr2533789wmd.92.1459943880450; Wed,
06 Apr 2016 04:58:00 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.28.64.65 with HTTP; Wed, 6 Apr 2016 04:57:31 -0700 (PDT)
In-Reply-To: <5702F257.6010700@musalbas.com>
References: <CAH6h1Lu81Ot0xVb+n05zrtb7PqMAukvP3525rZ8STaq2tcfWNw@mail.gmail.com>
<20160401090050.GA24677@savin.petertodd.org>
<5702F257.6010700@musalbas.com>
From: Marek Palatinus <marek@palatinus.cz>
Date: Wed, 6 Apr 2016 13:57:31 +0200
Message-ID: <CAJna-Hjx2e-ztyoieVi=MszXwW=Vdt+8NFyCMEdEH+jydoWKPw@mail.gmail.com>
To: Mustafa Al-Bassam <mus@musalbas.com>
Content-Type: multipart/alternative; boundary=001a114733ac631b19052fcfac86
X-Spam-Status: No, score=-2.6 required=5.0 tests=BAYES_00,DKIM_SIGNED,
DKIM_VALID,HTML_MESSAGE,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
X-Mailman-Approved-At: Fri, 08 Apr 2016 14:59:55 +0000
Cc: bitcoin-dev@lists.linuxfoundation.org
Subject: Re: [bitcoin-dev] AsicBoost
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, 06 Apr 2016 11:58:03 -0000
--001a114733ac631b19052fcfac86
Content-Type: text/plain; charset=UTF-8
To my understanding it is purely software thing. It cannot be detected from
outside if miner uses this improvement or not. So patenting it is worthless.
slush
On Tue, Apr 5, 2016 at 1:01 AM, Mustafa Al-Bassam via bitcoin-dev <
bitcoin-dev@lists.linuxfoundation.org> wrote:
> Alternatively scenario: it will cause a sudden increase of Bitcoin mines
> in countries where the algorithm is not patented, possibly causing a
> geographical decentralization of miners from countries that already have a
> lot of miners like China (if it is patented in China).
>
> On 01/04/16 10:00, Peter Todd via bitcoin-dev wrote:
>
> On Thu, Mar 31, 2016 at 09:41:40PM -0700, Timo Hanke via bitcoin-dev wrote:
>
> Hi.
>
> I'd like to announce a white paper that describes a very new and
> significant algorithmic improvement to the Bitcoin mining process which has
> never been discussed in public before. The white paper can be found here:
> http://www.math.rwth-aachen.de/~Timo.Hanke/AsicBoostWhitepaperrev5.pdf
>
> What steps are you going to take to make sure that this improvement is
> available to all ASIC designers/mfgs on a equal opportunity basis?
>
> The fact that you've chosen to patent this improvement could be a
> centralization concern depending on the licensing model used. For example, one
> could imagine a licensing model that gave one manufacture exclusive rights.
>
>
>
>
> _______________________________________________
> bitcoin-dev mailing listbitcoin-dev@lists.linuxfoundation.orghttps://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev
>
>
>
> _______________________________________________
> bitcoin-dev mailing list
> bitcoin-dev@lists.linuxfoundation.org
> https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev
>
>
--001a114733ac631b19052fcfac86
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
<div dir=3D"ltr">To my understanding it is purely software thing. It cannot=
be detected from outside if miner uses this improvement or not. So patenti=
ng it is worthless.<div><br></div><div>slush</div></div><div class=3D"gmail=
_extra"><br><div class=3D"gmail_quote">On Tue, Apr 5, 2016 at 1:01 AM, Must=
afa Al-Bassam via bitcoin-dev <span dir=3D"ltr"><<a href=3D"mailto:bitco=
in-dev@lists.linuxfoundation.org" target=3D"_blank">bitcoin-dev@lists.linux=
foundation.org</a>></span> wrote:<br><blockquote class=3D"gmail_quote" s=
tyle=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
=20
=20
=20
<div bgcolor=3D"#FFFFFF" text=3D"#000000">
Alternatively scenario: it will cause a sudden increase of Bitcoin
mines in countries where the algorithm is not patented, possibly
causing a geographical decentralization of miners from countries
that already have a lot of miners like China (if it is patented in
China).<span class=3D""><br>
<br>
<div>On 01/04/16 10:00, Peter Todd via
bitcoin-dev wrote:<br>
</div>
</span><blockquote type=3D"cite"><span class=3D"">
<pre>On Thu, Mar 31, 2016 at 09:41:40PM -0700, Timo Hanke via bitcoin=
-dev wrote:
</pre>
<blockquote type=3D"cite">
<pre>Hi.
I'd like to announce a white paper that describes a very new and
significant algorithmic improvement to the Bitcoin mining process which has
never been discussed in public before. The white paper can be found here:
<a href=3D"http://www.math.rwth-aachen.de/~Timo.Hanke/AsicBoostWhitepaperre=
v5.pdf" target=3D"_blank">http://www.math.rwth-aachen.de/~Timo.Hanke/AsicBo=
ostWhitepaperrev5.pdf</a>
</pre>
</blockquote>
<pre>What steps are you going to take to make sure that this improvem=
ent is
available to all ASIC designers/mfgs on a equal opportunity basis?
The fact that you've chosen to patent this improvement could be a
centralization concern depending on the licensing model used. For example, =
one
could imagine a licensing model that gave one manufacture exclusive rights.
</pre>
<br>
<fieldset></fieldset>
<br>
</span><pre>_______________________________________________
bitcoin-dev mailing list
<a href=3D"mailto:bitcoin-dev@lists.linuxfoundation.org" target=3D"_blank">=
bitcoin-dev@lists.linuxfoundation.org</a>
<a href=3D"https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev" =
target=3D"_blank">https://lists.linuxfoundation.org/mailman/listinfo/bitcoi=
n-dev</a>
</pre>
</blockquote>
<br>
</div>
<br>_______________________________________________<br>
bitcoin-dev mailing list<br>
<a href=3D"mailto:bitcoin-dev@lists.linuxfoundation.org">bitcoin-dev@lists.=
linuxfoundation.org</a><br>
<a href=3D"https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev" =
rel=3D"noreferrer" target=3D"_blank">https://lists.linuxfoundation.org/mail=
man/listinfo/bitcoin-dev</a><br>
<br></blockquote></div><br></div>
--001a114733ac631b19052fcfac86--
|
