Received: from sog-mx-3.v43.ch3.sourceforge.com ([172.29.43.193] helo=mx.sourceforge.net) by sfs-ml-2.v29.ch3.sourceforge.com with esmtp (Exim 4.76) (envelope-from ) id 1R9DmI-0001eF-MY for bitcoin-development@lists.sourceforge.net; Thu, 29 Sep 2011 10:23:42 +0000 Received-SPF: pass (sog-mx-3.v43.ch3.sourceforge.com: domain of gmail.com designates 209.85.213.175 as permitted sender) client-ip=209.85.213.175; envelope-from=witchspace81@gmail.com; helo=mail-yx0-f175.google.com; Received: from mail-yx0-f175.google.com ([209.85.213.175]) by sog-mx-3.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128) (Exim 4.76) id 1R9DmE-0002jl-Gj for bitcoin-development@lists.sourceforge.net; Thu, 29 Sep 2011 10:23:42 +0000 Received: by yxj17 with SMTP id 17so534227yxj.34 for ; Thu, 29 Sep 2011 03:23:33 -0700 (PDT) MIME-Version: 1.0 Received: by 10.150.50.11 with SMTP id x11mr3177937ybx.279.1317291813003; Thu, 29 Sep 2011 03:23:33 -0700 (PDT) Received: by 10.150.57.13 with HTTP; Thu, 29 Sep 2011 03:23:32 -0700 (PDT) In-Reply-To: <4E80D591.2080100@nilsschneider.net> References: <4E80D591.2080100@nilsschneider.net> Date: Thu, 29 Sep 2011 10:23:32 +0000 Message-ID: From: John Smith To: Nils Schneider Content-Type: multipart/alternative; boundary=000e0cd6a6f094626604ae11e644 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 0.0 AWL AWL: From: address is in the auto white-list X-Headers-End: 1R9DmE-0002jl-Gj 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: Thu, 29 Sep 2011 10:23:42 -0000 --000e0cd6a6f094626604ae11e644 Content-Type: text/plain; charset=ISO-8859-1 Nils, Sounds good. I'm also doubtful of depending on two crypto libraries when OpenSSL does perfectly well. However, losing compatibility with miners is not very nice. Is there really not a way to compute midstate with OpenSSL? JS On Mon, Sep 26, 2011 at 7:42 PM, Nils Schneider wrote: > Hey, > > I'd like to simplify the internal reference miner and remove all > dependencies on cryptopp (it's the only place we use cryptopp instead of > OpenSSL). > > Unfortunately, cryptopp is also used to calculate getwork "midstate". > This field is redundant and the miner could easily calculate it from the > blockheader so I'd like to remove it. > > Any thoughts? Where should such a change should be announced so all > miners can be upgraded? > > > ------------------------------------------------------------------------------ > All the data continuously generated in your IT infrastructure contains a > definitive record of customers, application performance, security > threats, fraudulent activity and more. Splunk takes this data and makes > sense of it. Business sense. IT sense. Common sense. > http://p.sf.net/sfu/splunk-d2dcopy1 > _______________________________________________ > Bitcoin-development mailing list > Bitcoin-development@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/bitcoin-development > --000e0cd6a6f094626604ae11e644 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Nils,

Sounds good. I'm also doubtful of depending on two crypto = libraries when OpenSSL does perfectly well.

However, losing compati= bility with miners is not very nice. Is there really not a way to compute m= idstate with OpenSSL?

JS

On Mon, Sep 26, 2011 at 7:42 PM, N= ils Schneider <nils@nilsschneider.net> wrote:
Hey,

I'd like to simplify the internal reference miner and remove all
dependencies on cryptopp (it's the only place we use cryptopp instead o= f
OpenSSL).

Unfortunately, cryptopp is also used to calculate getwork "midstate&qu= ot;.
This field is redundant and the miner could easily calculate it from the blockheader so I'd like to remove it.

Any thoughts? Where should such a change should be announced so all
miners can be upgraded?

---------------------------------------------------------------------------= ---
All the data continuously generated in your IT infrastructure contains a definitive record of customers, application performance, security
threats, fraudulent activity and more. Splunk takes this data and makes
sense of it. Business sense. IT sense. Common sense.
http://p.= sf.net/sfu/splunk-d2dcopy1
_______________________________________________
Bitcoin-development mailing list
Bitcoin-develo= pment@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bitcoin-de= velopment

--000e0cd6a6f094626604ae11e644--