For wallet #120, when generating the Bitcoin address from the private keys found by Keyhunt, it does not reach the Bitcoin address presented for the wallet on the challenge website.
Shouldn't it be the same address?
The 120 keys/address for the keyhunt documentation are examplest to test the speed. Please Read and
Understand the documentation before running it without know what are you doing.
I have been studying BSGS, and Pollard's Kangaroo methods for a while now. I have made an observation trying to mix BSGS with the Kangaroo method that I believe could be helpful.
I need time to understand what are you doing, because right now Kangaroo its still a mystery for me. So i CANT say anything about what you write
I am newbie to keyhunt. I have 32gb ram and rtx4070. While running the command line as ->
./keyhunt -t 8 -m address -f abc.txt -r (from hexadecimal to hexadecimal) -q -s 10 -k 2048 -R
the speed is 5564110 keys/s. I wanna to scan backwards because I think the target address is nearest to back end of the range. Please suggest what is the most efficient command line I need to follow. Thanks
Kehunt is for CPU only, so you GPU model doesn't have anything to do here.
For address there is no backwards mode, if you believe that your target is near of the end, THEN select a sub-range that is near of the desire range and not the whole range....
Thanks for reply.