BitCrack - A tool for brute-forcing private keys

[dlystyr]

Hi All,

I have a AMD 6900 XT and am using https://github.com/Uzlopak/BitCrackOpenCL/

I am wondering if anyone could help with the settings, I cant seem to get them right at all.

I tried the current settings above for Nvidia but being roughly same power I assumed same settings might be slightly compatible.

-b 82 -t 256 -p 2096

Appreciate any help.

[1714661889]

1714661889

[1714661889]

1714661889

[1714661889]

1714661889

[1714661889]

1714661889

[1714661889]

1714661889

[1714661889]

1714661889

[brainless]

Hi All,

I have a AMD 6900 XT and am using https://github.com/Uzlopak/BitCrackOpenCL/

I am wondering if anyone could help with the settings, I cant seem to get them right at all.

I tried the current settings above for Nvidia but being roughly same power I assumed same settings might be slightly compatible.

-b 82 -t 256 -p 2096

Appreciate any help.

-b 80 -t 512 -p 2048
-b 80 -t 256 -p 2048

if any one work for you, then let me know for quide you more for optimal speed setting

[dlystyr]

Hi All,

I have a AMD 6900 XT and am using https://github.com/Uzlopak/BitCrackOpenCL/

I am wondering if anyone could help with the settings, I cant seem to get them right at all.

I tried the current settings above for Nvidia but being roughly same power I assumed same settings might be slightly compatible.

-b 82 -t 256 -p 2096

Appreciate any help.

-b 80 -t 512 -p 2048
-b 80 -t 256 -p 2048

if any one work for you, then let me know for quide you more for optimal speed setting

-b 80 -t 256 -p 2048 works well, I found 80 compute units from the AMD site (RTFM! right.) I tried any threads higher and the GPU hung. I will have a play and get back to you, but thank you very much.

[brainless]

Hi All,

I have a AMD 6900 XT and am using https://github.com/Uzlopak/BitCrackOpenCL/

I am wondering if anyone could help with the settings, I cant seem to get them right at all.

I tried the current settings above for Nvidia but being roughly same power I assumed same settings might be slightly compatible.

-b 82 -t 256 -p 2096

Appreciate any help.

-b 80 -t 512 -p 2048
-b 80 -t 256 -p 2048

if any one work for you, then let me know for quide you more for optimal speed setting

-b 80 -t 256 -p 2048 works well, I found 80 compute units from the AMD site (RTFM! right.) I tried any threads higher and the GPU hung. I will have a play and get back to you, but thank you very much.

you can check more settings by adding 32 into p value
like 2048
2080
2112
2144
etc

same in other -b 80 -t 512 -p 2048
reduce 32 from p value
you can adjust as per your input file load, if you have single address and few 100's or 1000's, there value , you can adjust for maximum usage of gpu
if you load big addresses file, then same adjust p value with add/sub 32 into 2048 value

[italiandigger]

Hi to everyone,
i have done several tests with puzzle 64 to find the private key on different computers with clbitcrack.exe
(downloaded from : https://github.com/brichard19/BitCrack/releases)

If i give a very short range (2-3 keys) it finds the private key without problem, with bigger ranges (37181645903300 keys or more) it doesn't.
With a friend we have done the same test on 2 different notebooks, one with a Geforce 820M 1Gb and one with a Geforce 850M 4Gb, with the same results.

Has clbitcrack.exe a bug or what?

You can test it too with this command:

clbitcrack -o out.txt --keyspace f704fd56a9c53800:f7051f27b09112d4 16jY7qLJnxb7CHZyqBP8qca9d51gAjyXQN

it reaches the end of keyspace without results (it takes less than 13 minutes on the Geforce 820M).

and if you try:

clbitcrack -o out.txt --keyspace f7051f27b09112d2:f7051f27b09112d4 16jY7qLJnxb7CHZyqBP8qca9d51gAjyXQN

it reaches the end of keyspace with the found key.

I dont' know what to think...

I've just done the test with a Intel UHD Graphics 605, same results, so it doesn't seem a matter of graphics card..

[COBRAS]

Hi to everyone,
i have done several tests with puzzle 64 to find the private key on different computers with clbitcrack.exe
(downloaded from : https://github.com/brichard19/BitCrack/releases)

If i give a very short range (2-3 keys) it finds the private key without problem, with bigger ranges (37181645903300 keys or more) it doesn't.
With a friend we have done the same test on 2 different notebooks, one with a Geforce 820M 1Gb and one with a Geforce 850M 4Gb, with the same results.

Has clbitcrack.exe a bug or what?

You can test it too with this command:

clbitcrack -o out.txt --keyspace f704fd56a9c53800:f7051f27b09112d4 16jY7qLJnxb7CHZyqBP8qca9d51gAjyXQN

it reaches the end of keyspace without results (it takes less than 13 minutes on the Geforce 820M).

and if you try:

clbitcrack -o out.txt --keyspace f7051f27b09112d2:f7051f27b09112d4 16jY7qLJnxb7CHZyqBP8qca9d51gAjyXQN

it reaches the end of keyspace with the found key.

I dont' know what to think...

I've just done the test with a Intel UHD Graphics 605, same results, so it doesn't seem a matter of graphics card..

Shit, so many years for waste time

[brainless]

Hi to everyone,
i have done several tests with puzzle 64 to find the private key on different computers with clbitcrack.exe
(downloaded from : https://github.com/brichard19/BitCrack/releases)

If i give a very short range (2-3 keys) it finds the private key without problem, with bigger ranges (37181645903300 keys or more) it doesn't.
With a friend we have done the same test on 2 different notebooks, one with a Geforce 820M 1Gb and one with a Geforce 850M 4Gb, with the same results.

Has clbitcrack.exe a bug or what?

You can test it too with this command:

clbitcrack -o out.txt --keyspace f704fd56a9c53800:f7051f27b09112d4 16jY7qLJnxb7CHZyqBP8qca9d51gAjyXQN

it reaches the end of keyspace without results (it takes less than 13 minutes on the Geforce 820M).

and if you try:

clbitcrack -o out.txt --keyspace f7051f27b09112d2:f7051f27b09112d4 16jY7qLJnxb7CHZyqBP8qca9d51gAjyXQN

it reaches the end of keyspace with the found key.

I dont' know what to think...

I've just done the test with a Intel UHD Graphics 605, same results, so it doesn't seem a matter of graphics card..

--keyspace f704fd56a9c53800:f7051f27b09112d4
you want to say you check 37,181,645,904,596 keys in 13 min ?

[brainless]

Hi to everyone,
i have done several tests with puzzle 64 to find the private key on different computers with clbitcrack.exe
(downloaded from : https://github.com/brichard19/BitCrack/releases)

If i give a very short range (2-3 keys) it finds the private key without problem, with bigger ranges (37181645903300 keys or more) it doesn't.
With a friend we have done the same test on 2 different notebooks, one with a Geforce 820M 1Gb and one with a Geforce 850M 4Gb, with the same results.

Has clbitcrack.exe a bug or what?

You can test it too with this command:

clbitcrack -o out.txt --keyspace f704fd56a9c53800:f7051f27b09112d4 16jY7qLJnxb7CHZyqBP8qca9d51gAjyXQN

it reaches the end of keyspace without results (it takes less than 13 minutes on the Geforce 820M).

and if you try:

clbitcrack -o out.txt --keyspace f7051f27b09112d2:f7051f27b09112d4 16jY7qLJnxb7CHZyqBP8qca9d51gAjyXQN

it reaches the end of keyspace with the found key.

I dont' know what to think...

I've just done the test with a Intel UHD Graphics 605, same results, so it doesn't seem a matter of graphics card..

if i take highest speed
[2022-09-25.21:11:56] [Info] Initializing NVIDIA GeForce RTX 3070 Ti
[2022-09-25.21:11:56] [Info] Generating 50,331,648 starting points (1920.0MB)
[2022-09-25.21:12:03] [Info] 10.0%
[2022-09-25.21:12:03] [Info] 20.0%
[2022-09-25.21:12:04] [Info] 30.0%
[2022-09-25.21:12:04] [Info] 40.0%
[2022-09-25.21:12:04] [Info] 50.0%
[2022-09-25.21:12:04] [Info] 60.0%
[2022-09-25.21:12:04] [Info] 70.0%
[2022-09-25.21:12:05] [Info] 80.0%
[2022-09-25.21:12:05] [Info] 90.0%
[2022-09-25.21:12:05] [Info] 100.0%
[2022-09-25.21:12:05] [Info] Done
NVIDIA GeForce R 5678 / 8192MB | 1 target 1337.45 MKey/s (39,510,343,680 total) [00:00:27]

80g key/per m , 800 gkeys/ 10m
37181 Gkeys how possible in 13 min

[italiandigger]

--keyspace f704fd56a9c53800:f7051f27b09112d4
you want to say you check 37,181,645,904,596 keys in 13 min ?

Yes, it can be faster with another video card.

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 = key found

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

[italiandigger]

if i take highest speed
[2022-09-25.21:11:56] [Info] Initializing NVIDIA GeForce RTX 3070 Ti
[2022-09-25.21:11:56] [Info] Generating 50,331,648 starting points (1920.0MB)
[2022-09-25.21:12:03] [Info] 10.0%
[2022-09-25.21:12:03] [Info] 20.0%
[2022-09-25.21:12:04] [Info] 30.0%
[2022-09-25.21:12:04] [Info] 40.0%
[2022-09-25.21:12:04] [Info] 50.0%
[2022-09-25.21:12:04] [Info] 60.0%
[2022-09-25.21:12:04] [Info] 70.0%
[2022-09-25.21:12:05] [Info] 80.0%
[2022-09-25.21:12:05] [Info] 90.0%
[2022-09-25.21:12:05] [Info] 100.0%
[2022-09-25.21:12:05] [Info] Done
NVIDIA GeForce R 5678 / 8192MB | 1 target 1337.45 MKey/s (39,510,343,680 total) [00:00:27]

80g key/per m , 800 gkeys/ 10m
37181 Gkeys how possible in 13 min

I did it in 2 minutes with my little Geforce 820M:

C:\BitCrack>clbitcrack -o out.txt --keyspace f704fd56a9c53800:f7051f27b09112d4 16jY7qLJnxb7CHZyqBP8qca9d51gAjyXQN -b 96 -t 256 -p 256
[2022-09-26.17:45:32] [Info] Compression: compressed
[2022-09-26.17:45:32] [Info] Starting at: 000000000000000000000000000000000000000000000000F704FD56A9C53800
[2022-09-26.17:45:32] [Info] Ending at:   000000000000000000000000000000000000000000000000F7051F27B09112D4
[2022-09-26.17:45:32] [Info] Counting by: 0000000000000000000000000000000000000000000000000000000000000001
[2022-09-26.17:45:32] [Info] Compiling OpenCL kernels...
[2022-09-26.17:45:32] [Info] Initializing GeForce 820M
[2022-09-26.17:45:34] [Info] Generating 6,291,456 starting points (240.0MB)
[2022-09-26.17:45:42] [Info] 10.0%
[2022-09-26.17:45:49] [Info] 20.0%
[2022-09-26.17:45:54] [Info] 30.0%
[2022-09-26.17:45:56] [Info] 40.0%
[2022-09-26.17:45:58] [Info] 50.0%
[2022-09-26.17:46:00] [Info] 60.0%
[2022-09-26.17:46:03] [Info] 70.0%
[2022-09-26.17:46:05] [Info] 80.0%
[2022-09-26.17:46:07] [Info] 90.0%
[2022-09-26.17:46:09] [Info] 100.0%
[2022-09-26.17:46:09] [Info] Done
GeForce 820M     576 / 1024MB | 1 target 11.03 MKey/s (1,509,949,440 total) [00:02:14][2022-09-26.17:48:27] [Info] Reached end of keyspace

C:\BitCrack>

It's not a matter of how much fast is my gpu.
The problem is that clbitcrack doesn't find the key!!! because the keyrange is bigger than 260000 keys!

The key of puzzle 64 is f7051f27b09112d4

f7051f27b09112d4 = 17799667357578236000
f704fd56a9c53800 = 17799630175932332000

17799667357578236000-17799630175932332000=37181645904000 keys

[italiandigger]

Shit, so many years for waste time

It's the right reply.. unfortunately

[brainless]

Shit, so many years for waste time

It's the right reply.. unfortunately

1 target 11.03 MKey/s (1,509,949,440 total)
17799667357578236000-17799630175932332000=37181645904000 keys

required to check 37181645904000
and finsih at 1,509,949,440

defiantly their is bug in your tool
mostly peoples using cuda, thats work fine
maybe author long time ago post about cl version problem check their issues

[italiandigger]

required to check 37181645904000
and finsih at 1,509,949,440

defiantly their is bug in your tool
mostly peoples using cuda, thats work fine
maybe author long time ago post about cl version problem check their issues

I think that the the GPU calculate all the 37181645904000 keys because it reaches the end of keyspace.
The 1,509,949,440 seems a wrong compute of the program.
The main thing is to get the key.
Let me see that you find the key!

Try to post the complete cubitcrack.exe result from the beginning to the end (not cutted), so we can verify easily that it works fine.
You know the keyspace: --keyspace f704fd56a9c53800:f7051f27b09112d4 16jY7qLJnxb7CHZyqBP8qca9d51gAjyXQN

[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.

The main thing is to get the key.
Let me see that you find the key!

Try to post the complete cubitcrack.exe result from the beginning to the end (not cutted), so we can verify easily that it works fine.
You know the keyspace: --keyspace f704fd56a9c53800:f7051f27b09112d4 16jY7qLJnxb7CHZyqBP8qca9d51gAjyXQN

[italiandigger]

You are probably just a starter and hardly know and see what you are doing. Look at the range you are to scan. Will take a lot of time.

I'm very glad that you are more expert (even if i don't see any demonstration..  )

Try this clBitcrack -o out.txt --keyspace f7051f27a09112d4:f7051f37b09112d4 16jY7qLJnxb7CHZyqBP8qca9d51gAjyXQN

C:\BitCrack>clBitcrack -o out.txt --keyspace f7051f27a09112d4:f7051f37b09112d4 16jY7qLJnxb7CHZyqBP8qca9d51gAjyXQN -b 96 -t 256 -p 256
[2022-09-26.21:14:51] [Info] Compression: compressed
[2022-09-26.21:14:51] [Info] Starting at: 000000000000000000000000000000000000000000000000F7051F27A09112D4
[2022-09-26.21:14:51] [Info] Ending at:   000000000000000000000000000000000000000000000000F7051F37B09112D4
[2022-09-26.21:14:51] [Info] Counting by: 0000000000000000000000000000000000000000000000000000000000000001
[2022-09-26.21:14:51] [Info] Compiling OpenCL kernels...
[2022-09-26.21:14:51] [Info] Initializing GeForce 820M
[2022-09-26.21:14:53] [Info] Generating 6,291,456 starting points (240.0MB)
[2022-09-26.21:15:02] [Info] 10.0%
[2022-09-26.21:15:08] [Info] 20.0%
[2022-09-26.21:15:13] [Info] 30.0%
[2022-09-26.21:15:15] [Info] 40.0%
[2022-09-26.21:15:17] [Info] 50.0%
[2022-09-26.21:15:20] [Info] 60.0%
[2022-09-26.21:15:22] [Info] 70.0%
[2022-09-26.21:15:24] [Info] 80.0%
[2022-09-26.21:15:26] [Info] 90.0%
[2022-09-26.21:15:29] [Info] 100.0%
[2022-09-26.21:15:29] [Info] Done
[2022-09-26.21:15:29] [Info] Reached end of keyspace

C:\BitCrack>

Key not found because the keyrange is larger than 260000 keys!!!
As i told before clbitcrack doesn't work fine with more than 260000 keys, it simply skips to detect the key.
You suggested a keyrange of 268436000 keys..

f7051f27b09112d4 = 17799667357578236000
f7051f27a09112d4 = 17799667357309800000

17799667357578236000 - 17799667357309800000 = 268436000 keys

Why don't you post your result (without cuts) with cubitcrack too?

I will be very glad to see your demonstration with more keys and see the key found at the end of the software results!

[italiandigger]

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 = key found

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

Here you can see that with 260000 keys clbitcrack works fine:

C:\BitCrack>clbitcrack -o out.txt --keyspace f7051f27b08d1800:f7051f27b09112d4 16jY7qLJnxb7CHZyqBP8qca9d51gAjyXQN -b 96 -t 256 -p 256
[2022-09-26.21:32:54] [Info] Compression: compressed
[2022-09-26.21:32:54] [Info] Starting at: 000000000000000000000000000000000000000000000000F7051F27B08D1800
[2022-09-26.21:32:54] [Info] Ending at:   000000000000000000000000000000000000000000000000F7051F27B09112D4
[2022-09-26.21:32:54] [Info] Counting by: 0000000000000000000000000000000000000000000000000000000000000001
[2022-09-26.21:32:54] [Info] Compiling OpenCL kernels...
[2022-09-26.21:32:54] [Info] Initializing GeForce 820M
[2022-09-26.21:32:56] [Info] Generating 6,291,456 starting points (240.0MB)
[2022-09-26.21:33:04] [Info] 10.0%
[2022-09-26.21:33:11] [Info] 20.0%
[2022-09-26.21:33:15] [Info] 30.0%
[2022-09-26.21:33:17] [Info] 40.0%
[2022-09-26.21:33:20] [Info] 50.0%
[2022-09-26.21:33:22] [Info] 60.0%
[2022-09-26.21:33:24] [Info] 70.0%
[2022-09-26.21:33:26] [Info] 80.0%
[2022-09-26.21:33:29] [Info] 90.0%
[2022-09-26.21:33:31] [Info] 100.0%
[2022-09-26.21:33:31] [Info] Done
[2022-09-26.21:33:32] [Info] Found key for address '16jY7qLJnxb7CHZyqBP8qca9d51gAjyXQN'. Written to 'out.txt'
[2022-09-26.21:33:32] [Info] No targets remaining
[2022-09-26.21:33:32] [Info] Reached end of keyspace

C:\BitCrack>

Let me see your demonstration with more keys!!!

[italiandigger]

Try this clBitcrack -o out.txt --keyspace f7051f27a09112d4:f7051f37b09112d4 16jY7qLJnxb7CHZyqBP8qca9d51gAjyXQN

I did the suggested test with another software: keyhunt (https://github.com/secp8x32/keyhunt/tree/master/x64/Release)
The suggested test keyrange is 68.987.912.192 keys (it is useless to test it with clbitcrack because with 260000+ keys it skips the key found)

Keyhunt fullfills the target in 3.30 hours on my old laptop with geforce 820M!!!

C:\Keyhunt>keyhunt -m address -f addresses.txt -r f7051f27a09112d4:f7051f37b09112d4 -l compress -c btc -t 96

• Version 0.2.211012 Chocolate ┬íBeta!, developed by AlbertoBSD(Win64 build by KV)
• Mode address
• Search compress only
• Setting search for BTC adddress.
• Threads : 96
• Opening file addresses.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

Base key: f7051f36b08826c5     120 seconds: 374009 keys/s
HIT!! PrivKey: f7051f27b09112d4
pubkey: 03100611c54dfef604163b8358f7b7fac13ce478e02cb224ae16d45526b25d9d4d
address: 16jY7qLJnxb7CHZyqBP8qca9d51gAjyXQN
^Cse key: f7051f28c3cf56d3     580 seconds: 375917 keys/s
C:\Keyhunt>

The addresses.txt file contains only the address 16jY7qLJnxb7CHZyqBP8qca9d51gAjyXQN

I haven't enough experience to setup correctly the software, I don't know for example if and how i can allocate memory to reduce the processing time.
Keyhunt continues to elaborate the base key until the end of keyspace, i quitted it once i've seen that the key has been found.
Brainless you are right, it takes a lot of time to check 37.181.645.904.000 keys (116.160 times more than 268.436.000 keys with my old laptop if keyhunt cannot be set better)  
Clbitcrack is totally useless because it create the false illusion that the key can be found very quickly with any keyrange, but it's not true (it works with maximum 260000 keys only).
If you know how to setup better keyhunt, please let me know.
Did you tested keyhunt with better graphic cards like Gtx1080ti or Rtx3070? How many key/s do you reach?

[italiandigger]

Did you tested keyhunt with better graphic cards like Gtx1080ti or Rtx3070? How many key/s do you reach?

I asked to a friend that has both these cards to do the same test with keyhunt. He sent me the screenshots.
The results are:

GTX 1080 TI : 745.040 keys/s (desktop)

RTX 3070 : 3.410.368 keys/s (desktop with i10 processor)

It could be interesting to see how many keys/s can compute a laptop with the same RTX 3070 (price 2500$ new), the same of desktop or less? 250W is better thant 650W energy consume.

The keyrange of puzzle #66 is so big (36.893.488.147.419.107.000 keys).
With a RTX 3070 keyhunt can elaborate the complete keyrange in 10818037275572 seconds = 180300621259 minutes = 3005010354 hours =
125208764 days = 343037 anni  

[kimyzz]

From author himself few days ago, keyhunt does NOT use GPU

[italiandigger]

From author himself few days ago, keyhunt does NOT use GPU

Thanks, i was starting thinking it when there wasn't any gpu detected during keyhunt running.
The laptop heat reduction is less under stress too than with clbitcrack.

So, the cpu statistic with keyhunt is:
i7 4500U 1,80 - 2,40 Ghz = 370000 keys/s (my old 2015 laptop)
i7 6700K quad core 4.0 Ghz = 745040 keys/s
i10 (i don't exactly which one) = 3410368 keys/s

By the way i don't understand why keyunt in random mode calculates keys outside the keyspace.
I've done the following test from 1 to 5 (= 5 keys):

C:\Keyhunt>keyhunt -m address -f addresses.txt -r 1:5 -l compress -c btc -R -t 96 -M -s 2

• Version 0.2.211012 Chocolate ┬íBeta!, developed by AlbertoBSD(Win64 build by KV)
• Mode address
• Search compress only
• Setting search for BTC adddress.
• Random mode
• Threads : 96
• Matrix screen
• Stats output every 2 seconds
• Opening file addresses.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

Base key: 4
Base key: 4
Base key: 4
Base key: 4
Base key: 3
Base key: 404
Base key: 404
Base key: 1
Base key: 403
Base key: 804
Base key: 401
Base key: 804
Base key: 803
Base key: 2
Base key: 4
Base key: 1
Base key: 2
Base key: 2
Base key: 404
Base key: 804
Base key: 2
Base key: 402
Base key: 402
Base key: c04
Base key: 402
Base key: 802
Base key: 802
Base key: 801
Base key: 4
Base key: c03
Base key: 402

I quitted keyhunt after the first results.
WHY does keyhunt consider keys outside the keyspace???
I tried with keyspaces bigger than 5. Same result, a lot of keys counted are outside the keyspace! WHY???