Received-SPF: pass (sog-mx-4.v43.ch3.sourceforge.com: domain of gmail.com
	designates 209.85.219.43 as permitted sender)
	client-ip=209.85.219.43; envelope-from=mh.in.england@gmail.com;
	helo=mail-oa0-f43.google.com; 
MIME-Version: 1.0
Sender: mh.in.england@gmail.com
In-Reply-To: <CANEZrP0HxfJYaTxYdxh3ANLOMma_J9A93A0LjB47PHdiaNo5NA@mail.gmail.com>
References: <CAJHLa0PWF38N0-CFY9b3FzFdN2NfLduWHCeCQHXQOKirDYn0Pw@mail.gmail.com>
	<CAJna-HhhqYGSVwapvR_5yvRY3gc6wXGaNXm_dkP4Tid7F1SsLw@mail.gmail.com>
	<CANEZrP0HxfJYaTxYdxh3ANLOMma_J9A93A0LjB47PHdiaNo5NA@mail.gmail.com>
Date: Fri, 18 Jul 2014 12:43:19 +0200
Message-ID: <CANEZrP2+tufB0jbgqdCc9t_XLbs9pnX9t8jUGfLA_xLDhEts8Q@mail.gmail.com>
From: Mike Hearn <mike@plan99.net>
To: slush <slush@centrum.cz>
Content-Type: multipart/alternative; boundary=001a11c30012fa3f6f04fe756c9f
Cc: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>
Subject: Re: [Bitcoin-development] Decentralizing ming
Precedence: list

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

Oops, sorry, I see the subject line changed. This is what I get for working
down the thread list top to bottom :)

I think the best path forward now is to finish off getblocktemplate support
in the various tools so it's possible to pool for payout purposes without
giving up control of block creation modulo the coinbase. Combined with the
recent sipa performance enhancing goodness, it would hopefully persuade
some non-trivial chunk of hashpower to go back to running their own node
and start the process of turning pools merely into payout trackers rather
than block selectors.


On Fri, Jul 18, 2014 at 12:41 PM, Mike Hearn <mike@plan99.net> wrote:

> Jeff, I think the message you're replying to got clipped.
>
> Satoshi's only comment AFAIK on the topic of GPU mining was to wish for a
> gentlemen's agreement to postpone it as long as possible, to help make sure
> the distribution of coins was as even as possible. Indeed this predated
> pooled mining.
>
>

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

<div dir=3D"ltr">Oops, sorry, I see the subject line changed. This is what =
I get for working down the thread list top to bottom :)<div><br></div><div>=
I think the best path forward now is to finish off getblocktemplate support=
 in the various tools so it&#39;s possible to pool for payout purposes with=
out giving up control of block creation modulo the coinbase. Combined with =
the recent sipa performance enhancing goodness, it would hopefully persuade=
 some non-trivial chunk of hashpower to go back to running their own node a=
nd start the process of turning pools merely into payout trackers rather th=
an block selectors.</div>
</div><div class=3D"gmail_extra"><br><br><div class=3D"gmail_quote">On Fri,=
 Jul 18, 2014 at 12:41 PM, Mike Hearn <span dir=3D"ltr">&lt;<a href=3D"mail=
to:mike@plan99.net" target=3D"_blank">mike@plan99.net</a>&gt;</span> wrote:=
<br><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-lef=
t:1px #ccc solid;padding-left:1ex">
<div dir=3D"ltr">Jeff, I think the message you&#39;re replying to got clipp=
ed.<div><br></div><div>Satoshi&#39;s only comment AFAIK on the topic of GPU=
 mining was to wish for a gentlemen&#39;s agreement to postpone it as long =
as possible, to help make sure the distribution of coins was as even as pos=
sible. Indeed this predated pooled mining.</div>

<div class=3D"gmail_extra"><br></div></div>
</blockquote></div><br></div>

--001a11c30012fa3f6f04fe756c9f--