Post
Topic
Board Development & Technical Discussion
Re: BitCrack - A tool for brute-forcing private keys
by
WanderingPhilospher
on 30/01/2023, 01:27:26 UTC
Exactly that's right!
Yes nice result but you have 6 nice GPUs . With one GPU let's say you would have taken about 15 min it's a good result

Well I did say in my original post, "As always, it depends on the program you are running and how much hardware you have."

That was a 48 bit range; which could take up to 4-5 hours to check every key, so I leaned on the side of caution and ran with 6 GPUs lol...

Thank you for the testing of 14 missing characters, I appreciate it.


Quote
wif  (the last 17 are missing)
KwRPC6Be7ukp2fh4rVYU4GrmfSdCweo2RxL

Compressed address
1MpqX7tzAWAo1bZv6msHM3mkQ6fHFh2mjE

That's a 60 bit range C018588C2B6CC47... I'm gonna have to pass on that one lol.

Can you insert for example the command line you used to perform this search and can you use it randomly?

Sure, no problem:

Code:
VBCr.exe -stop -t 0 -drk 1 -dis 1 -gpu -g 480,512 -r 2900 -begr 6013a6d9493032a55781798cbba36961d73fb72d4a86ac940fcecb3e9857bf1 -endr 6013a6d9493032a55781798cbba36961d73fb72d4a86ac94cfe723cac3c4838 1MpqX7tzAWAo1bZv6msHM3mkQ6fHFh2mjE
pause

Note: This is searching with a GPU. You can change it to CPU by adding -t 4 (or whatever number of cores you want to use) and deleting the -gpu, -g flags.  You can also redo the -r flag to however often you want the CPU/GPU to generate new random keys. The -r is in millions so if you use -r 10, it will generate new random keys after 10,000,000 keys have been checked.

Thanks. can you put an example of using the -rp command?

https://github.com/JeanLucPons/VanitySearch#step-1