-
Notifications
You must be signed in to change notification settings - Fork 153
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Has anyone here actually succeeded with this app? #93
Comments
Yes they are. |
wondering how to port all necessary code for generating and checking keys (SHA-256, SHA-512, RIPEMD-160, EC Addition, EC Multiplication, etc.,) to OpenCL C, a programming language to run code on a GPU. …I feel like utilizing GPU’s and or ASICs to check keys would be exponentially faster/better @Michal2SAB — have you ever thought about designing this to be more efficient and utilize GPU’s / ASICs? |
This will not work on an ASIC - you will need to design a new chip to do this. |
Try this for GPU use - https://github.com/Vladimir855/Rotor-Cuda |
hello. --range 1:1fffffffff does this mean that it searches through all possible addresses? or what range should be set to iterate over all ranges of addresses that start with the number 1? |
Yes - searches all private keys between 1 and 1fffffffff . Here are some other ranges you can search - |
What range should I specify so that it checks the entire 256 range? |
Rotor-Cuda.exe -t 0 --gpu --gpux 256,256,256,256 --gpui 0,1 -n 256 -f base.bin |
no working. |
.\Rotor-Cuda.exe -t 0 -g --gpui 0 --gpux 256,256 -m addresses --coin BTC -o Found.txt --range 1:1fffffffff -i hash160_out_sorted.bin -r 5 |
How many GPU's do you have? |
-n 256 no working args |
OK - check the examples on github. |
I use this setup - Rotor-Cuda.exe -d 0 -g --gpui 0 --gpux 256,256 -m ADDRESSES --coin BTC -r 656 -n 1 -z 256 -i 1FullAddSorted.bin Are you running this on Windows with Nvidia GPU's ? |
Here is a different version - |
Honestly…lol. The odds seem overwhelmingly tiny…
The text was updated successfully, but these errors were encountered: