TheCharlatan on Nostr: No, but I'm pretty sure a single hash would be slower in any case with all the time ...
No, but I'm pretty sure a single hash would be slower in any case with all the time spent getting the data to the GPU and getting back the result. Mining is kind of unique, because you can really massively parallelize the hashing. Maybe you could parallelize the required hash work between the various scripts in a block and e.g. pre-compute the required sighashes in parallel. For merkle trees it is a bit ambiguous, since you have interim results that you'd have to share between jobs. My intuition is it would not be worth it.
Published at
2024-12-14 14:08:31Event JSON
{
"id": "63348ec2e340f65408fd939f0559597ac149ca35372c05b691a8ee7eb7a14ec0",
"pubkey": "2eb03a1f316c3cf9c900e7f536ee28e5486349067be018a965a7c7ca5b4f7f3c",
"created_at": 1734185311,
"kind": 1,
"tags": [
[
"e",
"80586fcac58d2d47d3b94cd9d8492f8442eea39a525ba55ff724f4d7822146fd",
"",
"root"
],
[
"p",
"8685ebef665338dd6931e2ccdf3c19d9f0e5a1067c918f22e7081c2558f8faf8"
]
],
"content": "No, but I'm pretty sure a single hash would be slower in any case with all the time spent getting the data to the GPU and getting back the result. Mining is kind of unique, because you can really massively parallelize the hashing. Maybe you could parallelize the required hash work between the various scripts in a block and e.g. pre-compute the required sighashes in parallel. For merkle trees it is a bit ambiguous, since you have interim results that you'd have to share between jobs. My intuition is it would not be worth it.",
"sig": "9352a7e58fdbdfbe58f4db50850752fb1ecc41a9d3b315bc52e3ad29e08e52dc3ca5f46b4a5b326b68d1c138674ceb73466b093b3fa8f2ae0be561c16805272e"
}
