Re: [Bitcoin-development] Deprecating "midstate" in getwork?

[Nils Schneider <nils@nilsschneider.net>]

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
> 
>