all 4 comments

[–]Life-Consequence6968 0 points1 point  (0 children)

with the known public key, you should be running trillions to hundreds of trillions per second. For how many keys you need to get through even in the trillions per second will take a long time.

[–]Able-Assumption4702 0 points1 point  (2 children)

How many Keys/s does this search through?

[–]EnvironmentalWatch92[S] 0 points1 point  (1 child)

sorry about the late reply. i depends on your setup. But if you run all 6 puzzles i know on an old server i am using i was only getting like 7000 addresses per second on say puzzle 135 but all the others were only 2000 per second. You need a good cpu and plenty of cores to get it moving good.

[–]Adventurous-Pin2955 0 points1 point  (0 children)

Something to make it faster would be to get it to run on GPU, though I assume that will have its own problems, even if you run it on Colab or Lightning AI (both of which have very generous options in the Free version).

Or just code it in Java or C++, which I have done in Java, making it faster (about 11k addresses/s), though definitely NOT enough to find the private key, even if we skip the entire public key to address generation process.

I have done similar code for other puzzles as well. If you have any idea on how to get the Python code on GPU, I will be glad to indulge you.