From: Wladimir <laanwj@gmail.com>
To: Jeff Garzik <jgarzik@bitpay.com>
Cc: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>
Subject: Re: [Bitcoin-development] Bitcoin miner heads-up: "getwork" RPC going away
Date: Sat, 7 Jun 2014 10:29:18 +0200 [thread overview]
Message-ID: <CA+s+GJDQJk_37EruYkc41YfAgA__ntubwKVGM=15K03LRE+6tQ@mail.gmail.com> (raw)
In-Reply-To: <CAJHLa0OW9TeJrh6J8mAnx8Zy0i+AoF_1Mrp0Wn+5kZGex3_uJg@mail.gmail.com>
On Sat, Jun 7, 2014 at 3:55 AM, Jeff Garzik <jgarzik@bitpay.com> wrote:
> As such, it is planned to remove "getwork" in the next release. Most
> if not all pool servers have switched away from "getwork" years ago.
To be clear, they switched to "getblocktemplate" and "submitblock"
which provides a much more flexible and scalable way to do mining.
This is explained in https://en.bitcoin.it/wiki/Getblocktemplate .
Wladimir
next prev parent reply other threads:[~2014-06-07 8:29 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-07 1:55 [Bitcoin-development] Bitcoin miner heads-up: "getwork" RPC going away Jeff Garzik
2014-06-07 8:29 ` Wladimir [this message]
2014-06-21 15:14 ` Pieter Wuille
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='CA+s+GJDQJk_37EruYkc41YfAgA__ntubwKVGM=15K03LRE+6tQ@mail.gmail.com' \
--to=laanwj@gmail.com \
--cc=bitcoin-development@lists.sourceforge.net \
--cc=jgarzik@bitpay.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
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