From: Andreas Schildbach <andreas@schildbach.de>
To: bitcoin-development@lists.sourceforge.net
Subject: Re: [Bitcoin-development] Proposal: remove "getwork" RPC from bitcoind
Date: Tue, 20 Aug 2013 01:02:41 +0200 [thread overview]
Message-ID: <kuu86a$ii5$1@ger.gmane.org> (raw)
In-Reply-To: <CAJHLa0MuF4r1cz1sQc=Qrf5CoHtei8CPvyAL8PBCo=Oug=hMRQ@mail.gmail.com>
On 08/19/2013 10:34 PM, Jeff Garzik wrote:
>> FWIW, Litecoin 0.8.x entirely removed the internal miner and we warned
>> people that getwork will be removed in the next major version. Pooler's CPU
>> minerd which supports both sha256d and scrypt recently grew stratum support.
>> Perhaps he could be convinced to add GBT support too, which would help this
>> goal of completely removing the internal miner and getwork.
>
> The internal miner is still actively used for testnet, here.
Here, too. If I'm too impatient to wait for the next block that is.
I think it'd be a pity if the easy way to mine blocks would be removed.
next prev parent reply other threads:[~2013-08-19 23:03 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-19 16:27 [Bitcoin-development] Proposal: remove "getwork" RPC from bitcoind Jeff Garzik
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 [this message]
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='kuu86a$ii5$1@ger.gmane.org' \
--to=andreas@schildbach.de \
--cc=bitcoin-development@lists.sourceforge.net \
/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