From mboxrd@z Thu Jan 1 00:00:00 1970 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 1VBYu4-0007Oy-VC for bitcoin-development@lists.sourceforge.net; Mon, 19 Aug 2013 23:30:29 +0000 Received-SPF: pass (sog-mx-2.v43.ch3.sourceforge.com: domain of gmail.com designates 209.85.160.45 as permitted sender) client-ip=209.85.160.45; envelope-from=wtogami@gmail.com; helo=mail-pb0-f45.google.com; Received: from mail-pb0-f45.google.com ([209.85.160.45]) by sog-mx-2.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128) (Exim 4.76) id 1VBYu3-0006ht-Jf for bitcoin-development@lists.sourceforge.net; Mon, 19 Aug 2013 23:30:28 +0000 Received: by mail-pb0-f45.google.com with SMTP id mc17so5545446pbc.4 for ; Mon, 19 Aug 2013 16:30:21 -0700 (PDT) MIME-Version: 1.0 X-Received: by 10.68.189.228 with SMTP id gl4mr15872198pbc.57.1376955021683; Mon, 19 Aug 2013 16:30:21 -0700 (PDT) Received: by 10.66.72.225 with HTTP; Mon, 19 Aug 2013 16:30:21 -0700 (PDT) In-Reply-To: References: Date: Mon, 19 Aug 2013 13:30:21 -1000 Message-ID: From: "Warren Togami Jr." To: Andreas Schildbach Content-Type: multipart/alternative; boundary=e89a8ff1cad2f0763e04e45552d7 X-Spam-Score: -0.6 (/) 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 (wtogami[at]gmail.com) -0.0 SPF_PASS SPF: sender matches SPF record 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: 1VBYu3-0006ht-Jf Cc: Bitcoin Dev 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 23:30:29 -0000 --e89a8ff1cad2f0763e04e45552d7 Content-Type: text/plain; charset=UTF-8 Hence ship a miner that automatically reads the bitcoin.conf to find the RPC authentication info. It would be faster and more efficient than the unoptimized miner while simplifying the bitcoind code. Win for everyone. Warren On Mon, Aug 19, 2013 at 1:02 PM, Andreas Schildbach wrote: > 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. > > > > > ------------------------------------------------------------------------------ > 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 > --e89a8ff1cad2f0763e04e45552d7 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
Hence ship a miner that automatically reads the bitcoin.co= nf to find the RPC authentication info. =C2=A0It would be faster and more e= fficient than the unoptimized miner while simplifying the bitcoind code. = =C2=A0Win for everyone.

Warren


On Mon, Aug 19, 2013 at 1:02 PM, Andreas Schildbach <andreas@schildbach.de> wrote:
On 08/19/2013 10:34 PM, Je= ff Garzik wrote:

>> FWIW, Litecoin 0.8.x entirely removed the internal miner and we wa= rned
>> people that getwork will be removed in the next major version. =C2= =A0Pooler's CPU
>> minerd which supports both sha256d and scrypt recently grew stratu= m 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 i= s.

I think it'd be a pity if the easy way to mine blocks would be removed.=



---------------------------------------------------------------------------= ---
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

--e89a8ff1cad2f0763e04e45552d7--