public inbox for bitcoindev@googlegroups.com
 help / color / mirror / Atom feed
From: Maciej Trebacz <maciej@bitalo.com>
To: bitcoin-development@lists.sourceforge.net
Subject: Re: [Bitcoin-development] Proposal: remove "getwork" RPC from bitcoind
Date: Thu, 22 Aug 2013 11:36:51 +0200	[thread overview]
Message-ID: <CAD=_8RRU8UAqOUZeawe=XVfT91YtWmVGwDzW+KfkWYj649aZbw@mail.gmail.com> (raw)
In-Reply-To: <6e1e64615be421f47a74bcc427a13485@astutium.com>

[-- Attachment #1: Type: text/plain, Size: 1470 bytes --]

Will removing "getwork" from the client impact the "setgenerate" RPC call?
I.e. would you still be able to generate coins on testnet-in-a-box this
way, or would you need a dedicated miner for that? testnet-in-a-box is very
useful for testing and easy to setup, it would be great if it stays that
way :).


On Wed, Aug 21, 2013 at 11:39 PM, <rob.golding@astutium.com> wrote:

> > 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,
>
> I thought the integrated miner was retired a version or so ago - I
> dontrecall seeing it for some time in bitcoin-qt
>
> Now you can buy a USB stick for $20 which can be pushed to around
> 500MH/s, and  there's no reason the manufacturers couldn't ship those
> with a miner-program onboard !
>
> Rob
>
>
> ------------------------------------------------------------------------------
> Introducing Performance Central, a new site from SourceForge and
> AppDynamics. Performance Central is your source for news, insights,
> analysis and resources for efficient Application Performance Management.
> Visit us today!
> http://pubads.g.doubleclick.net/gampad/clk?id=48897511&iu=/4140/ostg.clktrk
> _______________________________________________
> Bitcoin-development mailing list
> Bitcoin-development@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/bitcoin-development
>

[-- Attachment #2: Type: text/html, Size: 2298 bytes --]

  reply	other threads:[~2013-08-22 10:43 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <mailman.167053.1376954386.4583.bitcoin-development@lists.sourceforge.net>
2013-08-21 21:24 ` [Bitcoin-development] Proposal: remove "getwork" RPC from bitcoind Ron
2013-08-21 21:39   ` rob.golding
2013-08-22  9:36     ` Maciej Trebacz [this message]
2013-08-22 13:18       ` Jeff Garzik
2013-08-22 13:33         ` Mike Hearn
2013-08-22 15:30           ` Wladimir
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
  -- 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='CAD=_8RRU8UAqOUZeawe=XVfT91YtWmVGwDzW+KfkWYj649aZbw@mail.gmail.com' \
    --to=maciej@bitalo.com \
    --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