You use CudaBrainSecp by simply running ./CudaBrainSecp

There are no other commands, so it's very simple - only the configuration file GPUSecp.h

If the test cases are running succesfully then you can replace the test books / hashes with your books / hashes and try recovering your desired keys.

Please look in Real Launch section about how to do it.

As for compilation issues - i agree the compilation is not very simple and can result in various unexpected errors, mostly due to the complexity of Cuda / gcc / nvcc.

I have very limited knowledge of Cuda compilation / makefiles, however i did the best i could to describe the compilation process in Quick Setup section, and fully tested the project on two different Nvidia GPUs (Ubuntu 22.04)

I can suggest compiling the Nvidia Cuda sample project (https://github.com/NVIDIA/cuda-samples)

It is an excellent source of information about building cuda projects - and explains many different edge cases.

If the private key is hashed then the GPU kernel can't simply re-use an existing public key.
Re-using a public key would be ideal, since that would allow doing one point-addition + modular inverse to obtain the next public key.
However since the private key is hashed then there is no way of knowing which is the correct point-addition (which point-addition would result in the next private key that you wish to check).
It is nearly impossible because it would be the same as guessing a 256-bit number (which is technically not impossible).

I should probably make that paragraph more clear and understandable.

Thanks!

Development on this tool has been paused.