BitCrack - A tool for brute-forcing private keys

[7isce]

Thanks for your kind help!  

I did the steps but i got this error message:

PS C:\Users\me> python c:/keyhunt/addresses_to_hash160.py 64puzzle.txt 64puzzle.bin
Traceback (most recent call last):
  File "c:/keyhunt/addresses_to_hash160.py", line 4, in <module>
    import base58
ModuleNotFoundError: No module named 'base58'

I installed in visual studio the Base58 module from https://marketplace.visualstudio.com/items?itemName=crossjs.base58&utm_source=www.vsixhub.com

I copied in c:/keyhunt the base58.cpp base58.h base58.obj toobut i got the same error.  

Can you help me to fix it?

Its a easy thing to do in python, just use pip(python package manager) to install any module you want.
type in terminal:
"pip install base58" OR "pip3 install base58" it depend on your system.

And that's it. now you can just run addresses_to_hash160.py without any error.

[1714768303]

1714768303

[1714768303]

1714768303

[1714768303]

1714768303

[KudilCumil]

hi,..
what command to use all available devices for job.
i have 8 devices on list, but when im using
--device 0,1,2,3,4,5,6,7
it running but it only show 1 device
thank you

[7isce]

hi,..
what command to use all available devices for job.
i have 8 devices on list, but when im using
--device 0,1,2,3,4,5,6,7
it running but it only show 1 device
thank you

Which program you use?

[KudilCumil]

Which program you use?

cuBitcrack.exe

[7isce]

cuBitcrack.exe

ah, this program can run one GPU per window. so you need to open multiple window.
like for in window1 --device 0. In window --device 1 ...etc

If you have Nvidia card then you should go with https://github.com/kanhavishva/KeyHunt-Cuda

[italiandigger]

Its a easy thing to do in python, just use pip(python package manager) to install any module you want.
type in terminal:
"pip install base58" OR "pip3 install base58" it depend on your system.

And that's it. now you can just run addresses_to_hash160.py without any error.

I'VE DONE IT!!!!!!  
thanks again 7isce!!!!  

C:\>pip install base58
Collecting base58
  Downloading base58-2.1.1-py3-none-any.whl (5.6 kB)
Installing collected packages: base58
Successfully installed base58-2.1.1

C:\Keyhunt>python addresses_to_hash160.py puzzle64.txt puzzle64.bin
processed : 1 addresses
skipped   : 0 addresses

C:\Keyhunt>

It was not easy to understand what is the python "terminal".. it's the same terminal of windows!!!
It's enough to install only the latest version of Python for windows : https://www.python.org/downloads
No other downloads are necessary.

[italiandigger]

I found the operating keyspace range, it took me a while but I think it is 100% accurate, you can check it on your pc.
The program, as it is made, works fine only with a maximum range of 260000 keys (262500 does not already work fine) and it does not depend on the type of computer used, it is just a limit of the program.

The reason has been explained quite well from enmanueliglesias on : https://github.com/brichard19/BitCrack/issues/81
The cpu cannot elaborate the big amount of data sent from the gpu, so if the amount of data is bigger than 260000 keys it skips the result.

You can check for yourself, here are the two commands (it's a fast test):

clbitcrack -o out.txt --keyspace f7051f27b08d1800:f7051f27b09112d4 16jY7qLJnxb7CHZyqBP8qca9d51gAjyXQN
260000 keys = privkey found

clbitcrack -o out.txt --keyspace f7051f27b08d1000:f7051f27b09112d4 16jY7qLJnxb7CHZyqBP8qca9d51gAjyXQN
262500 keys = privkey not found

Now with the puzzle64.bin i can test keyhunt-cuda (cpu mode) with the same 260.000 keyspace used with clbitcrack, it's a very fast test, with a small keyspace it take less than 1 second :

C:\Keyhunt>KeyHunt-Cuda.exe -t 4 --gpui 0 -m address --coin BTC --range f7051f27b08d1800:f7051f27b09112d4 -i puzzle64.bin

KeyHunt-Cuda v1.08

COMP MODE    : COMPRESSED
COIN TYPE    : BITCOIN
SEARCH MODE  : Single Address
DEVICE       : CPU
CPU THREAD   : 4
SSE          : YES
RKEY         : 0 Mkeys
MAX FOUND    : 65536
BTC ADDRESS  :
OUTPUT FILE  : Found.txt


Bloom at 000001BE758F8EB0
  Version    : 2.1
  Entries    : 2
  Error      : 0.0000010000
  Bits       : 57
  Bits/Elem  : 28.755175
  Bytes      : 8 (0 MB)
  Hash funcs : 20

Start Time   : Sat Oct  1 22:44:29 2022
Global start : F7051F27B08D1800 (64 bit)
Global end   : F7051F27B09112D4 (64 bit)
Global range : 3FAD4 (18 bit)


[00:00:02] [CPU+GPU: 4.85 Mk/s] [GPU: 0.00 Mk/s] [C: 3825.571659 %] [R: 0] [T: 9,977,856 (24 bit)] [F: 0]

BYE

C:\Keyhunt>

Keyhunt-cuda DOESN'T find the privkey!!!!  

Let's try the same keyrange with the good old keyhunt (not CUDA) with the same range:

C:\Keyhunt>keyhunt -m rmd160 -f 64rmd160.txt -r f7051f27b08d1800:f7051f27b09112d4 -l compress -c btc -R -t 4 -q

• Version 0.2.211012 Chocolate ┬íBeta!, developed by AlbertoBSD(Win64 build by KV)
• Mode rmd160
• Search compress only
• Setting search for BTC adddress.
• Random mode
• Threads : 4
• Quiet thread output
• Opening file 64rmd160.txt
• Allocating memory for 1 elements: 0.00 MB
• Bloom filter for 1 elements.
• Loading data to the bloomfilter total: 0.00 MB
• Bloomfilter completed
• Sorting data ... done! 1 values were loaded and sorted

HIT!! PrivKey: f7051f27b09112d4
pubkey: 03100611c54dfef604163b8358f7b7fac13ce478e02cb224ae16d45526b25d9d4d

HIT!! PrivKey: f7051f27b09112d4
pubkey: 03100611c54dfef604163b8358f7b7fac13ce478e02cb224ae16d45526b25d9d4d

HIT!! PrivKey: f7051f27b09112d4
pubkey: 03100611c54dfef604163b8358f7b7fac13ce478e02cb224ae16d45526b25d9d4d

HIT!! PrivKey: f7051f27b09112d4
pubkey: 03100611c54dfef604163b8358f7b7fac13ce478e02cb224ae16d45526b25d9d4d
^C
C:\Keyhunt>

Keyhunt (not CUDA) finds the privkey 4 times!!!  (4 times because it's in random mode and it never finish until you stop it)

If you want to learn and do some testing then its OK to go with keyhunt(CPU) but if you want really to find any address then you should go the KeyHunt-Cuda(GPU)

Can you please try the same test, just curious to see if keyhunt-cuda (cpu mode only and gpu) works differently with you.

[7isce]

Did you convert the rmd160 or the address of 64?
Can you show us what was written inside puzzle64.txt?

[italiandigger]

Did you convert the rmd160 or the address of 64?
Can you show us what was written inside puzzle64.txt?

As you told me i wrote the address not rmd160: 16jY7qLJnxb7CHZyqBP8qca9d51gAjyXQN

What do you think if all the powers that left ETH mining could be of significant help in hacking these wallets?

The keyspace is too big : 1:fffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffff (63f = N), the privkey is like a drop in the sea.
For puzzle 66 i think 0,66 bitcoin is not enough to cover electric bill, for the richest wallets they can try in random mode dividing the keyspace but it's a very hard, long and expensive challenge, and if it happens for lucky it's only once in a century and not for several wallets.

In Windows its a pain.
But in Linux its just few command line(no programming)

1- sudo apt install build-essential git libgmp-dev python3-pip nano  -y
2- git clone https://github.com/kanhavishva/KeyHunt-Cuda
3- cd KeyHunt-Cuda/KeyHunt-Cuda/
4- nano Makefile (go to line "CUDA       = /usr/local/cuda-11.0" and change it to your cuda version for example "CUDA       = /usr/local/cuda-11.2"
5- make gpu=1 CCAP=21 all

And you ready to go ./KeyHunt....

I really know its look like too difficult but you should do it and take your time, week month its OK.
You can use https://vast.ai/console/ to rent cheap one for few hours and start to learn more about Linux and KeyHunt-Cuda (choose docker image "nvidia/cuda:11.2.0-devel-ubuntu18.04")

What are the commands on python only (windows)? too difficult?

[italiandigger]

Keyhunt in pub2rmd mode doesn't work too!!! keyrange 260000 keys, test with puzzle 64.

C:\Keyhunt>keyhunt -m pub2rmd -f 64rmd160.txt -t 4 -q -r f7051f27b08d1800:f7051f27b09112d4

• Version 0.2.211012 Chocolate ┬íBeta!, developed by AlbertoBSD(Win64 build by KV)
• Mode pub2rmd
• Threads : 4
• Quiet thread output
• Opening file 64rmd160.txt
• Allocating memory for 1 elements: 0.00 MB
• Bloom filter for 1 elements.
• Loading data to the bloomfilter total: 0.00 MB
• Bloomfilter completed
• Sorting data ... done! 1 values were loaded and sorted

^C] Total 94371840 keys in 720 seconds: 131072 keys/s
C:\Keyhunt>

It should find the pubkey in 2-3 seconds.. but it doesn't find anything and it continues non stop.

Albertobsd said that it's possible to test a range : https://github.com/albertobsd/keyhunt/issues/47
But it doesn't find the pubkey...

Until now, with all my tests only, keyhunt (address and rmd160 modes) works fine.
The test with 1.000.000.000 has been always 100% fulfilled.
Today i make a test with 100.000.000.000 keys of keyrange (it should take around 7 hours), i need to be sure that the software finds the privkey with "large" keyrange, if not it's 100% a waste of time and money (electricity).

[7isce]

What do you think if all the powers that left ETH mining could be of significant help in hacking these wallets?

Mining is just one type of hashing until you get to certain condition, like start with 17 zero so any hash that start 17 zero will be accepted.
Which mean there will be too many right answer.

Hacking/cracking/searching bitcoin address require more work and power.
start with create Secp256k1 private key and public key. then hash it with sha256 and then hash it again with RIPEMD160.
then you need to get exactly like address bits(100% the same)
We are here talking about address start with 1, others type of address require one more sha256 at the begin.

So as you can see the lost mining power will be at last cut a half to do cracking wallet.

[7isce]

What are the commands on python only (windows)? too difficult?

I found the problem in your range "f7051f27b08d1800:f7051f27b09112d4" the end range which will not cover is the 64 address so you need to increase it at least by one.

In windows there are no commands. You must work with Microsoft Visual Studio (not visual code) to run it.

[italiandigger]

What are the commands on python only (windows)? too difficult?

I found the problem in your range "f7051f27b08d1800:f7051f27b09112d4" the end range which will not cover is the 64 address so you need to increase it at least by one.

In windows there are no commands. You must work with Microsoft Visual Studio (not visual code) to run it.

I added some keys at the end of the keyspace so the privkey is inside, but KeyHunt-Cuda still not finds the privkey!!! 

C:\Keyhunt>KeyHunt-Cuda.exe -t 4 --gpui 0 -m address --coin BTC --range f7051f27b08d1800:f7051f27b0913800 -i puzzle64.bin

KeyHunt-Cuda v1.08

COMP MODE    : COMPRESSED
COIN TYPE    : BITCOIN
SEARCH MODE  : Single Address
DEVICE       : CPU
CPU THREAD   : 4
SSE          : YES
RKEY         : 0 Mkeys
MAX FOUND    : 65536
BTC ADDRESS  :
OUTPUT FILE  : Found.txt


Bloom at 00000208CD62A5B0
  Version    : 2.1
  Entries    : 2
  Error      : 0.0000010000
  Bits       : 57
  Bits/Elem  : 28.755175
  Bytes      : 8 (0 MB)
  Hash funcs : 20

Start Time   : Sun Oct  2 09:45:28 2022
Global start : F7051F27B08D1800 (64 bit)
Global end   : F7051F27B0913800 (64 bit)
Global range : 42000 (19 bit)


[00:00:02] [CPU+GPU: 6.09 Mk/s] [GPU: 0.00 Mk/s] [C: 4609.090909 %] [R: 0] [T: 12,460,032 (24 bit)] [F: 0]

BYE

C:\Keyhunt>

[italiandigger]

If anyone has a fast cpu (like intel i9 or ryzen9 or near) he could help with a test on a bigger keyspace, like 1.000.000.000.000 keys, just to verify that it founds the privkey.
On my old laptop it takes around 72 hours to calculate this amount of keys, of course keyhunt can find the key sooner, on average in half the time.

The command is :

keyhunt -m rmd160 -f 64rmd160.txt -r f7051ed5cdb09800:f7051fbea255a800 -l compress -c btc -R -t 4 -q

In the 64rmd160.txt just write : 3ee4133d991f52fdf6a25c9834e0745ac74248a4

If your cpu has more than 4 threads (you can check the threads number on intel website) change the -t value.

keyhunt.exe download here: https://github.com/secp8x32/keyhunt/tree/master/x64/Release)

[7isce]

Just change "-m address" to "-m addresses" 

[italiandigger]

Just change "-m address" to "-m addresses"  

THANKS!!! it works!!!!  

C:\Keyhunt>KeyHunt-Cuda.exe -t 4 --gpui 0 -m addresses --coin BTC --range f7051f27b08d1800:f7051f27b0913800 -i puzzle64.bin

KeyHunt-Cuda v1.08

COMP MODE    : COMPRESSED
COIN TYPE    : BITCOIN
SEARCH MODE  : Multi Address
DEVICE       : CPU
CPU THREAD   : 4
SSE          : YES
RKEY         : 0 Mkeys
MAX FOUND    : 65536
BTC HASH160s : puzzle64.bin
OUTPUT FILE  : Found.txt

Loaded       : 1 Bitcoin addresses

Bloom at 000001CEC6967D50
  Version    : 2.1
  Entries    : 2
  Error      : 0.0000010000
  Bits       : 57
  Bits/Elem  : 28.755175
  Bytes      : 8 (0 MB)
  Hash funcs : 20

Start Time   : Sun Oct  2 10:14:59 2022
Global start : F7051F27B08D1800 (64 bit)
Global end   : F7051F27B0913800 (64 bit)
Global range : 42000 (19 bit)



=================================================================================
PubAddress: 16jY7qLJnxb7CHZyqBP8qca9d51gAjyXQN
Priv (WIF): p2pkh:KwDiBf89QgGbjEhKnhXJuH7LrciVrZi3qZ6FxoaD5r1kYegmtbaT
Priv (HEX): F7051F27B09112D4
PubK (HEX): 03100611C54DFEF604163B8358F7B7FAC13CE478E02CB224AE16D45526B25D9D4D
=================================================================================

=================================================================================
PubAddress: 16jY7qLJnxb7CHZyqBP8qca9d51gAjyXQN
Priv (WIF): p2pkh:KwDiBf89QgGbjEhKnhXJuH7LrciVrZi3qZ6FxoaD5r1kYegmtbaT
Priv (HEX): F7051F27B09112D4
PubK (HEX): 03100611C54DFEF604163B8358F7B7FAC13CE478E02CB224AE16D45526B25D9D4D
=================================================================================

=================================================================================
PubAddress: 16jY7qLJnxb7CHZyqBP8qca9d51gAjyXQN
Priv (WIF): p2pkh:KwDiBf89QgGbjEhKnhXJuH7LrciVrZi3qZ6FxoaD5r1kYegmtbaT
Priv (HEX): F7051F27B09112D4
PubK (HEX): 03100611C54DFEF604163B8358F7B7FAC13CE478E02CB224AE16D45526B25D9D4D
=================================================================================

=================================================================================
PubAddress: 16jY7qLJnxb7CHZyqBP8qca9d51gAjyXQN
Priv (WIF): p2pkh:KwDiBf89QgGbjEhKnhXJuH7LrciVrZi3qZ6FxoaD5r1kYegmtbaT
Priv (HEX): F7051F27B09112D4
PubK (HEX): 03100611C54DFEF604163B8358F7B7FAC13CE478E02CB224AE16D45526B25D9D4D
=================================================================================
[00:00:02] [CPU+GPU: 5.50 Mk/s] [GPU: 0.00 Mk/s] [C: 4284.848485 %] [R: 0] [T: 11,583,488 (24 bit)] [F: 4]

BYE

C:\Keyhunt>

[italiandigger]

keyhunt-cuda.exe spent only 1 minute to find the privkey with 1.000.000.000 keys of keyspace: much faster than keyhunt.exe!!!

C:\Keyhunt>KeyHunt-Cuda.exe -t 4 --gpui 0 -m addresses --coin BTC --range f7051f279dcf0000:f7051f27d969c800 -i puzzle64.bin

KeyHunt-Cuda v1.08

COMP MODE    : COMPRESSED
COIN TYPE    : BITCOIN
SEARCH MODE  : Multi Address
DEVICE       : CPU
CPU THREAD   : 4
SSE          : YES
RKEY         : 0 Mkeys
MAX FOUND    : 65536
BTC HASH160s : puzzle64.bin
OUTPUT FILE  : Found.txt

Loaded       : 1 Bitcoin addresses

Bloom at 000001EE5F4B85E0
  Version    : 2.1
  Entries    : 2
  Error      : 0.0000010000
  Bits       : 57
  Bits/Elem  : 28.755175
  Bytes      : 8 (0 MB)
  Hash funcs : 20

Start Time   : Sun Oct  2 10:19:29 2022
Global start : F7051F279DCF0000 (64 bit)
Global end   : F7051F27D969C800 (64 bit)
Global range : 3B9AC800 (30 bit)


[00:01:00] [CPU+GPU: 3.97 Mk/s] [GPU: 0.00 Mk/s] [C: 25.309402 %] [R: 0] [T: 253,093,888 (28 bit)] [F: 0]
=================================================================================
PubAddress: 16jY7qLJnxb7CHZyqBP8qca9d51gAjyXQN
Priv (WIF): p2pkh:KwDiBf89QgGbjEhKnhXJuH7LrciVrZi3qZ6FxoaD5r1kYegmtbaT
Priv (HEX): F7051F27B09112D4
PubK (HEX): 03100611C54DFEF604163B8358F7B7FAC13CE478E02CB224AE16D45526B25D9D4D
=================================================================================
[00:01:02] [CPU+GPU: 3.93 Mk/s] [GPU: 0.00 Mk/s] [C: 26.097063 %] [R: 0] [T: 260,970,496 (28 bit)] [F: 1]

BYE

C:\Keyhunt>

[italiandigger]

7isce, can you get keyhunt-cuda to work randomly like keyhunt?

I don't understand well the option:

-r, --rkey Rkey                          : Random key interval in MegaKeys, default is disabled

[KudilCumil]

hallo,..
how to change addresses.txt to puzzle64.bin?

C:\Users\xxxx\Downloads\KeyHunt-Cuda\x64\Release>KeyHunt-Cuda.exe -g --gpui 0,1,2,3,4,5,6,7 -m addresses --coin BTC --range xxxxxxxxx:xxxxxxxx -i puzzle64.bin

KeyHunt-Cuda v1.08

COMP MODE    : COMPRESSED
COIN TYPE    : BITCOIN
SEARCH MODE  : Multi Address
DEVICE       : GPU
CPU THREAD   : 0
GPU IDS      : 0, 1, 2, 3, 4, 5, 6, 7
GPU GRIDSIZE : -1x128, -1x128, -1x128, -1x128, -1x128, -1x128, -1x128, -1x128 (Auto grid size)
SSE          : YES
RKEY         : 0 Mkeys
MAX FOUND    : 65536
BTC HASH160s : puzzle64.bin
OUTPUT FILE  : Found.txt
puzzle64.bin can not open

[7isce]

7isce, can you get keyhunt-cuda to work randomly like keyhunt?

I don't understand well the option:

-r, --rkey Rkey                          : Random key interval in MegaKeys, default is disabled

-r 1 mean every 1 Million keys(done searching 1 Million keys) the program will regenerate new random start point.
-r 10 mean every 10 Millions keys...
...etc