š
Original date posted:2011-09-29
šļø Summary of this message: The original CPU miner for Bitcoin didn't use any libraries like OpenSSL, and it's possible to implement SHA2 without it.
š Original message: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.
It's just that because it's block based, there is no need to ever recalculate the first half since the brute forcing value is in the second half of the block..
This was the original prototype for the OpenCL miner without eliminating redundant calculations and it shows the block1 and block2 calculations clearly.
http://heliacal.net/~solar/bitcoin/sha256.cl
Laszlo
On Sep 29, 2011, at 11:48 AM, Stefan Thomas wrote:
> BitcoinJS uses OpenSSL to calculate midstate:
>
> https://github.com/bitcoinjs/node-bitcoin-p2p/blob/master/native.cc#L380
>
>
> On 9/29/2011 1:40 PM, Nils Schneider wrote:
>> 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
>>>
>>>
>>
>> ------------------------------------------------------------------------------
>> 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
>> https://lists.sourceforge.net/lists/listinfo/bitcoin-development
>>
>
>
> ------------------------------------------------------------------------------
> 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
> https://lists.sourceforge.net/lists/listinfo/bitcoin-development
solar [ARCHIVE] /
npub1vfā¦a8meq
2023-06-07 02:30:14
in reply to nevent1qā¦7udf
Author Public Key
npub1vf6uu3xanv8q5tt7vckle9s3e3z2zzkce5p5pr6x47nh32xwcj8q8a8meqPublished at
2023-06-07 02:30:14Event JSON
{
"id": "feb458093a16eaf55eaf8513262f516ce985f3f8fef1c05a2516d26dd6b6d811",
"pubkey": "6275ce44dd9b0e0a2d7e662dfc9611cc44a10ad8cd03408f46afa778a8cec48e",
"created_at": 1686105014,
"kind": 1,
"tags": [
[
"e",
"6491defa1f8d3f8d731a73f0c9e5252dbcef1fa25b10ce935f3278c866036399",
"",
"root"
],
[
"e",
"474bdd738ccf7b84addb598b58197ccc4e8bc950dcdca4d276e32b1952f95b82",
"",
"reply"
],
[
"p",
"49f07bd32c0108a2903a0fa59f904ed312e0ea427d3269eb5fa910eb4a9e22c4"
]
],
"content": "š
Original date posted:2011-09-29\nšļø Summary of this message: The original CPU miner for Bitcoin didn't use any libraries like OpenSSL, and it's possible to implement SHA2 without it.\nš Original message: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.\n\nIt's just that because it's block based, there is no need to ever recalculate the first half since the brute forcing value is in the second half of the block..\n\nThis was the original prototype for the OpenCL miner without eliminating redundant calculations and it shows the block1 and block2 calculations clearly.\n\nhttp://heliacal.net/~solar/bitcoin/sha256.cl\n\nLaszlo\n\nOn Sep 29, 2011, at 11:48 AM, Stefan Thomas wrote:\n\n\u003e BitcoinJS uses OpenSSL to calculate midstate:\n\u003e \n\u003e https://github.com/bitcoinjs/node-bitcoin-p2p/blob/master/native.cc#L380\n\u003e \n\u003e \n\u003e On 9/29/2011 1:40 PM, Nils Schneider wrote:\n\u003e\u003e Yes, that's possible and what\n\u003e\u003e https://github.com/bitcoin/bitcoin/pull/535 does. However, deprecating\n\u003e\u003e midstate (and hash1) would allow for much cleaner code.\n\u003e\u003e \n\u003e\u003e A pull request for marking midstate (and hash1) as deprecated can be\n\u003e\u003e found at https://github.com/bitcoin/bitcoin/pull/538\n\u003e\u003e \n\u003e\u003e On 29.09.2011 12:23, John Smith wrote:\n\u003e\u003e\u003e Nils,\n\u003e\u003e\u003e \n\u003e\u003e\u003e Sounds good. I'm also doubtful of depending on two crypto libraries when\n\u003e\u003e\u003e OpenSSL does perfectly well.\n\u003e\u003e\u003e \n\u003e\u003e\u003e However, losing compatibility with miners is not very nice. Is there\n\u003e\u003e\u003e really not a way to compute midstate with OpenSSL?\n\u003e\u003e\u003e \n\u003e\u003e\u003e JS\n\u003e\u003e\u003e \n\u003e\u003e\u003e On Mon, Sep 26, 2011 at 7:42 PM, Nils Schneider\u003cnils at nilsschneider.net\n\u003e\u003e\u003e \u003cmailto:nils at nilsschneider.net\u003e\u003e wrote:\n\u003e\u003e\u003e \n\u003e\u003e\u003e Hey,\n\u003e\u003e\u003e \n\u003e\u003e\u003e I'd like to simplify the internal reference miner and remove all\n\u003e\u003e\u003e dependencies on cryptopp (it's the only place we use cryptopp instead of\n\u003e\u003e\u003e OpenSSL).\n\u003e\u003e\u003e \n\u003e\u003e\u003e Unfortunately, cryptopp is also used to calculate getwork \"midstate\".\n\u003e\u003e\u003e This field is redundant and the miner could easily calculate it from the\n\u003e\u003e\u003e blockheader so I'd like to remove it.\n\u003e\u003e\u003e \n\u003e\u003e\u003e Any thoughts? Where should such a change should be announced so all\n\u003e\u003e\u003e miners can be upgraded?\n\u003e\u003e\u003e \n\u003e\u003e\u003e ------------------------------------------------------------------------------\n\u003e\u003e\u003e All the data continuously generated in your IT infrastructure contains a\n\u003e\u003e\u003e definitive record of customers, application performance, security\n\u003e\u003e\u003e threats, fraudulent activity and more. Splunk takes this data and makes\n\u003e\u003e\u003e sense of it. Business sense. IT sense. Common sense.\n\u003e\u003e\u003e http://p.sf.net/sfu/splunk-d2dcopy1\n\u003e\u003e\u003e _______________________________________________\n\u003e\u003e\u003e Bitcoin-development mailing list\n\u003e\u003e\u003e Bitcoin-development at lists.sourceforge.net\n\u003e\u003e\u003e \u003cmailto:Bitcoin-development at lists.sourceforge.net\u003e\n\u003e\u003e\u003e https://lists.sourceforge.net/lists/listinfo/bitcoin-development\n\u003e\u003e\u003e \n\u003e\u003e\u003e \n\u003e\u003e \n\u003e\u003e ------------------------------------------------------------------------------\n\u003e\u003e All the data continuously generated in your IT infrastructure contains a\n\u003e\u003e definitive record of customers, application performance, security\n\u003e\u003e threats, fraudulent activity and more. Splunk takes this data and makes\n\u003e\u003e sense of it. Business sense. IT sense. Common sense.\n\u003e\u003e http://p.sf.net/sfu/splunk-d2dcopy1\n\u003e\u003e _______________________________________________\n\u003e\u003e Bitcoin-development mailing list\n\u003e\u003e Bitcoin-development at lists.sourceforge.net\n\u003e\u003e https://lists.sourceforge.net/lists/listinfo/bitcoin-development\n\u003e\u003e \n\u003e \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 https://lists.sourceforge.net/lists/listinfo/bitcoin-development",
"sig": "8d81b630285e7e15cf5f45d4dd5b9add99505e7b8597a71ae2557e98e059509462f321594914e888b08792aaed929614eb059ddc80314ef49473f30c42e38d29"
}