BitCrack - A tool for brute-forcing private keys

[WanderingPhilospher]

That's some insane numbers, you sure thats a 1660 Ti? GFX902 is more like a Radeon RX Vega.
Prob. the reason Kangeroo doesn't work for you, that is CUDA only.

I was thinking the same thing however, my Vega 7s get no where close to that speed nor my 1660Tis. Who knows...

[renedx]

I was thinking the same thing however, my Vega 7s get no where close to that speed nor my 1660Tis. Who knows...

Yeah, his speed is like 4 times the speed my 3080s do and afaik these do top-speed atm on opencl version.
But I mean, AMD & openCL do work better together. But THIS good? 

[EXXXXO]

Thanks for your great help!

@NotATether,
CUDA 10.2 installation kept getting cancelled. The system is not compatible.
I am trying to install CUDA 11.2 and will test the pollard kangaroo software again this weekend.

@WanderingPhilospher, thanks for the helpful tip.

@renedx
the "gfx902" chip is the integrated onboard AMD-GPU combined with the dedicated Geforce GTX 1660 Ti in a ROG Zephyrus G14 notebook.

[renedx]

@renedx
the "gfx902" chip is the integrated onboard AMD-GPU combined with the dedicated Geforce GTX 1660 Ti in a ROG Zephyrus G14 notebook.

Aha, still very impressive results. I mean, you're better off buying that laptop instead of a 3090 at the current price if your stats are solid  
You see, I'm amazing jealous.  

You should try to tweak them params a bit, like -p 2048, it should be doing even more.
With that speed you're better of mining bitcoins. btw. LOL.

[Trancefan]

How do i create and lookup key value pair in opencl?

[fxsniper]

Can anybody help to explain How BitCrack random key. I mean, Done BitCrack random by small dot that exit and random next or random by pattern
have any image figure help to explain understand

I just think BitCrack should be develop to have more option for strategy search by pattern
BitCrack next update need to have option to powerful possibility of random method

[WanderingPhilospher]

Can anybody help to explain How BitCrack random key. I mean, Done BitCrack random by small dot that exit and random next or random by pattern
have any image figure help to explain understand

I just think BitCrack should be develop to have more option for strategy search by pattern
BitCrack next update need to have option to powerful possibility of random method

The original BitCrack does not have random feature. It breaks the search range up and then progresses key by key, point by point. I do not believe the original creator updates/upgrades/adds features to the program

[WanderingPhilospher]

@fxsniper

Here is how my random "BitCrack" works. I call it Randomonium or VanBitKraken (since it is based off of VanitySearch and BitCrack). It can regenerate random points every so many keys based off of user input or user can decide to just let the program create random points throughout a range and search sequentially from each point generated.
With the flags/setup you see below, I am telling the program to search for 1Be2U address, generate new random points every 1600 Mkeys checked. I am also tell the program to search in the 36 bit range (900000000) via the boomT flag and setting the bits via the bitz flag to 32. So all random points will start with a 9 and random 32 bits, as evident by the keys below. I have it to stop once it finds the key, that's why the program stopped. Just a small sample size to show you how it works. I know there are some versions of BitCrack out there that have a random feature but I do not know which ones work. I think BitCrack generates x amount of points (based off of your -b -t -p settings) and spreads those points over the range you have identified in the --keyspace flag, but I could be wrong.

Code:

C:\Users\your\Documents\BitRangeFinderWithRandomonium>RandomoniumV1 -t 0 -r 1600 -stop -gpu -gpuId 0 -bitz 32 -boomT 900000000 -o FoundKeysWithRandomonium.txt 1Be2UF9NLfyLFbtm3TCbmuocc9N1Kduci1
Rando-monium
Searching For: 1Be2UF9NLfyLFbtm3TCbmuocc9N1Kduci1 [Compressed]
Started at Wed Feb 24 18:41:55 2021
CPU Threads Used: 0
GPU: GPU #0 GeForce GTX 1060 6GB (10x128 cores) Grid(80x128)

Key 0: 90FB029C9
Key 1: 915AB8BEF
Key 2: 94566471B
Key 3: 9B32AD4C5
Key 10236: 916FC7D4F
Key 10237: 9941AA5CC
Key 10238: 9CA0313F6
Key 10239: 9CD679F6E
Key 0: 971B253A7
Key 1: 9747E23CC
Key 2: 97155A495
Key 3: 95ADB5819
Key 10236: 94C80D1C1
Key 10237: 9718F18A5
Key 10238: 9733219BB
[424.30 Mkey/s][GPU 424.30 Mkey/s][Total 2^30.66][Prob 0.0%][50% in 7.5709e+31y][Found 0]
Key 0: 975D40E2C
Key 1: 94693B865
Key 2: 9CB0359C2
Key 3: 9A7E99691
Key 10236: 997802E90
Key 10237: 9C4F7F057
Key 10238: 9A619E828
[402.27 Mkey/s][GPU 402.27 Mkey/s][Total 2^31.91][Prob 0.0%][50% in 7.98551e+31y][Found 0]
Key 0: 94824A22E
Key 1: 98D8DF9B2
Key 2: 95FF97060
Key 3: 90D7649EB
Key 10236: 99728C9A7
Key 10237: 942FC0681
Key 10238: 9B6305716
[396.73 Mkey/s][GPU 396.73 Mkey/s][Total 2^32.57][Prob 0.0%][50% in 8.09702e+31y][Found 0]
Key 0: 9502B7D4F
Key 1: 9A50EB31E
Key 2: 9137FF051
Key 3: 98459EFC4
Key 10236: 9A4E0E1A3
Key 10237: 955C27269
Key 10238: 9344F13EE
[396.68 Mkey/s][GPU 396.68 Mkey/s][Total 2^33.03][Prob 0.0%][50% in 8.0979e+31y][Found 0]
Key 0: 90713B8A5
Key 1: 95F65F231
Key 2: 96C034F9B
Key 3: 9D5E97324
Key 10236: 9099689AA
Key 10237: 9673E3AB2
Key 10238: 9E37BEC45
[392.72 Mkey/s][GPU 392.72 Mkey/s][Total 2^33.37][Prob 0.0%][50% in 8.17973e+31y][Found 0]
Key 0: 98ECC53D8
Key 1: 98D4A705E
Key 2: 9EE3F71FB
Key 3: 9FCDC5825
Key 10236: 91581FDF1
Key 10237: 96B2A59CF
Key 10238: 9DA85DB2D
[392.74 Mkey/s][GPU 392.74 Mkey/s][Total 2^33.64][Prob 0.0%][50% in 8.1792e+31y][Found 0]
Key 0: 9524454BC
Key 1: 911B85D89
Key 2: 964F741BA
Key 3: 9AA26E965
Key 10236: 93D1494B2
Key 10237: 9680AC923
Key 10238: 9FAFE8130
[392.75 Mkey/s][GPU 392.75 Mkey/s][Total 2^33.87][Prob 0.0%][50% in 8.17905e+31y][Found 0]
Key 0: 997B54EDC
Key 1: 999C24D45
Key 2: 9A1DBE828
Key 3: 9C151CB30
Key 10236: 95EF8F151
Key 10237: 9C899397C
Key 10238: 9A032F0C9
[392.80 Mkey/s][GPU 392.80 Mkey/s][Total 2^34.07][Prob 0.0%][50% in 8.17792e+31y][Found 0]
Key 0: 9E1CD4F93
Key 1: 999311CD2
Key 2: 92FFE0C75
Key 3: 917BB7886
Key 10236: 951B19828
Key 10237: 908EAA926
Key 10238: 9C6AEA820
Key 10239: 9AE046F3E
C:\Users\your\Documents\BitRangeFinderWithRandomonium>pause
Press any key to continue . . .

[fxsniper]

@fxsniper

Here is how my random "BitCrack" works. I call it Randomonium or VanBitKraken (since it is based off of VanitySearch and BitCrack). It can regenerate random points every so many keys based off of user input or user can decide to just let the program create random points throughout a range and search sequentially from each point generated.
With the flags/setup you see below, I am telling the program to search for 1Be2U address, generate new random points every 1600 Mkeys checked. I am also tell the program to search in the 36 bit range (900000000) via the boomT flag and setting the bits via the bitz flag to 32. So all random points will start with a 9 and random 32 bits, as evident by the keys below. I have it to stop once it finds the key, that's why the program stopped. Just a small sample size to show you how it works. I know there are some versions of BitCrack out there that have a random feature but I do not know which ones work. I think BitCrack generates x amount of points (based off of your -b -t -p settings) and spreads those points over the range you have identified in the --keyspace flag, but I could be wrong.
 

Thank you WanderingPhilospher
BitCrack is fast to generate bitcoin address to brute-force fast

For solve puzzle, all leave address
Can possible Forked BitCrack to use Pollard's kangaroo pattern
but may be easy for you help modify Forked Pollard's kangaroo to brute-force from bitcoin key
if kangaroo require pubkey for calculate x y may be can apply using from private key generate by same rank (or give sample) but target check change to bitcoin address
may be need to add function covert private key to address for check
I don't know high technical and deep programming. it scan possible, just think idea for looking way better brute-force

because on leave of puzzle, many address not have pubkey for use reference to brute-force

I think for now use BitCrack for high bits may be use very long time for brute-force , should be have some strategy for attack
I think kangaroo method is good algorithm

[fxsniper]

What BitCrack program work faster?

I download from github
https://github.com/brichard19/BitCrack/releases

BitCrack have two program clBitCrack.exe  and cuBitCrack.exe

clBitCrack.exe for using with OpenCL  (CPU/GPU Intel, AMD, Nvidia)
and
cuBitCrack.exe for using with Nvidia CUDA

I using cuBitCrack.exe  with Nvidia GeForce GTX 1050 4GB Laptop

Why cuBitCrack.exe  work slow than clBitCrack.exe

I test run BitCrack both version same time

using BitCrack both with option --device 0  for call to use GPU

GPU on Task Manager show run 95%-100%  CPU high only 18%

So on nvidia should be using clBitCrack.exe version for OpenCL is better tnan use with Nvidia CUDA

My CUDA using last version 11.2

[WanderingPhilospher]

Thank you WanderingPhilospher
BitCrack is fast to generate bitcoin address to brute-force fast

For solve puzzle, all leave address
Can possible Forked BitCrack to use Pollard's kangaroo pattern
but may be easy for you help modify Forked Pollard's kangaroo to brute-force from bitcoin key
if kangaroo require pubkey for calculate x y may be can apply using from private key generate by same rank (or give sample) but target check change to bitcoin address
may be need to add function covert private key to address for check
I don't know high technical and deep programming. it scan possible, just think idea for looking way better brute-force

because on leave of puzzle, many address not have pubkey for use reference to brute-force

I think for now use BitCrack for high bits may be use very long time for brute-force , should be have some strategy for attack
I think kangaroo method is good algorithm

You can use python and batch scripts, with BitCrack, to mimic what Kangaroo is doing, as far as jumps. But there is no way to make it look for pubkeys, it is a brute force program. I mean you could tweak it to a Kangaroo program but Jean Luc's Kangaroo would be much faster.

[fxsniper]

reference
https://github.com/brichard19/BitCrack/releases/tag/0.31

I found problem on clBitCrack.exe

Can anyone help to testing if you have BitCrack on you PC/laptop?

I found cuBitCrack.exe can found private key
but, clBitCrack.exe can not found private key

test puzzle #115  1NLbHuJebVwUZ1XqDjsAyfTRUPwDQbemfv

command
cuBitCrack.exe --device 0 -o output.txt --keyspace 60F4D11574F5DEEE49961D8577307:60F4D11574F5DEEE49961DA609AC5 1NLbHuJebVwUZ1XqDjsAyfTRUPwDQbemfv
cuBitCrack.exe -o output.txt --keyspace 60F4D11574F5DEEE49961D8577307:60F4D11574F5DEEE49961DA609AC5 1NLbHuJebVwUZ1XqDjsAyfTRUPwDQbemfv

clBitCrack.exe --device 0 -o output.txt --keyspace 60F4D11574F5DEEE49961D8577307:60F4D11574F5DEEE49961DA609AC5 1NLbHuJebVwUZ1XqDjsAyfTRUPwDQbemfv
clBitCrack.exe -o output.txt --keyspace 60F4D11574F5DEEE49961D8577307:60F4D11574F5DEEE49961DA609AC5 1NLbHuJebVwUZ1XqDjsAyfTRUPwDQbemfv

you will be found private key in second
upper both same command options and same keyspace

problem
Result test cuBitCrack.exe can found key
but clBitCrack.exe work fast and never found key

clBitCrack.exe  will be work fast and end with message Reached end of keyspace
but clBitCrack.exe  never found key


cuBitCrack.exe result
GeForce GTX 1050 738 / 4096MB | 1 target 6.11 MKey/s (4,008,181,760 total) [00:10:57] [Info] Found key for address '1NLbHuJebVwUZ1XqDjsAyfTRUPwDQbemfv'. Written to 'output.txt'

[WanderingPhilospher]

Hello guys,
Is there a way to stop the work and continue later at this point?

That's some insane numbers, you sure thats a 1660 Ti? GFX902 is more like a Radeon RX Vega.
Prob. the reason Kangeroo doesn't work for you, that is CUDA only.

Now I see, they are using the cl version which shows higher rate but doesn't find the key. I believe there are none issues with cl version. @fxsniper just posted his results while saying cl was faster MKey/s rate, but never found the key. 

[fxsniper]

Now I see, they are using the cl version which shows higher rate but doesn't find the key. I believe there are none issues with cl version. @fxsniper just posted his results while saying cl was faster MKey/s rate, but never found the key. 

WanderingPhilospher

How can I Re-Compiling OpenCL kernels?


I testing by download other release version to test it still work fine

may be problem is my Compiling OpenCL kernels..

version have problem is 0.31 latest

I download clBitCrack.exe from release 0.31 0.30 .. 0.24 all

I found 0.30 and other still work fine normal and success found key

I don't know how process program work and how OpenCL works

when run other release version 0.30 and 0.29   clBitCrack.exe waiting for Compiling OpenCL kernels... for that release run
that mean each release will Compiling OpenCL kernels new one

So, can possible if I can RE-Compiling OpenCL kernels last version 0.31  may be it work again

I test  clBitCrack.exe version 0.31 on 2 laptop is same result  can not find any private key and program finish work with   100.0% Done Reached end of keyspace

Can anyone try to test clBitCrack.exe  on you PC/laptop  last version 0.31 (Improve OpenCL performance)

and if you need to use  clBitCrack.exe OpenCL version try back to use version 0.30 or 0.29

[WanderingPhilospher]

Now I see, they are using the cl version which shows higher rate but doesn't find the key. I believe there are none issues with cl version. @fxsniper just posted his results while saying cl was faster MKey/s rate, but never found the key. 

WanderingPhilospher

How can I Re-Compiling OpenCL kernels?


I test  clBitCrack.exe version 0.31 on 2 laptop is same result  can not find any private key and program finish work with   100.0% Done Reached end of keyspace

Can anyone try to test clBitCrack.exe  on you PC/laptop  last version 0.31 (Improve OpenCL performance)

and if you need to use  clBitCrack.exe OpenCL version try back to use version 0.30 or 0.29

Same results here. release 30 works and release 31 does not.
I would not know how to mess with OpenCL.  Does cu (cuda) bitcrack not work for you? In order for me to use it, I have to  install older drivers, and then it works.

[NotATether]

Can anyone try to test clBitCrack.exe  on you PC/laptop  last version 0.31 (Improve OpenCL performance)

I just looked at those commits leading to 0.31, and while I don't know much about OpenCL, it seems that the only major change he made is to replace the representation of 256-bit numbers from an array of 8 32-bit bits to a struct with an array of 8 32-bit bits (and some loops were unrolled). I don't see how this is supposed to make it run faster because it should've used a larger word size like a 64-bit cl_ulong, which would reduce the number of load and store instructions by half. Nobody uses 32-bit platforms any more so there's no reason to keep a 32-bit version around and therefore constrain all the arrays to use 32-bit ints as well.

[t0nyst4r]

0.31 would not find those test keys for me either using clbitcrack. Anyone have a link to 0.30 precompiled so I can test? Can't seem to get 0.30 to compile under Windows.

[renedx]

reference
https://github.com/brichard19/BitCrack/releases/tag/0.31

I found problem on clBitCrack.exe

Can anyone help to testing if you have BitCrack on you PC/laptop?

I found cuBitCrack.exe can found private key
but, clBitCrack.exe can not found private key

test puzzle #115  1NLbHuJebVwUZ1XqDjsAyfTRUPwDQbemfv

command
cuBitCrack.exe --device 0 -o output.txt --keyspace 60F4D11574F5DEEE49961D8577307:60F4D11574F5DEEE49961DA609AC5 1NLbHuJebVwUZ1XqDjsAyfTRUPwDQbemfv
cuBitCrack.exe -o output.txt --keyspace 60F4D11574F5DEEE49961D8577307:60F4D11574F5DEEE49961DA609AC5 1NLbHuJebVwUZ1XqDjsAyfTRUPwDQbemfv

clBitCrack.exe --device 0 -o output.txt --keyspace 60F4D11574F5DEEE49961D8577307:60F4D11574F5DEEE49961DA609AC5 1NLbHuJebVwUZ1XqDjsAyfTRUPwDQbemfv
clBitCrack.exe -o output.txt --keyspace 60F4D11574F5DEEE49961D8577307:60F4D11574F5DEEE49961DA609AC5 1NLbHuJebVwUZ1XqDjsAyfTRUPwDQbemfv

you will be found private key in second
upper both same command options and same keyspace

problem
Result test cuBitCrack.exe can found key
but clBitCrack.exe work fast and never found key

clBitCrack.exe  will be work fast and end with message Reached end of keyspace
but clBitCrack.exe  never found key


cuBitCrack.exe result
GeForce GTX 1050 738 / 4096MB | 1 target 6.11 MKey/s (4,008,181,760 total) [00:10:57] [Info] Found key for address '1NLbHuJebVwUZ1XqDjsAyfTRUPwDQbemfv'. Written to 'output.txt'

You just need a fixed CL version. The forum/issues tracker is full of solutions;

Code:

clBitCrack.exe -o output.txt --keyspace 60F4D11574F5DEEE49961D8577307:60F4D11574F5DEEE49961DA609AC5 1NLbHuJebVwUZ1XqDjsAyfTRUPwDQbemfv
[2021-02-26.14:35:16] [Info] Compression: compressed
[2021-02-26.14:35:16] [Info] Starting at: 0000000000000000000000000000000000060F4D11574F5DEEE49961D8577307
[2021-02-26.14:35:16] [Info] Ending at:   0000000000000000000000000000000000060F4D11574F5DEEE49961DA609AC5
[2021-02-26.14:35:16] [Info] Counting by: 0000000000000000000000000000000000000000000000000000000000000001
[2021-02-26.14:35:17] [Info] Compiling OpenCL kernels...
[2021-02-26.14:35:17] [Info] Initializing GeForce RTX 3090
[2021-02-26.14:35:17] [Info] Generating 262,144 starting points (10.0MB)
[2021-02-26.14:35:17] [Info] 10.0%
[2021-02-26.14:35:17] [Info] 20.0%
[2021-02-26.14:35:17] [Info] 30.0%
[2021-02-26.14:35:17] [Info] 40.0%
[2021-02-26.14:35:17] [Info] 50.0%
[2021-02-26.14:35:17] [Info] 60.0%
[2021-02-26.14:35:17] [Info] 70.0%
[2021-02-26.14:35:17] [Info] 80.0%
[2021-02-26.14:35:17] [Info] 90.0%
[2021-02-26.14:35:17] [Info] 100.0%
[2021-02-26.14:35:17] [Info] Done
[2021-02-26.14:35:17] [Info] Found key for address '1NLbHuJebVwUZ1XqDjsAyfTRUPwDQbemfv'. Written to 'output.txt'
[2021-02-26.14:35:17] [Info] No targets remaining

[WanderingPhilospher]

0.31 would not find those test keys for me either using clbitcrack. Anyone have a link to 0.30 precompiled so I can test? Can't seem to get 0.30 to compile under Windows.

https://github.com/brichard19/BitCrack/releases/tag/0.30

[t0nyst4r]

You just need a fixed CL version. The forum/issues tracker is full of solutions;

Code:

clBitCrack.exe -o output.txt --keyspace 60F4D11574F5DEEE49961D8577307:60F4D11574F5DEEE49961DA609AC5 1NLbHuJebVwUZ1XqDjsAyfTRUPwDQbemfv
[2021-02-26.14:35:16] [Info] Compression: compressed
[2021-02-26.14:35:16] [Info] Starting at: 0000000000000000000000000000000000060F4D11574F5DEEE49961D8577307
[2021-02-26.14:35:16] [Info] Ending at:   0000000000000000000000000000000000060F4D11574F5DEEE49961DA609AC5
[2021-02-26.14:35:16] [Info] Counting by: 0000000000000000000000000000000000000000000000000000000000000001
[2021-02-26.14:35:17] [Info] Compiling OpenCL kernels...
[2021-02-26.14:35:17] [Info] Initializing GeForce RTX 3090
[2021-02-26.14:35:17] [Info] Generating 262,144 starting points (10.0MB)
[2021-02-26.14:35:17] [Info] 10.0%
[2021-02-26.14:35:17] [Info] 20.0%
[2021-02-26.14:35:17] [Info] 30.0%
[2021-02-26.14:35:17] [Info] 40.0%
[2021-02-26.14:35:17] [Info] 50.0%
[2021-02-26.14:35:17] [Info] 60.0%
[2021-02-26.14:35:17] [Info] 70.0%
[2021-02-26.14:35:17] [Info] 80.0%
[2021-02-26.14:35:17] [Info] 90.0%
[2021-02-26.14:35:17] [Info] 100.0%
[2021-02-26.14:35:17] [Info] Done
[2021-02-26.14:35:17] [Info] Found key for address '1NLbHuJebVwUZ1XqDjsAyfTRUPwDQbemfv'. Written to 'output.txt'
[2021-02-26.14:35:17] [Info] No targets remaining

"Fixed" clbitcrack as in using an older build like 0.30, or a fixed version of 0.31? I just tried 0.30 and while it finds all keys ok, it's about half as fast as 0.31. I have 3090's so I believe I'm stuck using clbitcrack until the misaligned address issue is fixed for these newer cards that require the newer CUDA.