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 <mh.in.england@gmail.com>) id 1RDFkE-0003JK-Uc for bitcoin-development@lists.sourceforge.net; Mon, 10 Oct 2011 13:18:14 +0000 Received-SPF: pass (sog-mx-2.v43.ch3.sourceforge.com: domain of gmail.com designates 74.125.82.41 as permitted sender) client-ip=74.125.82.41; envelope-from=mh.in.england@gmail.com; helo=mail-ww0-f41.google.com; Received: from mail-ww0-f41.google.com ([74.125.82.41]) by sog-mx-2.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128) (Exim 4.76) id 1RDFkE-0003ex-3e for bitcoin-development@lists.sourceforge.net; Mon, 10 Oct 2011 13:18:14 +0000 Received: by wwf10 with SMTP id 10so3642650wwf.4 for <bitcoin-development@lists.sourceforge.net>; Mon, 10 Oct 2011 06:18:08 -0700 (PDT) MIME-Version: 1.0 Received: by 10.216.51.148 with SMTP id b20mr1854541wec.86.1318252687736; Mon, 10 Oct 2011 06:18:07 -0700 (PDT) Sender: mh.in.england@gmail.com Received: by 10.216.137.17 with HTTP; Mon, 10 Oct 2011 06:18:07 -0700 (PDT) In-Reply-To: <201110100905.58725.luke@dashjr.org> References: <CABsx9T2eCpxqzbd0PmWJxCDFLHwOix2BOYp+APQGMZYh_O+R4g@mail.gmail.com> <201110081912.33356.luke@dashjr.org> <CANEZrP1tyxE2inhg2adJHTQTxgNmsB30L8c7874CLZUmHyKYAw@mail.gmail.com> <201110100905.58725.luke@dashjr.org> Date: Mon, 10 Oct 2011 15:18:07 +0200 X-Google-Sender-Auth: paEoK88m-baVovGJTNouun-S_88 Message-ID: <CANEZrP2wyw+951SJxDJyZ0rLNA9UvRJ9a+B7=-jui-w+A0GOWA@mail.gmail.com> From: Mike Hearn <mike@plan99.net> To: Luke-Jr <luke@dashjr.org> Content-Type: multipart/alternative; boundary=0016e6dd977b2d404204aef19f60 X-Spam-Score: -0.5 (/) 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 (mh.in.england[at]gmail.com) -0.0 SPF_PASS SPF: sender matches SPF record 1.0 HTML_MESSAGE BODY: HTML included in message 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: 1RDFkE-0003ex-3e Cc: bitcoin-development@lists.sourceforge.net Subject: Re: [Bitcoin-development] Help wanted: translations 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, 10 Oct 2011 13:18:15 -0000 --0016e6dd977b2d404204aef19f60 Content-Type: text/plain; charset=UTF-8 > > > > As I will no longer be using bitcoind for Eligius soon > > > > What will you be using instead? Isn't bitcoind a requirement for running > a > > pool? > > Writing some custom software designed to more efficiently create work. > To clarify, bitcoind will still serve the purpose of peering with external > nodes and picking out valid transactions to be accepted into blocks; it > just > won't be involved in the primary operations of the pool. > Ah, I see. Sounds a bit like the direction Steve is going with poolserverj. So your custom software would handle incrementing the extraNonce, recalculating the merkle tree/root, and so on? --0016e6dd977b2d404204aef19f60 Content-Type: text/html; charset=UTF-8 <div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;"><div><div class="h5">> > As I will no longer be using bitcoind for Eligius soon<br> ><br> > What will you be using instead? Isn't bitcoind a requirement for running a<br> > pool?<br> <br> </div></div>Writing some custom software designed to more efficiently create work.<br> To clarify, bitcoind will still serve the purpose of peering with external<br> nodes and picking out valid transactions to be accepted into blocks; it just<br> won't be involved in the primary operations of the pool.<br> </blockquote></div><br><div>Ah, I see. Sounds a bit like the direction Steve is going with poolserverj. So your custom software would handle incrementing the extraNonce, recalculating the merkle tree/root, and so on?</div> --0016e6dd977b2d404204aef19f60--