From: Jeff Garzik <jgarzik@bitpay•com>
To: Bitcoin Dev <bitcoin-development@lists•sourceforge.net>
Subject: [Bitcoin-development] Proposal: remove "getwork" RPC from bitcoind
Date: Mon, 19 Aug 2013 12:27:01 -0400 [thread overview]
Message-ID: <CAJHLa0MnnWw=qiYC0nJcY=BdTDcAjGtraJ+kazoG7_bHW-HBtw@mail.gmail.com> (raw)
Pull request https://github.com/bitcoin/bitcoin/pull/2905 proposes to
remove "getwork" RPC from bitcoind: https://en.bitcoin.it/wiki/Getwork
On mainnet, almost everybody uses a pool (and therefore, not "getwork"
directly to bitcoind). Those few who solo mine use a pool server to
talk to bitcoind via "getblocktemplate" or other means. Tests show
that attempts to solo mine on mainnet via "getwork" lead to delays and
problems.
On testnet, getwork has a better chance of continuing to work.
Nevertheless, the same tools (open source pool servers or p2pool) are
available for testnet, obviating the continued need to support
getwork.
However, at one time, getwork to bitcoind was widely used. I wanted
to poke the audience, to gauge response to removing "getwork." If a
driving use case remains of which we're unaware, speak up, please. We
don't want to break anybody needlessly.
--
Jeff Garzik
Senior Software Engineer and open source evangelist
BitPay, Inc. https://bitpay.com/
next reply other threads:[~2013-08-19 16:27 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-19 16:27 Jeff Garzik [this message]
2013-08-19 20:09 ` Frank F
2013-08-19 20:13 ` Luke-Jr
2013-08-19 20:14 ` Pieter Wuille
2013-08-19 20:16 ` Frank F
2013-08-19 20:16 ` Gregory Maxwell
2013-08-19 20:18 ` Frank F
2013-08-19 20:23 ` Gregory Maxwell
2013-08-19 20:33 ` Warren Togami Jr.
2013-08-19 20:34 ` Jeff Garzik
2013-08-19 23:02 ` Andreas Schildbach
2013-08-19 23:30 ` Warren Togami Jr.
2013-08-19 20:15 ` Matt Corallo
2013-08-19 20:22 Goss, Brian C., M.D.
2013-08-19 21:07 ` Gregory Maxwell
2013-08-19 22:49 ` Jorge Timón
[not found] <mailman.167053.1376954386.4583.bitcoin-development@lists.sourceforge.net>
2013-08-21 21:24 ` Ron
2013-08-21 21:39 ` rob.golding
2013-08-22 9:36 ` Maciej Trebacz
2013-08-22 13:18 ` Jeff Garzik
2013-08-22 13:33 ` Mike Hearn
2013-08-22 15:30 ` Wladimir
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='CAJHLa0MnnWw=qiYC0nJcY=BdTDcAjGtraJ+kazoG7_bHW-HBtw@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