📅 Original date posted:2011-09-29
🗒️ Summary of this message: A pull request for deprecating midstate and hash1 in Bitcoin's code has been made to simplify the internal reference miner and remove dependencies on cryptopp.
📝 Original message: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 at nilsschneider.net
> <mailto:nils at 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 at lists.sourceforge.net
> <mailto:Bitcoin-development at lists.sourceforge.net>
> https://lists.sourceforge.net/lists/listinfo/bitcoin-development
>
>
Nils Schneider [ARCHIVE] /
npub177…cxlu5
2023-06-07 02:30:07
in reply to nevent1q…ndag
Author Public Key
npub177jdc67dhsafw0wakj9ggpna5e7ss72vqayua84qgq5lp6x5rr9swcxlu5Published at
2023-06-07 02:30:07Event JSON
{
"id": "3ad43d9082763bcc21f43bd478110761a926147726965b51f1a17b868ff1c3dc",
"pubkey": "f7a4dc6bcdbc3a973dddb48a84067da67d08794c0749ce9ea04029f0e8d418cb",
"created_at": 1686105007,
"kind": 1,
"tags": [
[
"e",
"6491defa1f8d3f8d731a73f0c9e5252dbcef1fa25b10ce935f3278c866036399",
"",
"root"
],
[
"e",
"aa149991c3c529bd73b0841cc040ef3a922cf653bea13baa5584f47ffea5d1d1",
"",
"reply"
],
[
"p",
"cd7fc091d5673974c36bf2b5c6e8b4a5079d6821b95f6719fd48571aeb25b785"
]
],
"content": "📅 Original date posted:2011-09-29\n🗒️ Summary of this message: A pull request for deprecating midstate and hash1 in Bitcoin's code has been made to simplify the internal reference miner and remove dependencies on cryptopp.\n📝 Original message:Yes, that's possible and what\nhttps://github.com/bitcoin/bitcoin/pull/535 does. However, deprecating\nmidstate (and hash1) would allow for much cleaner code.\n\nA pull request for marking midstate (and hash1) as deprecated can be\nfound at https://github.com/bitcoin/bitcoin/pull/538\n\nOn 29.09.2011 12:23, John Smith wrote:\n\u003e Nils,\n\u003e \n\u003e Sounds good. I'm also doubtful of depending on two crypto libraries when\n\u003e OpenSSL does perfectly well.\n\u003e \n\u003e However, losing compatibility with miners is not very nice. Is there\n\u003e really not a way to compute midstate with OpenSSL?\n\u003e \n\u003e JS\n\u003e \n\u003e On Mon, Sep 26, 2011 at 7:42 PM, Nils Schneider \u003cnils at nilsschneider.net\n\u003e \u003cmailto:nils at nilsschneider.net\u003e\u003e wrote:\n\u003e \n\u003e Hey,\n\u003e \n\u003e I'd like to simplify the internal reference miner and remove all\n\u003e dependencies on cryptopp (it's the only place we use cryptopp instead of\n\u003e OpenSSL).\n\u003e \n\u003e Unfortunately, cryptopp is also used to calculate getwork \"midstate\".\n\u003e This field is redundant and the miner could easily calculate it from the\n\u003e blockheader so I'd like to remove it.\n\u003e \n\u003e Any thoughts? Where should such a change should be announced so all\n\u003e miners can be upgraded?\n\u003e \n\u003e ------------------------------------------------------------------------------\n\u003e All the data continuously generated in your IT infrastructure contains a\n\u003e definitive record of customers, application performance, security\n\u003e threats, fraudulent activity and more. Splunk takes this data and makes\n\u003e sense of it. Business sense. IT sense. Common sense.\n\u003e http://p.sf.net/sfu/splunk-d2dcopy1\n\u003e _______________________________________________\n\u003e Bitcoin-development mailing list\n\u003e Bitcoin-development at lists.sourceforge.net\n\u003e \u003cmailto:Bitcoin-development at lists.sourceforge.net\u003e\n\u003e https://lists.sourceforge.net/lists/listinfo/bitcoin-development\n\u003e \n\u003e",
"sig": "e3a7a30b2f581cfe8d4a4c0ade5313ea2f9e8f4737029e187bffdc58b9b89f730033a60f5bc1ee16a98bd377701c255cddbb8278705be7bd58b595a2d53147be"
}