public inbox for bitcoindev@googlegroups.com
 help / color / mirror / Atom feed
From: Nils Schneider <nils@nilsschneider.net>
To: John Smith <witchspace81@gmail.com>
Cc: bitcoin-development@lists.sourceforge.net
Subject: Re: [Bitcoin-development] Deprecating "midstate" in getwork?
Date: Thu, 29 Sep 2011 13:40:37 +0200	[thread overview]
Message-ID: <4E845935.8060601@nilsschneider.net> (raw)
In-Reply-To: <CAJNQ0stW-7HMw-O_C9Go8ViRrxBNtEpsbhSRyc3aOzm6OvR6dA@mail.gmail.com>

Yes, that's possible and what
https://github.com/bitcoin/bitcoin/pull/535 does. However, deprecating
midstate (and hash1) would allow for much cleaner code.

A pull request for marking midstate (and hash1) as deprecated can be
found at https://github.com/bitcoin/bitcoin/pull/538

On 29.09.2011 12:23, John Smith wrote:
> 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 <nils@nilsschneider.net
> <mailto: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 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
>     <mailto:Bitcoin-development@lists.sourceforge.net>
>     https://lists.sourceforge.net/lists/listinfo/bitcoin-development
> 
> 




  reply	other threads:[~2011-09-29 11:40 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-09-26 19:42 [Bitcoin-development] Deprecating "midstate" in getwork? Nils Schneider
2011-09-28  3:45 ` Jeff Garzik
2011-09-28  3:54   ` Luke-Jr
2011-09-29 10:23 ` John Smith
2011-09-29 11:40   ` Nils Schneider [this message]
2011-09-29 11:48     ` Stefan Thomas
2011-09-29 12:49       ` solar
2011-10-02  7:52         ` John Smith

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4E845935.8060601@nilsschneider.net \
    --to=nils@nilsschneider.net \
    --cc=bitcoin-development@lists.sourceforge.net \
    --cc=witchspace81@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox