public inbox for bitcoindev@googlegroups.com
 help / color / mirror / Atom feed
From: Frank F <frankf44@gmail.com>
Cc: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>
Subject: Re: [Bitcoin-development] Proposal: remove "getwork" RPC from bitcoind
Date: Mon, 19 Aug 2013 15:09:41 -0500	[thread overview]
Message-ID: <CALxyHsXoCqL8dNXeayibfbR7-JU6Ke19gJJ1fToboULdUa155Q@mail.gmail.com> (raw)
In-Reply-To: <CAJHLa0MnnWw=qiYC0nJcY=BdTDcAjGtraJ+kazoG7_bHW-HBtw@mail.gmail.com>

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

I strongly object to removing the only mechanism that allows anyone to say
that bitcoin is p2p, in the truest sense of the word. Moves like this that
favor only the pool operators and private mining interests are signs that
bitcoin is headed towards a monopoly/cartel model, and that would be a
tragic outcome for something that holds a great promise. Nobody knows what
mining will look like in the future, and denying the individual novice the
ability to mine at a small scale, even if we may think it is inefficient
now, is not a good path to start down.

If there are technical problems with getwork, maybe they should be
addressed and fixed instead of outright abandoned.


On Mon, Aug 19, 2013 at 11:27 AM, Jeff Garzik <jgarzik@bitpay.com> 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.
>
> --
> Jeff Garzik
> Senior Software Engineer and open source evangelist
> BitPay, Inc.      https://bitpay.com/
>
>
> ------------------------------------------------------------------------------
> 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
>



-- 
*MONEY IS OVER!*
                                IF YOU WANT IT<http://www.zeitgeistmovie.com/>
=====================================================
The causes of my servitude can be traced to the tyranny of money.
-Serj Tankian

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

  reply	other threads:[~2013-08-19 20:09 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 [this message]
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
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=CALxyHsXoCqL8dNXeayibfbR7-JU6Ke19gJJ1fToboULdUa155Q@mail.gmail.com \
    --to=frankf44@gmail.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