Received: from sog-mx-2.v43.ch3.sourceforge.com ([172.29.43.192] helo=mx.sourceforge.net) by sfs-ml-4.v29.ch3.sourceforge.com with esmtp (Exim 4.76) (envelope-from ) id 1VBVls-0005Bn-Ql for bitcoin-development@lists.sourceforge.net; Mon, 19 Aug 2013 20:09:48 +0000 Received-SPF: pass (sog-mx-2.v43.ch3.sourceforge.com: domain of gmail.com designates 209.85.212.45 as permitted sender) client-ip=209.85.212.45; envelope-from=frankf44@gmail.com; helo=mail-vb0-f45.google.com; Received: from mail-vb0-f45.google.com ([209.85.212.45]) by sog-mx-2.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128) (Exim 4.76) id 1VBVlr-0005Hj-I1 for bitcoin-development@lists.sourceforge.net; Mon, 19 Aug 2013 20:09:48 +0000 Received: by mail-vb0-f45.google.com with SMTP id e15so3443059vbg.4 for ; Mon, 19 Aug 2013 13:09:42 -0700 (PDT) MIME-Version: 1.0 X-Received: by 10.58.137.167 with SMTP id qj7mr14863434veb.1.1376942981976; Mon, 19 Aug 2013 13:09:41 -0700 (PDT) Received: by 10.220.165.201 with HTTP; Mon, 19 Aug 2013 13:09:41 -0700 (PDT) In-Reply-To: References: Date: Mon, 19 Aug 2013 15:09:41 -0500 Message-ID: From: Frank F Cc: Bitcoin Dev Content-Type: multipart/alternative; boundary=047d7b677efa51198a04e4528551 X-Spam-Score: 0.9 (/) X-Spam-Report: Spam Filtering performed by mx.sourceforge.net. See http://spamassassin.org/tag/ for more details. -1.5 SPF_CHECK_PASS SPF reports sender host as permitted sender for sender-domain 0.0 FREEMAIL_FROM Sender email is commonly abused enduser mail provider (frankf44[at]gmail.com) -0.0 SPF_PASS SPF: sender matches SPF record 0.2 FREEMAIL_ENVFROM_END_DIGIT Envelope-from freemail username ends in digit (frankf44[at]gmail.com) 1.2 MISSING_HEADERS Missing To: header 1.0 HTML_MESSAGE BODY: HTML included in message -0.1 DKIM_VALID_AU Message has a valid DKIM or DK signature from author's domain 0.1 DKIM_SIGNED Message has a DKIM or DK signature, not necessarily valid -0.1 DKIM_VALID Message has at least one valid DKIM or DK signature X-Headers-End: 1VBVlr-0005Hj-I1 Subject: Re: [Bitcoin-development] Proposal: remove "getwork" RPC from bitcoind X-BeenThere: bitcoin-development@lists.sourceforge.net X-Mailman-Version: 2.1.9 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 19 Aug 2013 20:09:49 -0000 --047d7b677efa51198a04e4528551 Content-Type: text/plain; charset=ISO-8859-1 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 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 ===================================================== The causes of my servitude can be traced to the tyranny of money. -Serj Tankian --047d7b677efa51198a04e4528551 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable
I strongly object to removing the only mechanism that allo= ws anyone to say that bitcoin is p2p, in the truest sense of the word. Move= s 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 in= efficient now, is not a good path to start down.

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


On Mon, Aug 19, 201= 3 at 11:27 AM, Jeff Garzik <jgarzik@bitpay.com> wrote:
Pull request https://github.com/bitcoin/bitc= oin/pull/2905 proposes to
remove "getwork" RPC from bitcoind: https://en.bitcoin.it/wiki/Getwork<= br>
On mainnet, almost everybody uses a pool (and therefore, not "getwork&= quot;
directly to bitcoind). =A0Those few who solo mine use a pool server to
talk to bitcoind via "getblocktemplate" or other means. =A0Tests = show
that attempts to solo mine on mainnet via "getwork" lead to delay= s 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. =A0I wanted
to poke the audience, to gauge response to removing "getwork." = =A0If a
driving use case remains of which we're unaware, speak up, please. =A0W= e
don't want to break anybody needlessly.

--
Jeff Garzik
Senior Software Engineer and open source evangelist
BitPay, Inc. =A0 =A0 =A0h= ttps://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/gam= pad/clk?id=3D48897511&iu=3D/4140/ostg.clktrk
_______________________________________________
Bitcoin-development mailing list
Bitcoin-develo= pment@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bitcoin-de= velopment



--
MONEY IS OVER!
=A0=A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 = =A0IF YOU WANT= IT
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D
The causes of my servitude can be traced to the tyranny of mon= ey.
-Serj Tankian
--047d7b677efa51198a04e4528551--