Author

Topic: [RFC] removal of "getwork" RPC mining protocol (Read 1405 times)

legendary
Activity: 1232
Merit: 1094
August 19, 2013, 04:14:27 PM
#5
Really unlikely, offering getwork to miners has nothing to do with using it themselves. If they do, they are probably also running bitcoind from sometime in the mid 1940s and won't care... but if they are using it they should report so here!

How do pools actually operate, I assume they don't expose an actual bitcoind as their network input?
staff
Activity: 4326
Merit: 8951
Some pools are still using getwork (btcmine for example) - and therefore potentially needing it for bitcoind as well.
Really unlikely, offering getwork to miners has nothing to do with using it themselves. If they do, they are probably also running bitcoind from sometime in the mid 1940s and won't care... but if they are using it they should report so here!
full member
Activity: 201
Merit: 100
Some pools are still using getwork (btcmine for example) - and therefore potentially needing it for bitcoind as well.

If it's not causing an issue being there, put it on a deprecated list for removal at some future point Smiley

legendary
Activity: 2142
Merit: 1010
Newbie
Can't we deprecate this functionality? "getwork" could return a parameter ("note", for example) with value "Deprecated, read https://bitcointalksearch.org/topic/rfc-removal-of-getwork-rpc-mining-protocol-277631 for more info". Anyone who attempts to use it will see the note. Just in case if s/he didn't see this thread.
legendary
Activity: 1596
Merit: 1100

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.
Jump to: