📅 Original date posted:2013-08-19 📝 Original message:ACK, I see no reason to ...

Matt Corallo [ARCHIVE] /

npub1e46…xmcu

2023-06-07 15:06:22

in reply to nevent1q…0fqq

📅 Original date posted:2013-08-19
📝 Original message:ACK, I see no reason to leave broken things in that a) arent necessary
and b) no one has the developer resources to fix.

Matt

On Mon, 2013-08-19 at 12:27 -0400, Jeff Garzik wrote:
> 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.
>

Author Public Key

npub1e46n428mcyfwznl7nlsf6d3s7rhlwm9x3cmkuqzt3emmdpadmkaqqjxmcu

Seen on

wss://relay.noswhere.com wss://relay.nostr.band

Show more details

Published at

2023-06-07 15:06:22

Kind type

1 Short Text Note

Event JSON

{ "id": "ea1996352b689b33ced3d86b3c8f57b3c17d5775f70d402089ced7ced33af866", "pubkey": "cd753aa8fbc112e14ffe9fe09d3630f0eff76ca68e376e004b8e77b687adddba", "created_at": 1686150382, "kind": 1, "tags": [ [ "e", "bb0527f033ea487dcaa4ce33f90b862c947802222a1f356b24c426eb3b6562e3", "", "root" ], [ "e", "cce2b2e485c20623c85f6242b2188b00307a9f5f57d4aa2d823e68bdcb5fb485", "", "reply" ], [ "p", "8502a34ff455a038f6a04f4e3cd053dcbb5d711b89a3d211e65615b00e0ed65d" ] ], "content": "📅 Original date posted:2013-08-19\n📝 Original message:ACK, I see no reason to leave broken things in that a) arent necessary\nand b) no one has the developer resources to fix.\n\nMatt\n\nOn Mon, 2013-08-19 at 12:27 -0400, Jeff Garzik wrote:\n\u003e Pull request https://github.com/bitcoin/bitcoin/pull/2905 proposes to\n\u003e remove \"getwork\" RPC from bitcoind: https://en.bitcoin.it/wiki/Getwork\n\u003e \n\u003e On mainnet, almost everybody uses a pool (and therefore, not \"getwork\"\n\u003e directly to bitcoind). Those few who solo mine use a pool server to\n\u003e talk to bitcoind via \"getblocktemplate\" or other means. Tests show\n\u003e that attempts to solo mine on mainnet via \"getwork\" lead to delays and\n\u003e problems.\n\u003e \n\u003e On testnet, getwork has a better chance of continuing to work.\n\u003e Nevertheless, the same tools (open source pool servers or p2pool) are\n\u003e available for testnet, obviating the continued need to support\n\u003e getwork.\n\u003e \n\u003e However, at one time, getwork to bitcoind was widely used. I wanted\n\u003e to poke the audience, to gauge response to removing \"getwork.\" If a\n\u003e driving use case remains of which we're unaware, speak up, please. We\n\u003e don't want to break anybody needlessly.\n\u003e", "sig": "c70849d054faedbe800c2879f55fc4fee70ff2b7bc1be8bcd63a2050e7c371c64b6241aeef0059511cb188835765900dfcfd6b5e017ca42ee1c89009d09105fc" }