Received: from sog-mx-2.v43.ch3.sourceforge.com ([172.29.43.192] helo=mx.sourceforge.net) by sfs-ml-1.v29.ch3.sourceforge.com with esmtp (Exim 4.76) (envelope-from ) id 1RAGr9-0003dK-35 for bitcoin-development@lists.sourceforge.net; Sun, 02 Oct 2011 07:53:03 +0000 Received-SPF: pass (sog-mx-2.v43.ch3.sourceforge.com: domain of gmail.com designates 209.85.213.47 as permitted sender) client-ip=209.85.213.47; envelope-from=witchspace81@gmail.com; helo=mail-yw0-f47.google.com; Received: from mail-yw0-f47.google.com ([209.85.213.47]) by sog-mx-2.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-MD5:128) (Exim 4.76) id 1RAGr8-00038E-9J for bitcoin-development@lists.sourceforge.net; Sun, 02 Oct 2011 07:53:02 +0000 Received: by ywf7 with SMTP id 7so3199926ywf.34 for ; Sun, 02 Oct 2011 00:52:57 -0700 (PDT) MIME-Version: 1.0 Received: by 10.150.113.18 with SMTP id l18mr12830711ybc.222.1317541976875; Sun, 02 Oct 2011 00:52:56 -0700 (PDT) Received: by 10.150.57.13 with HTTP; Sun, 2 Oct 2011 00:52:56 -0700 (PDT) In-Reply-To: References: <4E80D591.2080100@nilsschneider.net> <4E845935.8060601@nilsschneider.net> <4E845B09.8040400@justmoon.de> Date: Sun, 2 Oct 2011 07:52:56 +0000 Message-ID: From: John Smith To: solar Content-Type: multipart/alternative; boundary=000e0cd5c6de82219804ae4c25bf 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 (witchspace81[at]gmail.com) -0.0 SPF_PASS SPF: sender matches SPF record 0.1 FREEMAIL_ENVFROM_END_DIGIT Envelope-from freemail username ends in digit (witchspace81[at]gmail.com) 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: 1RAGr8-00038E-9J Cc: bitcoin-development@lists.sourceforge.net Subject: Re: [Bitcoin-development] Deprecating "midstate" in getwork? 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: Sun, 02 Oct 2011 07:53:03 -0000 --000e0cd5c6de82219804ae4c25bf Content-Type: text/plain; charset=ISO-8859-1 On Thu, Sep 29, 2011 at 12:49 PM, solar wrote: > It's just simple SHA2, you can implement the whole thing easily without > dragging in a huge lib like OpenSSL. I guess I haven't looked at it > recently but the original CPU miner was just implemented locally in bitcoin > and didn't use any libs. > I don't get the 'dragging in' part. Bitcoin already depends on OpenSSL for ecdsa, bignum, and SSL for RPC. Please, please don't try to reimplement these locally :-) JS --000e0cd5c6de82219804ae4c25bf Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable
On Thu, Sep 29, 2011 at 12:49 PM, solar <solar@heliacal.net<= /a>> wrote:
It's just simple SHA2, you can implement the whole thing easily without= dragging in a huge lib like OpenSSL. =A0I guess I haven't looked at it= recently but the original CPU miner was just implemented locally in bitcoi= n and didn't use any libs.

I don't get the 'dragging in' part. Bitco= in already depends on OpenSSL for ecdsa, bignum, and SSL for RPC. Please, p= lease don't try to reimplement these locally :-)

JS

--000e0cd5c6de82219804ae4c25bf--