summaryrefslogtreecommitdiff
path: root/d4/abe88a09114f28b08662aa563501512eda651d
blob: 36bb2a3794bde7ab36a1fd3e89bb2f80de66c732 (plain)
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
Received: from sog-mx-4.v43.ch3.sourceforge.com ([172.29.43.194]
	helo=mx.sourceforge.net)
	by sfs-ml-3.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
	(envelope-from <mh.in.england@gmail.com>) id 1X85dP-0006OU-PH
	for bitcoin-development@lists.sourceforge.net;
	Fri, 18 Jul 2014 10:43:27 +0000
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; 
Received: from mail-oa0-f43.google.com ([209.85.219.43])
	by sog-mx-4.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
	(Exim 4.76) id 1X85dO-0000i8-Ua
	for bitcoin-development@lists.sourceforge.net;
	Fri, 18 Jul 2014 10:43:27 +0000
Received: by mail-oa0-f43.google.com with SMTP id i7so2890084oag.2
	for <bitcoin-development@lists.sourceforge.net>;
	Fri, 18 Jul 2014 03:43:20 -0700 (PDT)
MIME-Version: 1.0
X-Received: by 10.182.233.230 with SMTP id tz6mr5363821obc.53.1405680199808;
	Fri, 18 Jul 2014 03:43:19 -0700 (PDT)
Sender: mh.in.england@gmail.com
Received: by 10.76.35.234 with HTTP; Fri, 18 Jul 2014 03:43:19 -0700 (PDT)
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
X-Google-Sender-Auth: hUV9d_aG6uT9oFOZprzG-Codtmk
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
X-Spam-Score: -0.5 (/)
X-Spam-Report: Spam Filtering performed by mx.sourceforge.net.
	See http://spamassassin.org/tag/ for more details.
	-1.5 SPF_CHECK_PASS SPF reports sender host as permitted sender for
	sender-domain
	0.0 FREEMAIL_FROM Sender email is commonly abused enduser mail provider
	(mh.in.england[at]gmail.com)
	-0.0 SPF_PASS               SPF: sender matches SPF record
	1.0 HTML_MESSAGE           BODY: HTML included in message
	0.1 DKIM_SIGNED            Message has a DKIM or DK signature,
	not necessarily valid
	-0.1 DKIM_VALID Message has at least one valid DKIM or DK signature
X-Headers-End: 1X85dO-0000i8-Ua
Cc: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>
Subject: Re: [Bitcoin-development] Decentralizing ming
X-BeenThere: bitcoin-development@lists.sourceforge.net
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: <bitcoin-development.lists.sourceforge.net>
List-Unsubscribe: <https://lists.sourceforge.net/lists/listinfo/bitcoin-development>,
	<mailto:bitcoin-development-request@lists.sourceforge.net?subject=unsubscribe>
List-Archive: <http://sourceforge.net/mailarchive/forum.php?forum_name=bitcoin-development>
List-Post: <mailto:bitcoin-development@lists.sourceforge.net>
List-Help: <mailto:bitcoin-development-request@lists.sourceforge.net?subject=help>
List-Subscribe: <https://lists.sourceforge.net/lists/listinfo/bitcoin-development>,
	<mailto:bitcoin-development-request@lists.sourceforge.net?subject=subscribe>
X-List-Received-Date: Fri, 18 Jul 2014 10:43:27 -0000

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