Received: from sog-mx-2.v43.ch3.sourceforge.com ([172.29.43.192] helo=mx.sourceforge.net) by sfs-ml-3.v29.ch3.sourceforge.com with esmtp (Exim 4.76) (envelope-from <frankf44@gmail.com>) id 1VBVu1-0006VP-HF for bitcoin-development@lists.sourceforge.net; Mon, 19 Aug 2013 20:18:13 +0000 Received-SPF: pass (sog-mx-2.v43.ch3.sourceforge.com: domain of gmail.com designates 209.85.128.178 as permitted sender) client-ip=209.85.128.178; envelope-from=frankf44@gmail.com; helo=mail-ve0-f178.google.com; Received: from mail-ve0-f178.google.com ([209.85.128.178]) by sog-mx-2.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128) (Exim 4.76) id 1VBVu0-0005c0-Do for bitcoin-development@lists.sourceforge.net; Mon, 19 Aug 2013 20:18:13 +0000 Received: by mail-ve0-f178.google.com with SMTP id ox1so3280250veb.23 for <bitcoin-development@lists.sourceforge.net>; Mon, 19 Aug 2013 13:18:07 -0700 (PDT) MIME-Version: 1.0 X-Received: by 10.59.8.232 with SMTP id dn8mr14756691ved.8.1376943486900; Mon, 19 Aug 2013 13:18:06 -0700 (PDT) Received: by 10.220.165.201 with HTTP; Mon, 19 Aug 2013 13:18:06 -0700 (PDT) In-Reply-To: <CAAS2fgQRcfbe+3A6_t4s8BJRaWwmLdKkGG1ePmG+Epm5W6CxdQ@mail.gmail.com> References: <CAJHLa0MnnWw=qiYC0nJcY=BdTDcAjGtraJ+kazoG7_bHW-HBtw@mail.gmail.com> <CALxyHsXoCqL8dNXeayibfbR7-JU6Ke19gJJ1fToboULdUa155Q@mail.gmail.com> <CAAS2fgQRcfbe+3A6_t4s8BJRaWwmLdKkGG1ePmG+Epm5W6CxdQ@mail.gmail.com> Date: Mon, 19 Aug 2013 15:18:06 -0500 Message-ID: <CALxyHsVtAqWtS6supU9L0Y7RgD0AKychQFQMTcf2fvDteJ4B3A@mail.gmail.com> From: Frank F <frankf44@gmail.com> Cc: Bitcoin Dev <bitcoin-development@lists.sourceforge.net> Content-Type: multipart/alternative; boundary=047d7bd75d5c69a2c704e452a3f7 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: 1VBVu0-0005c0-Do 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: <bitcoin-development.lists.sourceforge.net> List-Unsubscribe: <https://lists.sourceforge.net/lists/listinfo/bitcoin-development>, <mailto:bitcoin-development-request@lists.sourceforge.net?subject=unsubscribe> List-Archive: <http://sourceforge.net/mailarchive/forum.php?forum_name=bitcoin-development> List-Post: <mailto:bitcoin-development@lists.sourceforge.net> List-Help: <mailto:bitcoin-development-request@lists.sourceforge.net?subject=help> List-Subscribe: <https://lists.sourceforge.net/lists/listinfo/bitcoin-development>, <mailto:bitcoin-development-request@lists.sourceforge.net?subject=subscribe> X-List-Received-Date: Mon, 19 Aug 2013 20:18:13 -0000 --047d7bd75d5c69a2c704e452a3f7 Content-Type: text/plain; charset=ISO-8859-1 This sounds like an ideal compromise. On Mon, Aug 19, 2013 at 3:16 PM, Gregory Maxwell <gmaxwell@gmail.com> wrote: > On Mon, Aug 19, 2013 at 1:09 PM, Frank F <frankf44@gmail.com> wrote: > > If there are technical problems with getwork, maybe they should be > addressed > > and fixed instead of outright abandoned. > > They have been, resulting in a replacement called "getblocktemplate" > which (presumably) almost everyone talking to bitcoin(d|-qt) has been > using for a long time. > > I think removing the ability to mine in the stock package would be > regrettable, but to be honest we already don't have it for the > mainnet. I think we should do as Jeff suggests and remove getwork. But > I think we should also package along a proper getblocktemplate miner > to remove any doubt that we're providing a full network node here. (I > note that the choice of miner is also easy: Regardless of people's > preferences which way or another, AFAIK only luke's bfgminer stuff can > mine directly against bitcoin getblocktemplate with no pool in the > middle. It also supports a huge variety of hardware, and a superset > of our target platforms) > -- *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 --047d7bd75d5c69a2c704e452a3f7 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable <div dir=3D"ltr">This sounds like an ideal compromise.</div><div class=3D"g= mail_extra"><br><br><div class=3D"gmail_quote">On Mon, Aug 19, 2013 at 3:16= PM, Gregory Maxwell <span dir=3D"ltr"><<a href=3D"mailto:gmaxwell@gmail= .com" target=3D"_blank">gmaxwell@gmail.com</a>></span> wrote:<br> <blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p= x #ccc solid;padding-left:1ex"><div class=3D"im">On Mon, Aug 19, 2013 at 1:= 09 PM, Frank F <<a href=3D"mailto:frankf44@gmail.com">frankf44@gmail.com= </a>> wrote:<br> > If there are technical problems with getwork, maybe they should be add= ressed<br> > and fixed instead of outright abandoned.<br> <br> </div>They have been, resulting in a replacement called "getblocktempl= ate"<br> which (presumably) almost everyone talking to bitcoin(d|-qt) has been<br> using for a long time.<br> <br> I think removing the ability to mine in the stock package would be<br> regrettable, but to be honest we already don't have it for the<br> mainnet. I think we should do as Jeff suggests and remove getwork. But<br> I think we should also package along a proper getblocktemplate miner<br> to remove any doubt that we're providing a full network node here. =A0(= I<br> note that the choice of miner is also easy: =A0Regardless of people's<b= r> preferences which way or another, AFAIK only luke's bfgminer stuff can<= br> mine directly against bitcoin getblocktemplate with no pool in the<br> middle. =A0It also supports a huge variety of hardware, and a superset<br> of our target platforms)<br> </blockquote></div><br><br clear=3D"all"><div><br></div>-- <br><div style= =3D"text-align:left"><b><span style=3D"font-size:xx-large">MONEY IS OVER!</= span></b></div><div><div style=3D"text-align:left"><span style=3D"font-size= :x-small">=A0=A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 = =A0<a href=3D"http://www.zeitgeistmovie.com/" target=3D"_blank">IF YOU WANT= IT</a></span></div> =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<br>The causes of my servitude can be traced to the tyranny of mon= ey.<br>-Serj Tankian</div> </div> --047d7bd75d5c69a2c704e452a3f7--