BitCrack - A tool for brute-forcing private keys

[italiandigger]

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

It's enough to install only the latest version of Python for windows : https://www.python.org/downloads

After install run the Python IDLE program.

Copy the 32 code lines from here : https://github.com/secp8x32/KeyHunt-Cuda/blob/main/addresses_to_hash160.py

Paste the copied lines in the Python IDLE and Save as addresses_to_hash160.py in the keyhunt-cuda.exe folder.

Run the installed Python program (Pyton 3.10 64bit).

Run the windows terminal (where you run keyhunt-cuda.exe), and write:

C:\>pip install base58

You get this reply:

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

Go in your keyhunt-cuda folder and write:

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

Done!  

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

Thanks!!!

[1714798043]

1714798043

[1714798043]

1714798043

[1714798043]

1714798043

[KudilCumil]

It's enough to install only the latest version of Python for windows : https://www.python.org/downloads

After install run the Python IDLE program.

Copy the 32 code lines from here : https://github.com/secp8x32/KeyHunt-Cuda/blob/main/addresses_to_hash160.py

Paste the copied lines in the Python IDLE and Save as addresses_to_hash160.py in the keyhunt-cuda.exe folder.

Run the installed Python program (Pyton 3.10 64bit).

Run the windows terminal (where you run keyhunt-cuda.exe), and write:

C:\>pip install base58

You get this reply:

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

Go in your keyhunt-cuda folder and write:

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

Done!  

thanks 

[italiandigger]

-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

Test 1: random with 100 Millions keys : after 41 minutes i stopped it, no privkey found!!! The same with -r 1 and -r 10!
The keyunt.exe (not CUDA) -R random option works much better and it gives ALWAYS a result in 0-10 minutes.

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

KeyHunt-Cuda v1.08

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

Loaded       : 1 Bitcoin addresses

Bloom at 00000201CFEF8EB0
  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 13:32:14 2022
Base Key     : Randomly changes on every 100 Mkeys
Global start : F7051F279DCF0000 (64 bit)
Global end   : F7051F27D969C800 (64 bit)
Global range : 3B9AC800 (30 bit)


[00:41:21] [CPU+GPU: 2.68 Mk/s] [GPU: 0.00 Mk/s] [C: 0.000000 %] [R: 68] [T: 7,057,741,824 (33 bit)] [F: 0]

BYE

Test 2: without random it finish the keyspace in less than 2 minutes (like told in a previous post)

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 0000029AB4EF7200
  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 14:14:03 2022
Global start : F7051F279DCF0000 (64 bit)
Global end   : F7051F27D969C800 (64 bit)
Global range : 3B9AC800 (30 bit)


[00:01:23] [CPU+GPU: 3.02 Mk/s] [GPU: 0.00 Mk/s] [C: 25.447232 %] [R: 0] [T: 254,472,192 (28 bit)] [F: 0]
=================================================================================
PubAddress: 16jY7qLJnxb7CHZyqBP8qca9d51gAjyXQN
Priv (WIF): p2pkh:KwDiBf89QgGbjEhKnhXJuH7LrciVrZi3qZ6FxoaD5r1kYegmtbaT
Priv (HEX): F7051F27B09112D4
PubK (HEX): 03100611C54DFEF604163B8358F7B7FAC13CE478E02CB224AE16D45526B25D9D4D
=================================================================================
[00:01:25] [CPU+GPU: 3.02 Mk/s] [GPU: 0.00 Mk/s] [C: 26.080065 %] [R: 0] [T: 260,800,512 (28 bit)] [F: 1]

BYE

C:\Keyhunt>

[7isce]

Hi italiandigger,
You should watch this video to understand how random search work
https://www.youtube.com/watch?v=7WWnWSPymdc

[italiandigger]

Hi italiandigger,
You should watch this video to understand how random search work
https://www.youtube.com/watch?v=7WWnWSPymdc

Hi 7isce, i've looked the video until the end with interest.
From my last two tests (and according with the old tests with keyhunt) i can say that the random algorithm is different in keyhunt.exe and keyhunt-cuda.exe!
The random of keyhunt-cuda, using the language of the YT video, repeats MUCH MORE than keyhunt the possible candidate solution and it's evident from the number of iterations, and so it takes much more time to complete the process.
Keyhunt-cuda goes far below the 63% of probaility to get the reach of the solution before the end of keyspace.
Keyhunt probability is around the 63% and more until 99%, you can see it from the tests of 1.000.000.000 keys of keyspace done in my previous post, all before the 10 minutes (usually around the 1.000.000.000 keys examined).
Do you agree?

In conclusion from my tests:
Keyunt.exe works fine in the random mode.
Keyhunt-cuda.exe (cpu) works fine and faster only in secuential mode.

[7isce]

Hi 7isce, i've looked the video until the end with interest.
From my last two tests (and according with the old tests with keyhunt) i can say that the random algorithm is different in keyhunt.exe and keyhunt-cuda.exe!
The random of keyhunt-cuda, using the language of the YT video, repeats MUCH MORE than keyhunt the possible candidate solution and it's evident from the number of iterations, and so it takes much more time to complete the process.
Keyhunt-cuda goes far below the 63% of probaility to get the reach of the solution before the end of keyspace.
Keyhunt probability is around the 63% and more until 99%, you can see it from the tests of 1.000.000.000 keys of keyspace done in my previous post, all before the 10 minutes (usually around the 1.000.000.000 keys examined).
Do you agree?

In conclusion from my tests:
Keyunt.exe works fine in the random mode.
Keyhunt-cuda.exe (cpu) works fine and faster only in secuential mode.

I think this unfair comparison.
Keyhunt is build for CPU only and it very optimize for that purpose.
Keyhunt-cuda is fork from VanitySearch by JeanLucPons. Its fully focus on GPU and the just keep the CPU because its work by inherited it So they decided to keep it.
You need to test Keyhunt-cuda on GPU to have a fair comparison.

[italiandigger]

The whole reached end of keyspace problem is in Bitcrack  0.31 OpenCL version only. There is a way to fix this in the issues section.

Just tried clbitcrack 3.0 (not the 3.1) and it works fine over the 260.000 keys of keyspace!  
https://github.com/brichard19/BitCrack/releases/tag/0.30

C:\>cd bitcrack

C:\BitCrack>clbitcrack -o out.txt --keyspace f7051f27b08d1000:f7051f27b09112d4 16jY7qLJnxb7CHZyqBP8qca9d51gAjyXQN
[2022-10-02.16:08:18] [Info] Compression: compressed
[2022-10-02.16:08:18] [Info] Starting at: 000000000000000000000000000000000000000000000000F7051F27B08D1000
[2022-10-02.16:08:18] [Info] Ending at:   000000000000000000000000000000000000000000000000F7051F27B09112D4
[2022-10-02.16:08:18] [Info] Counting by: 0000000000000000000000000000000000000000000000000000000000000001
[2022-10-02.16:08:18] [Info] Compiling OpenCL kernels...
[2022-10-02.16:10:02] [Info] Initializing Intel(R) UHD Graphics 605
[2022-10-02.16:10:02] [Info] Generating 262,144 starting points (10.0MB)
[2022-10-02.16:10:08] [Info] 10.0%
[2022-10-02.16:10:15] [Info] 20.0%
[2022-10-02.16:10:20] [Info] 30.0%
[2022-10-02.16:10:26] [Info] 40.0%
[2022-10-02.16:10:32] [Info] 50.0%
[2022-10-02.16:10:38] [Info] 60.0%
[2022-10-02.16:10:44] [Info] 70.0%
[2022-10-02.16:10:49] [Info] 80.0%
[2022-10-02.16:10:55] [Info] 90.0%
[2022-10-02.16:11:01] [Info] 100.0%
[2022-10-02.16:11:01] [Info] Done
[2022-10-02.16:11:01] [Info] Found key for address '16jY7qLJnxb7CHZyqBP8qca9d51gAjyXQN'. Written to 'out.txt'
[2022-10-02.16:11:01] [Info] No targets remaining
[2022-10-02.16:11:01] [Info] Reached end of keyspace

C:\BitCrack>

[italiandigger]

Good news for Keyhunt-cuda (cpu only) too, the 100.000.000.000 keyspace test has been fullfilled fine in less than 6 hours.

C:\Keyhunt>KeyHunt-Cuda.exe -t 4 --gpui 0 -m addresses --coin BTC --range f7051f1d195d2800:f7051f3461d41000 -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 000001DF33F13E20
  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:47:02 2022
Global start : F7051F1D195D2800 (64 bit)
Global end   : F7051F3461D41000 (64 bit)
Global range : 174876E800 (37 bit)


[05:43:55] [CPU+GPU: 3.99 Mk/s] [GPU: 0.00 Mk/s] [C: 81.867672 %] [R: 0] [T: 81,867,671,552 (37 bit)] [F: 0]
=================================================================================
PubAddress: 16jY7qLJnxb7CHZyqBP8qca9d51gAjyXQN
Priv (WIF): p2pkh:KwDiBf89QgGbjEhKnhXJuH7LrciVrZi3qZ6FxoaD5r1kYegmtbaT
Priv (HEX): F7051F27B09112D4
PubK (HEX): 03100611C54DFEF604163B8358F7B7FAC13CE478E02CB224AE16D45526B25D9D4D
=================================================================================
[05:43:57] [CPU+GPU: 3.99 Mk/s] [GPU: 0.00 Mk/s] [C: 81.875855 %] [R: 0] [T: 81,875,855,360 (37 bit)] [F: 1]

BYE

C:\Keyhunt>

[italiandigger]

In conclusion Clbitcrack (0.30 version) complete the 100 billions keyspace test 45 minutes sooner than Keyhunt, because clbitcrack uses gpu+cpu and keyhunt the cpu only.

5.37Mkey/s against 3.99MKey/s on my laptop.  

A pity that clbitcrack doesn't work random.

Now i wait to test the cubitcrack and keyhunt-cuda (cpu+gpu) to see if it's faster than clbitcrack.
Let's see if i can solve my CUDA laptop problems.  

With clbitcrack (0.30) and my old laptop all the puzzle 64 keyspace can be completed in 210579 years  
Random becomes an obligatory choice, i presume.

[7isce]

In conclusion Clbitcrack (0.30 version) complete the 100 billions keyspace test 45 minutes sooner than Keyhunt, because clbitcrack use gpu+cpu and keyhunt the cpu only. 3.99MKey/s against 5.37Mkey/s on my laptop.  

Now i wait to test the cubitcrack and keyhunt-cuda (cpu+gpu) to see if it's faster than clbitcrack.
Let's see if i can solve my CUDA laptop problems.  

For keyhunt-cuda you must run either GPU OR CPU(both is not supported)
"CPU and GPU can not be used together, because the program divides the whole input range into equal parts for all the threads, so use either CPU or GPU so that the whole range can increment by all the threads with consistency."

If you want to run both then use https://github.com/JeanLucPons/VanitySearch/

[italiandigger]

In conclusion Clbitcrack (0.30 version) complete the 100 billions keyspace test 45 minutes sooner than Keyhunt, because clbitcrack use gpu+cpu and keyhunt the cpu only. 3.99MKey/s against 5.37Mkey/s on my laptop.  

Now i wait to test the cubitcrack and keyhunt-cuda (cpu+gpu) to see if it's faster than clbitcrack.
Let's see if i can solve my CUDA laptop problems.  

For keyhunt-cuda you must run either GPU OR CPU(both is not supported)
"CPU and GPU can not be used together, because the program divides the whole input range into equal parts for all the threads, so use either CPU or GPU so that the whole range can increment by all the threads with consistency."

If you want to run both then use https://github.com/JeanLucPons/VanitySearch/

Clbitcrack detect my gpu, does it mean that it use gpu and cpu together? or gpu only? or cpu only? you see from the same test, it's faster than keyhunt.

About VanitySearch i don't understand well what does it mean:

As you can see, even with a competitive hardware, it is very unlikely that you find a collision. Birthday paradox doesn't apply in this context, it works only if we know already the public key (not the address, the hash of the public key) we want to find. This program doesn't look for collisions between public keys. It searchs only for collisions with addresses with a certain prefix.

We don't know the puzzle 66 pubkey.. we know only the address.

Collisions with addresses with a certain prefix??? 

[7isce]

Clbitcrack detect my gpu, does it mean that it use gpu and cpu together? or gpu only? or cpu only? you see from the same test, it's faster than keyhunt.

About VanitySearch i don't understand well what does it mean:

As you can see, even with a competitive hardware, it is very unlikely that you find a collision. Birthday paradox doesn't apply in this context, it works only if we know already the public key (not the address, the hash of the public key) we want to find. This program doesn't look for collisions between public keys. It searchs only for collisions with addresses with a certain prefix.

We don't know the puzzle 66 pubkey.. we know only the address.

Collisions with addresses with a certain prefix??? 

Clbitcrack is support both CPU and GPU.
From what I see in your result that you have the Intel GPU not Nvidia GPU so you can't run KeyHunt-Cuda because Cuda is for Nvidia GPU only.

prefix is mean start with. you can use it for search key start with puzzle address "1LeBZP5QC"
Or you can search for special address for yourself like address start with 1italiandigger

[KudilCumil]

does keyhunt-cuda has restore point command?

[7isce]

does keyhunt-cuda has restore point command?

I don't get it, Can you explain more?

[KudilCumil]

I don't get it, Can you explain more?

i mean, is it any command that can be use if something happen, lets say like electric out, so it dont have to start all over again.
just like cubitcrack has it (--continue FILE)

[7isce]

i mean, is it any command that can be use if something happen, lets say like electric out, so it dont have to start all over again.
just like cubitcrack has it (--continue FILE)

unfortunate there is no arrangement for that job.
But you can redirect all output to file like ./Keyhunt .... > save/file1.txt
So you can keep track of progress status and if any thing happen then you just edit the start range+last progress status

[italiandigger]

From what I see in your result that you have the Intel GPU not Nvidia GPU so you can't run KeyHunt-Cuda because Cuda is for Nvidia GPU only.

I did the fast 260.000 keyspace test with the "main" desktop computer that i use for internet  
In the old laptop that i use for quite all the tests there is a Nvidia Geforce 820M with 2Gb.
There is Nvidia Cuda 8.0.0 driver installed (NVCUDA.dll)

C:\BitCrack>clbitcrack -o out.txt --keyspace f7051f27b08d1000:f7051f27b09112d4 16jY7qLJnxb7CHZyqBP8qca9d51gAjyXQN
[2022-10-03.08:32:22] [Info] Compression: compressed
[2022-10-03.08:32:22] [Info] Starting at: 000000000000000000000000000000000000000000000000F7051F27B08D1000
[2022-10-03.08:32:22] [Info] Ending at:   000000000000000000000000000000000000000000000000F7051F27B09112D4
[2022-10-03.08:32:22] [Info] Counting by: 0000000000000000000000000000000000000000000000000000000000000001
[2022-10-03.08:32:22] [Info] Compiling OpenCL kernels...
[2022-10-03.08:32:23] [Info] Initializing GeForce 820M
[2022-10-03.08:32:23] [Info] Generating 262,144 starting points (10.0MB)
[2022-10-03.08:32:24] [Info] 10.0%
[2022-10-03.08:32:25] [Info] 20.0%
[2022-10-03.08:32:26] [Info] 30.0%
[2022-10-03.08:32:26] [Info] 40.0%
[2022-10-03.08:32:27] [Info] 50.0%
[2022-10-03.08:32:27] [Info] 60.0%
[2022-10-03.08:32:28] [Info] 70.0%
[2022-10-03.08:32:29] [Info] 80.0%
[2022-10-03.08:32:29] [Info] 90.0%
[2022-10-03.08:32:30] [Info] 100.0%
[2022-10-03.08:32:30] [Info] Done
[2022-10-03.08:32:30] [Info] Found key for address '16jY7qLJnxb7CHZyqBP8qca9d51gAjyXQN'. Written to 'out.txt'
[2022-10-03.08:32:30] [Info] No targets remaining
[2022-10-03.08:32:30] [Info] Reached end of keyspace

C:\BitCrack>

[italiandigger]

In the old laptop that i use for quite all the tests there is a Nvidia Geforce 820M with 2Gb.
There is Nvidia Cuda 8.0.0 driver installed (NVCUDA.dll)

https://askubuntu.com/questions/999509/which-cuda-cudnn-nvidia-versions-to-install-for-deep-learning

The link says:
Your Geforce 820M GPU has a CUDA compute capability of 2.1 (see Intel geforce gpu list This capability is too low for CUDA 9.0+, but does support CUDA 8.0. Try installing that CUDA version.

https://developer.nvidia.com/cuda-gpus#compute

 

[KudilCumil]

after running awhile this problem occur :
"cudaSafeCall() failed at D:/PROGRAMMING/VisualStudioProjects/KeyHunt-Cuda-GIT-2017/KeyHunt-Cuda/KeyHunt-Cuda/GPU/GPUEngine.cu:686 : an illegal memory access was encountered'.
then stop,.. why is this? is it because lack of virtual memory?

[7isce]

after running awhile this problem occur :
"cudaSafeCall() failed at D:/PROGRAMMING/VisualStudioProjects/KeyHunt-Cuda-GIT-2017/KeyHunt-Cuda/KeyHunt-Cuda/GPU/GPUEngine.cu:686 : an illegal memory access was encountered'.
then stop,.. why is this? is it because lack of virtual memory?

Did you change CCAP value to match your GPU CCAP?