Return-Path: <timo.hanke@web.de>
Received: from smtp1.linuxfoundation.org (smtp1.linux-foundation.org
	[172.17.192.35])
	by mail.linuxfoundation.org (Postfix) with ESMTPS id 5DBAACA0
	for <bitcoin-dev@lists.linuxfoundation.org>;
	Fri,  8 Apr 2016 20:59:03 +0000 (UTC)
X-Greylist: from auto-whitelisted by SQLgrey-1.7.6
Received: from mout.web.de (mout.web.de [212.227.15.14])
	by smtp1.linuxfoundation.org (Postfix) with ESMTPS id 1EEB61CE
	for <bitcoin-dev@lists.linuxfoundation.org>;
	Fri,  8 Apr 2016 20:59:01 +0000 (UTC)
Received: from mail-lf0-f44.google.com ([209.85.215.44]) by smtp.web.de
	(mrweb002) with ESMTPSA (Nemesis) id 0LrsGE-1bnurU1cMA-013iD3 for
	<bitcoin-dev@lists.linuxfoundation.org>; Fri, 08 Apr 2016 22:58:58 +0200
Received: by mail-lf0-f44.google.com with SMTP id g184so91491955lfb.3
	for <bitcoin-dev@lists.linuxfoundation.org>;
	Fri, 08 Apr 2016 13:58:57 -0700 (PDT)
X-Gm-Message-State: AD7BkJIsw+Lk8lgNDz/YQoJFvIeLBYqn9G7CK7NHQ5M9Pmh7kJP23A4tmFfwSae0cMDL8GU6hokZo7X8JuZmsQ==
MIME-Version: 1.0
X-Received: by 10.112.72.199 with SMTP id f7mr4320895lbv.17.1460149137427;
	Fri, 08 Apr 2016 13:58:57 -0700 (PDT)
Received: by 10.25.166.148 with HTTP; Fri, 8 Apr 2016 13:58:57 -0700 (PDT)
In-Reply-To: <CAJna-Hjx2e-ztyoieVi=MszXwW=Vdt+8NFyCMEdEH+jydoWKPw@mail.gmail.com>
References: <CAH6h1Lu81Ot0xVb+n05zrtb7PqMAukvP3525rZ8STaq2tcfWNw@mail.gmail.com>
	<20160401090050.GA24677@savin.petertodd.org>
	<5702F257.6010700@musalbas.com>
	<CAJna-Hjx2e-ztyoieVi=MszXwW=Vdt+8NFyCMEdEH+jydoWKPw@mail.gmail.com>
Date: Fri, 8 Apr 2016 10:58:57 -1000
X-Gmail-Original-Message-ID: <CAH6h1LtZ3_zbiPS4id2yUwm=2M1_qtdaD5Uu2gbhxPGzwZnz1w@mail.gmail.com>
Message-ID: <CAH6h1LtZ3_zbiPS4id2yUwm=2M1_qtdaD5Uu2gbhxPGzwZnz1w@mail.gmail.com>
From: Timo Hanke <timo.hanke@web.de>
To: Marek Palatinus <marek@palatinus.cz>
Content-Type: multipart/alternative; boundary=001a11c24064a7d751052fff76ad
X-Provags-ID: V03:K0:S5Nkjq9THnmTqOk3Wz79bdmE1gjSg7dQ8v7u7nfprn4VNacrkPv
	Gt8+scv1D6teOypCyW1Gd4Bfw+O6+0Y4Oequkb3o5mmx04aS2O+dUE/tcw3z95/VO0M0pZ7
	LCz+dWL/SyT3xQTYVIsORLpcyTxaO7Edwu0zpqrFiiruvvnc2Zye+zeYbIhjTUBpP2j7j5V
	eGvtQpwVZ4NPmPkK/edrQ==
X-UI-Out-Filterresults: notjunk:1;V01:K0:Is+sEdtNuYM=:7BY568xV7yXyMBvvEzvyJc
	qIr9UF5inaC2ve6W+V2YBIpxCgHunP9uy2gzqpREABSoKMbQQufunks3FYH6UhFvmmfnWwPkz
	6+N4lUGpJC2CwxGIIV975am519d5Ru9DZwbhh8as4hXhUsd8I4GXcZIAU8RZl4Mxl6Go5QjUd
	js1+GKYFMUIWGDn9T1mY773+BBtq3uttmh5mHAjTVkMzUZChBRVbbZwfWnQd9p36uOWzKefsq
	Y7Lu7X5lDkI5MY2mSA4Ebvwguu+gG+Lnz4vSGw3qdXeOBubN5QtJkiYjtahAccW+cfFjqzWcy
	CfiXtgcPfKeL4aS8sZKlf5QgDleVfR27j1Jpbswv8iPwVYDu2scC7RXmr+5JiuDC1nt+awPRf
	P5k1+K6OqCC1gbJqF30i7K73W2F9m/LuQexKZUm/4stEYhgL/fULbbO/04F4k1X4Udo3oqMnR
	1dPWhJtVY8SIuSe0h9gvPGnrdgvWwGj7vrlAXFmKyEvQNSdREOiDgXaq7WJcKeysm0+FhViAy
	XpnDAPKbewOBPfjEq4Aeo5AwPzfZ90K+UHb2/F+sdjnEfVDf2gbyx/dF+DW7/1oLaldNEskFg
	Yl+YM6AkycB9jDa8gQzP7pekzuHGbtyZnaDmRNcPoabdacHlbB7IeaWtZCR7AdXotreMb1a7e
	/P6aC8s1BVzuAKcRrdEraknkPpAIhqnEOz8hd7FY4sEzdbWcYNH/2sBQiOV3TOHQ6RE7nHLCN
	KyTNuzjZ+7McLPeiNxClKZuOlTRsESORGTeAnTyjty6UWiNrjnBkmbJFMBLWaIqa1S7G8Ap2s
	V39Wzov
X-Spam-Status: No, score=-3.6 required=5.0 tests=BAYES_00,FREEMAIL_FROM,
	HTML_MESSAGE, RCVD_IN_DNSWL_LOW,
	RP_MATCHES_RCVD 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 22:03:09 +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: Fri, 08 Apr 2016 20:59:03 -0000

--001a11c24064a7d751052fff76ad
Content-Type: text/plain; charset=UTF-8

Slush,

You can actually detect the use of this improvement by looking at the I/O
of the chip, the I/O of an on-board micro-controller or even at the system
I/O because all the communication including the mining pool protocol is
different.

Timo

On Wed, Apr 6, 2016 at 1:57 AM, Marek Palatinus <marek@palatinus.cz> wrote:

> 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
>>
>>
>

--001a11c24064a7d751052fff76ad
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">Slush,<div><br></div><div>You can actually detect the use =
of this improvement by looking at the I/O of the chip, the I/O of an on-boa=
rd micro-controller or even at the system I/O because all the communication=
 including the mining pool protocol is different.=C2=A0</div><div><br></div=
><div>Timo<br><div class=3D"gmail_extra"><br><div class=3D"gmail_quote">On =
Wed, Apr 6, 2016 at 1:57 AM, Marek Palatinus <span dir=3D"ltr">&lt;<a href=
=3D"mailto:marek@palatinus.cz" target=3D"_blank">marek@palatinus.cz</a>&gt;=
</span> wrote:<br><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .=
8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir=3D"ltr">To my und=
erstanding it is purely software thing. It cannot be detected from outside =
if miner uses this improvement or not. So patenting it is worthless.<div><b=
r></div><div>slush</div></div><div class=3D"HOEnZb"><div class=3D"h5"><div =
class=3D"gmail_extra"><br><div class=3D"gmail_quote">On Tue, Apr 5, 2016 at=
 1:01 AM, Mustafa Al-Bassam via bitcoin-dev <span dir=3D"ltr">&lt;<a href=
=3D"mailto:bitcoin-dev@lists.linuxfoundation.org" target=3D"_blank">bitcoin=
-dev@lists.linuxfoundation.org</a>&gt;</span> wrote:<br><blockquote class=
=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padd=
ing-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><br>
    <br>
    <div>On 01/04/16 10:00, Peter Todd via
      bitcoin-dev wrote:<br>
    </div>
    </span><blockquote type=3D"cite"><span>
      <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&#39;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&#39;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" target=3D"_blank">=
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>
</div></div></blockquote></div><br></div></div></div>

--001a11c24064a7d751052fff76ad--