From: Jeff Garzik <jgarzik@bitpay•com>
To: Bitcoin Dev <bitcoin-development@lists•sourceforge.net>
Subject: [Bitcoin-development] Bitcoin miner heads-up: "getwork" RPC going away
Date: Fri, 6 Jun 2014 21:55:31 -0400 [thread overview]
Message-ID: <CAJHLa0OW9TeJrh6J8mAnx8Zy0i+AoF_1Mrp0Wn+5kZGex3_uJg@mail.gmail.com> (raw)
"getwork" has long been unused on mainnet, and mostly unused elsewhere
as well. It generates work by a method that cannot keep up with the
demands of the modern network.
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.
--
Jeff Garzik
Bitcoin core developer and open source evangelist
BitPay, Inc. https://bitpay.com/
next reply other threads:[~2014-06-07 1:55 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-07 1:55 Jeff Garzik [this message]
2014-06-07 8:29 ` Wladimir
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=CAJHLa0OW9TeJrh6J8mAnx8Zy0i+AoF_1Mrp0Wn+5kZGex3_uJg@mail.gmail.com \
--to=jgarzik@bitpay$(echo .)com \
--cc=bitcoin-development@lists$(echo .)sourceforge.net \
/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