From: Mike Hearn <mike@plan99•net>
To: slush <slush@centrum•cz>
Cc: Bitcoin Dev <bitcoin-development@lists•sourceforge.net>
Subject: Re: [Bitcoin-development] Decentralizing ming
Date: Fri, 18 Jul 2014 12:43:19 +0200 [thread overview]
Message-ID: <CANEZrP2+tufB0jbgqdCc9t_XLbs9pnX9t8jUGfLA_xLDhEts8Q@mail.gmail.com> (raw)
In-Reply-To: <CANEZrP0HxfJYaTxYdxh3ANLOMma_J9A93A0LjB47PHdiaNo5NA@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 965 bytes --]
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.
>
>
[-- Attachment #2: Type: text/html, Size: 1372 bytes --]
next prev parent reply other threads:[~2014-07-18 10:43 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-17 16:14 Jeff Garzik
2014-07-17 17:22 ` slush
2014-07-18 10:41 ` Mike Hearn
2014-07-18 10:43 ` Mike Hearn [this message]
2014-07-18 13:44 ` Jeff Garzik
2014-07-19 0:51 ` Emin Gün Sirer
2014-07-19 0:54 ` Emin Gün Sirer
2014-07-18 13:39 ` Jeff Garzik
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CANEZrP2+tufB0jbgqdCc9t_XLbs9pnX9t8jUGfLA_xLDhEts8Q@mail.gmail.com \
--to=mike@plan99$(echo .)net \
--cc=bitcoin-development@lists$(echo .)sourceforge.net \
--cc=slush@centrum$(echo .)cz \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox