From: Gregory Maxwell <gmaxwell@gmail•com>
To: "Goss, Brian C., M.D." <Goss.Brian@mayo•edu>
Cc: "bitcoin-development@lists•sourceforge.net"
<bitcoin-development@lists•sourceforge.net>
Subject: Re: [Bitcoin-development] Proposal: remove "getwork" RPC from bitcoind
Date: Mon, 19 Aug 2013 14:07:46 -0700 [thread overview]
Message-ID: <CAAS2fgQtGg+SxRc7Byw0_L3NpEudPTtBpmnKYt-+7VEVSnKZaQ@mail.gmail.com> (raw)
In-Reply-To: <FFE335820B1BFF4F8E8619F446F2D87F4C1A2E7B@MSGPEXCEI26B.mfad.mfroot.org>
On Mon, Aug 19, 2013 at 1:22 PM, Goss, Brian C., M.D.
<Goss.Brian@mayo•edu> wrote:
> What if we have a massive (like many orders of magnitude) drop in network harsh rate? Might such a function be useful to salvage the (non-functioning) network? Same for IRC bootstrapping. How do we pick ourselves up off the ground in case of the equivalent of a great depression in network hash rate (or some jerk spending $100M just to drive the difficulty up and then turning his hardware off?).
[Aside: When replying to the digest, please try to trim it]
It appears that we will soon be at a hashrate where all the desktop
CPUs in the world couldn't really make a dent in it... certainly not
desktop cpus using the slow integrated cpu miner, which is much slower
than external optimized cpu miners.
But this is why I suggest packaging up a modern mining tool that
supports CPU/GPU/FPGA/ASIC mining against a current bitcoind. Doing so
would reduce the difference between testnet and mainnet, and provide
an actually useful tool for contributing directly.
Though again, I note, that Jeff's patch doesn't actually remove the
integrated miner (I think it should…). Just the getwork support for
external miners which don't use getblocktemplate... and if you're
going to download one of those you could go download bfgminer instead.
next prev parent reply other threads:[~2013-08-19 21:07 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-19 20:22 Goss, Brian C., M.D.
2013-08-19 21:07 ` Gregory Maxwell [this message]
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
-- strict thread matches above, loose matches on Subject: below --
2013-08-19 16:27 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
2013-08-19 23:30 ` Warren Togami Jr.
2013-08-19 20:15 ` Matt Corallo
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=CAAS2fgQtGg+SxRc7Byw0_L3NpEudPTtBpmnKYt-+7VEVSnKZaQ@mail.gmail.com \
--to=gmaxwell@gmail$(echo .)com \
--cc=Goss.Brian@mayo$(echo .)edu \
--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