BitCrack - A tool for brute-forcing private keys

[fxsniper]

some detail
both version optimize GPU
both use memory a lot for calculate it made continue search will struck when search over memory used
if run only one time not a problem
may be possible about free memory after used
I solve that problem by open new windows or new process
example batch file modify code to open new windows
or program lunch by open new windows (when finish and windows close with close memory)

[1715138796]

1715138796

[NotATether]

I have released a faster binary of bitcrack.

https://github.com/sp-hash/Bitcrack/releases/tag/sp-mod1

The build require Compute 61 or newer (pascal). Please test. What hashrates are you getting?

[img ]https://i.ibb.co/prM8c7S/bitcrack.png[/img]

Great job!

I will try this on my T4, so compute 75 (it's taking some time to compile as usual). [EDIT - I just did, unfortunately that idiot misaligned address error is still there but since I sorta found what is being misaligned I think it's just a matter of making a couple of 32-bit pointer arrays 64-bit.]

I also noticed you fixed the bug that made clBitCrack skip way too many points than it should - I remember there was someone here complaining that the search finished too quickly.

You should probably change the COMPUTE_CAP variable in the Makefile though - It's still at the default 30 although it will not compile on that compute cap.

I can give you a bash script that autodetects the CUDA version using the deviceQuery example program. I'm using it in my Makefile for another project (custom Kangaroo) that I haven't released yet.


Wait an idea just hit me. All of the 256bit numbers are stored in 32-bit bits so if all of that gets upgraded to 64-bits then we will have just doubled the speed of this program while also destroying the misaligned access error (because I suspect that Volta/Turing/Ampere will no longer align array elements across 32-bits, only 64 or 128).

[_Counselor]

I have released a faster binary of bitcrack.

https://github.com/sp-hash/Bitcrack/releases/tag/sp-mod1

The build require Compute 61 or newer (pascal). Please test. What hashrates are you getting?

Tesla V100 and Tesla P100 shows no difference between original and modified versions

[brainless]

I have released a faster binary of bitcrack.

https://github.com/sp-hash/Bitcrack/releases/tag/sp-mod1

The build require Compute 61 or newer (pascal). Please test. What hashrates are you getting?

[img ]https://i.ibb.co/prM8c7S/bitcrack.png[/img]

Great job!

I will try this on my T4, so compute 75 (it's taking some time to compile as usual). [EDIT - I just did, unfortunately that idiot misaligned address error is still there but since I sorta found what is being misaligned I think it's just a matter of making a couple of 32-bit pointer arrays 64-bit.]

I also noticed you fixed the bug that made clBitCrack skip way too many points than it should - I remember there was someone here complaining that the search finished too quickly.

You should probably change the COMPUTE_CAP variable in the Makefile though - It's still at the default 30 although it will not compile on that compute cap.

I can give you a bash script that autodetects the CUDA version using the deviceQuery example program. I'm using it in my Makefile for another project (custom Kangaroo) that I haven't released yet.


Wait an idea just hit me. All of the 256bit numbers are stored in 32-bit bits so if all of that gets upgraded to 64-bits then we will have just doubled the speed of this program while also destroying the misaligned access error (because I suspect that Volta/Turing/Ampere will no longer align array elements across 32-bits, only 64 or 128).

all fork including orginal ver of bitcrack have bug, result address wrong print follow

 ./cuBitCrack -b 7 -t 512 -p 1156 11HWBme5fYis2SZ5PXLL5qEj9L3vxUVtZ -o new0321.txt -c -u
[2021-03-21.00:38:24] [Info] Compression: both
[2021-03-21.00:38:24] [Info] Starting at: 0000000000000000000000000000000000000000000000000000000000000001
[2021-03-21.00:38:24] [Info] Ending at:   FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFEBAAEDCE6AF48A03BBFD25E8CD0364140
[2021-03-21.00:38:24] [Info] Counting by: 0000000000000000000000000000000000000000000000000000000000000001
[2021-03-21.00:38:24] [Info] Initializing GeForce GTX 460
[2021-03-21.00:38:24] [Info] Generating 4,143,104 starting points (158.0MB)
[2021-03-21.00:38:25] [Info] 10.0%
[2021-03-21.00:38:25] [Info] 20.0%
[2021-03-21.00:38:25] [Info] 30.0%
[2021-03-21.00:38:25] [Info] 40.0%
[2021-03-21.00:38:26] [Info] 50.0%
[2021-03-21.00:38:26] [Info] 60.0%
[2021-03-21.00:38:26] [Info] 70.0%
[2021-03-21.00:38:26] [Info] 80.0%
[2021-03-21.00:38:26] [Info] 90.0%
[2021-03-21.00:38:26] [Info] 100.0%
[2021-03-21.00:38:26] [Info] Done
[2021-03-21.00:38:26] [Info] Found key for address '1HWBme5fYis2SZ5PXLL5qEj9L3vxUVtZ'. Written to 'new0321.txt'
[2021-03-21.00:38:26] [Info] No targets remaining
 
original address for search, and reult print next
11HWBme5fYis2SZ5PXLL5qEj9L3vxUVtZ
and reult print next
1HWBme5fYis2SZ5PXLL5qEj9L3vxUVtZ

check these addresses same
original addresses
111oGz8t35hUQunGAvhwkBTJuzXVMr3j
1111BxbRo6FeiBX8tegyzCk9jCnmBe7SE
111HfAJagjbBRw2N9zfQVucXoPi2znNjr
11HWBme5fYis2SZ5PXLL5qEj9L3vxUVtZ
11Af6ENu11SZiw3tCoXVGE5JxjmTAhjFr

result

1oGz8t35hUQunGAvhwkBTJuzXVMr3j
1BxbRo6FeiBX8tegyzCk9jCnmBe7SE
1HfAJagjbBRw2N9zfQVucXoPi2znNjr
1HWBme5fYis2SZ5PXLL5qEj9L3vxUVtZ
1Af6ENu11SZiw3tCoXVGE5JxjmTAhjFr

[sp_]

Tesla V100 and Tesla P100 shows no difference between original and modified versions

What is the speed on the V100 and the P100, and what is the launch config?

[sp_]

because I suspect that Volta/Turing/Ampere will no longer align array elements across 32-bits, only 64 or 128).

The new version is using vector instructions to read and write to memory. Alligned to 16 byte borders. My exe was compiled and optimized with compute61 and sm61 only.

[fxsniper]

How can setup Tesla V100 on google cloud?
and when using on google cloud is use on linux right?

how I compile bitcrack on linux ?
I try on ubuntu on windows subsystem already not success compile
I use command make already but have error on linux subsystem not have CUDA
no bitcrack program
have only program addrgen

[NotATether]

how I compile bitcrack on linux ?
I try on ubuntu on windows subsystem already not success compile
I use command make already but have error on linux subsystem not have CUDA
no bitcrack program
have only program addrgen

Add BUILD_CUDA=1 at the end of the make call. To adjust the compute cap add COMPUTE_CAP=xy as well, where "x" is the major version and "y" is the minor version of the compute cap without any dot in the middle, eg "61", "35" and "52".

[fxsniper]

Add BUILD_CUDA=1 at the end of the make call. To adjust the compute cap add COMPUTE_CAP=xy as well, where "x" is the major version and "y" is the minor version of the compute cap without any dot in the middle, eg "61", "35" and "52".

Thank you I will try again on linux

[fxsniper]

some error on all bitcrack all version include original

may be only me error only happen on my laptop

when run script batch file and bitcrack struck with scan not finish

bitcrack should be open scan and close by fast

but when feel while minute bitcrack will be scan and not finish and continue run non stop

Code:

start /wait cuBitCrack.exe --device 0 -c -u -o 16jY7qL.txt --keyspace 8b9052780c6a8800:8b9072780c6a9000 16jY7qLJnxb7CHZyqBP8qca9d51gAjyXQN 
start /wait cuBitCrack.exe --device 0 -c -u -o 16jY7qL.txt --keyspace 98b9b228d0d42800:98b9d228d0d42800 16jY7qLJnxb7CHZyqBP8qca9d51gAjyXQN 
start /wait cuBitCrack.exe --device 0 -c -u -o 16jY7qL.txt --keyspace 9e4b41ba17b24800:9e4b61ba17b24800 16jY7qLJnxb7CHZyqBP8qca9d51gAjyXQN 
start /wait cuBitCrack.exe --device 0 -c -u -o 16jY7qL.txt --keyspace a4f4e25630790000:a4f5025630790000 16jY7qLJnxb7CHZyqBP8qca9d51gAjyXQN 
start /wait cuBitCrack.exe --device 0 -c -u -o 16jY7qL.txt --keyspace af55ec59c335c800:af560c59c335c800 16jY7qLJnxb7CHZyqBP8qca9d51gAjyXQN 
start /wait cuBitCrack.exe --device 0 -c -u -o 16jY7qL.txt --keyspace b19d5e1486268800:b19d7e1486268800 16jY7qLJnxb7CHZyqBP8qca9d51gAjyXQN 
start /wait cuBitCrack.exe --device 0 -c -u -o 16jY7qL.txt --keyspace b3801ec84da91000:b3803ec84da91000 16jY7qLJnxb7CHZyqBP8qca9d51gAjyXQN 
start /wait cuBitCrack.exe --device 0 -c -u -o 16jY7qL.txt --keyspace b78a6e102a66c000:b78a8e102a66c800 16jY7qLJnxb7CHZyqBP8qca9d51gAjyXQN 
start /wait cuBitCrack.exe --device 0 -c -u -o 16jY7qL.txt --keyspace c1e9922ae9ebc000:c1e9b22ae9ebc000 16jY7qLJnxb7CHZyqBP8qca9d51gAjyXQN 
start /wait cuBitCrack.exe --device 0 -c -u -o 16jY7qL.txt --keyspace d26e02d90c69b000:d26e22d90c69b000 16jY7qLJnxb7CHZyqBP8qca9d51gAjyXQN 
start /wait cuBitCrack.exe --device 0 -c -u -o 16jY7qL.txt --keyspace d41c489a82d93000:d41c689a82d93000 16jY7qLJnxb7CHZyqBP8qca9d51gAjyXQN 
start /wait cuBitCrack.exe --device 0 -c -u -o 16jY7qL.txt --keyspace d7034c8d37df7800:d7036c8d37df8000 16jY7qLJnxb7CHZyqBP8qca9d51gAjyXQN 
start /wait cuBitCrack.exe --device 0 -c -u -o 16jY7qL.txt --keyspace d8f5407ad846b000:d8f5607ad846b000 16jY7qLJnxb7CHZyqBP8qca9d51gAjyXQN 
start /wait cuBitCrack.exe --device 0 -c -u -o 16jY7qL.txt --keyspace e92d8770f9568800:e92da770f9569000 16jY7qLJnxb7CHZyqBP8qca9d51gAjyXQN 
start /wait cuBitCrack.exe --device 0 -c -u -o 16jY7qL.txt --keyspace ea1a4c66dcc11800:ea1a6c66dcc12000 16jY7qLJnxb7CHZyqBP8qca9d51gAjyXQN 
start /wait cuBitCrack.exe --device 0 -c -u -o 16jY7qL.txt --keyspace f99cadfb599ed000:f99ccdfb599ed000 16jY7qLJnxb7CHZyqBP8qca9d51gAjyXQN 
start /wait cuBitCrack.exe --device 0 -c -u -o 16jY7qL.txt --keyspace fc0791825367b800:fc07b1825367c000 16jY7qLJnxb7CHZyqBP8qca9d51gAjyXQN 

Code:

start /wait cuBitCrack.exe --device 0 -c -u -o 16jY7qLJnxb7CHZ.txt --keyspace 8b9062780c5b45c0:8b9062780c79d240 16jY7qLJnxb7CHZyqBP8qca9d51gAjyXQN
start /wait cuBitCrack.exe --device 0 -c -u -o 16jY7qLJnxb7CHZ.txt --keyspace 98b9c228d0c4e5c0:98b9c228d0e36a40 16jY7qLJnxb7CHZyqBP8qca9d51gAjyXQN
start /wait cuBitCrack.exe --device 0 -c -u -o 16jY7qLJnxb7CHZ.txt --keyspace 9e4b51ba17a305c0:9e4b51ba17c18a40 16jY7qLJnxb7CHZyqBP8qca9d51gAjyXQN
start /wait cuBitCrack.exe --device 0 -c -u -o 16jY7qLJnxb7CHZ.txt --keyspace a4f4f2563069bdc0:a4f4f25630884240 16jY7qLJnxb7CHZyqBP8qca9d51gAjyXQN
start /wait cuBitCrack.exe --device 0 -c -u -o 16jY7qLJnxb7CHZ.txt --keyspace af55fc59c32685c0:af55fc59c3450a40 16jY7qLJnxb7CHZyqBP8qca9d51gAjyXQN
start /wait cuBitCrack.exe --device 0 -c -u -o 16jY7qLJnxb7CHZ.txt --keyspace b19d6e14861745c0:b19d6e148635ca40 16jY7qLJnxb7CHZyqBP8qca9d51gAjyXQN
start /wait cuBitCrack.exe --device 0 -c -u -o 16jY7qLJnxb7CHZ.txt --keyspace b3802ec84d99cdc0:b3802ec84db85240 16jY7qLJnxb7CHZyqBP8qca9d51gAjyXQN
start /wait cuBitCrack.exe --device 0 -c -u -o 16jY7qLJnxb7CHZ.txt --keyspace b78a7e102a577dc0:b78a7e102a760a40 16jY7qLJnxb7CHZyqBP8qca9d51gAjyXQN
start /wait cuBitCrack.exe --device 0 -c -u -o 16jY7qLJnxb7CHZ.txt --keyspace c1e9a22ae9dc7dc0:c1e9a22ae9fb0240 16jY7qLJnxb7CHZyqBP8qca9d51gAjyXQN
start /wait cuBitCrack.exe --device 0 -c -u -o 16jY7qLJnxb7CHZ.txt --keyspace d26e12d90c5a6dc0:d26e12d90c78f240 16jY7qLJnxb7CHZyqBP8qca9d51gAjyXQN
start /wait cuBitCrack.exe --device 0 -c -u -o 16jY7qLJnxb7CHZ.txt --keyspace d41c589a82c9edc0:d41c589a82e87240 16jY7qLJnxb7CHZyqBP8qca9d51gAjyXQN
start /wait cuBitCrack.exe --device 0 -c -u -o 16jY7qLJnxb7CHZ.txt --keyspace d7035c8d37d035c0:d7035c8d37eec240 16jY7qLJnxb7CHZyqBP8qca9d51gAjyXQN
start /wait cuBitCrack.exe --device 0 -c -u -o 16jY7qLJnxb7CHZ.txt --keyspace d7035c8d37d035c0:d8f5507ad855f240 16jY7qLJnxb7CHZyqBP8qca9d51gAjyXQN
start /wait cuBitCrack.exe --device 0 -c -u -o 16jY7qLJnxb7CHZ.txt --keyspace d8f5507ad8376dc0:e92d9770f965d240 16jY7qLJnxb7CHZyqBP8qca9d51gAjyXQN
start /wait cuBitCrack.exe --device 0 -c -u -o 16jY7qLJnxb7CHZ.txt --keyspace ea1a5c66dcb1d5c0:ea1a5c66dcd06240 16jY7qLJnxb7CHZyqBP8qca9d51gAjyXQN
start /wait cuBitCrack.exe --device 0 -c -u -o 16jY7qLJnxb7CHZ.txt --keyspace f99cbdfb598f8dc0:f99cbdfb59ae1240 16jY7qLJnxb7CHZyqBP8qca9d51gAjyXQN
start /wait cuBitCrack.exe --device 0 -c -u -o 16jY7qLJnxb7CHZ.txt --keyspace fc07a182535875c0:fc07a18253770240 16jY7qLJnxb7CHZyqBP8qca9d51gAjyXQN

[brainless]

some error on all bitcrack all version include original

may be only me error only happen on my laptop

when run script batch file and bitcrack struck with scan not finish

bitcrack should be open scan and close by fast

but when feel while minute bitcrack will be scan and not finish and continue run non stop

Code:

start /wait cuBitCrack.exe --device 0 -c -u -o 16jY7qL.txt --keyspace 8b9052780c6a8800:8b9072780c6a9000 16jY7qLJnxb7CHZyqBP8qca9d51gAjyXQN 
start /wait cuBitCrack.exe --device 0 -c -u -o 16jY7qL.txt --keyspace 98b9b228d0d42800:98b9d228d0d42800 16jY7qLJnxb7CHZyqBP8qca9d51gAjyXQN 
start /wait cuBitCrack.exe --device 0 -c -u -o 16jY7qL.txt --keyspace 9e4b41ba17b24800:9e4b61ba17b24800 16jY7qLJnxb7CHZyqBP8qca9d51gAjyXQN 
start /wait cuBitCrack.exe --device 0 -c -u -o 16jY7qL.txt --keyspace a4f4e25630790000:a4f5025630790000 16jY7qLJnxb7CHZyqBP8qca9d51gAjyXQN 
start /wait cuBitCrack.exe --device 0 -c -u -o 16jY7qL.txt --keyspace af55ec59c335c800:af560c59c335c800 16jY7qLJnxb7CHZyqBP8qca9d51gAjyXQN 
start /wait cuBitCrack.exe --device 0 -c -u -o 16jY7qL.txt --keyspace b19d5e1486268800:b19d7e1486268800 16jY7qLJnxb7CHZyqBP8qca9d51gAjyXQN 
start /wait cuBitCrack.exe --device 0 -c -u -o 16jY7qL.txt --keyspace b3801ec84da91000:b3803ec84da91000 16jY7qLJnxb7CHZyqBP8qca9d51gAjyXQN 
start /wait cuBitCrack.exe --device 0 -c -u -o 16jY7qL.txt --keyspace b78a6e102a66c000:b78a8e102a66c800 16jY7qLJnxb7CHZyqBP8qca9d51gAjyXQN 
start /wait cuBitCrack.exe --device 0 -c -u -o 16jY7qL.txt --keyspace c1e9922ae9ebc000:c1e9b22ae9ebc000 16jY7qLJnxb7CHZyqBP8qca9d51gAjyXQN 
start /wait cuBitCrack.exe --device 0 -c -u -o 16jY7qL.txt --keyspace d26e02d90c69b000:d26e22d90c69b000 16jY7qLJnxb7CHZyqBP8qca9d51gAjyXQN 
start /wait cuBitCrack.exe --device 0 -c -u -o 16jY7qL.txt --keyspace d41c489a82d93000:d41c689a82d93000 16jY7qLJnxb7CHZyqBP8qca9d51gAjyXQN 
start /wait cuBitCrack.exe --device 0 -c -u -o 16jY7qL.txt --keyspace d7034c8d37df7800:d7036c8d37df8000 16jY7qLJnxb7CHZyqBP8qca9d51gAjyXQN 
start /wait cuBitCrack.exe --device 0 -c -u -o 16jY7qL.txt --keyspace d8f5407ad846b000:d8f5607ad846b000 16jY7qLJnxb7CHZyqBP8qca9d51gAjyXQN 
start /wait cuBitCrack.exe --device 0 -c -u -o 16jY7qL.txt --keyspace e92d8770f9568800:e92da770f9569000 16jY7qLJnxb7CHZyqBP8qca9d51gAjyXQN 
start /wait cuBitCrack.exe --device 0 -c -u -o 16jY7qL.txt --keyspace ea1a4c66dcc11800:ea1a6c66dcc12000 16jY7qLJnxb7CHZyqBP8qca9d51gAjyXQN 
start /wait cuBitCrack.exe --device 0 -c -u -o 16jY7qL.txt --keyspace f99cadfb599ed000:f99ccdfb599ed000 16jY7qLJnxb7CHZyqBP8qca9d51gAjyXQN 
start /wait cuBitCrack.exe --device 0 -c -u -o 16jY7qL.txt --keyspace fc0791825367b800:fc07b1825367c000 16jY7qLJnxb7CHZyqBP8qca9d51gAjyXQN 

Code:

start /wait cuBitCrack.exe --device 0 -c -u -o 16jY7qLJnxb7CHZ.txt --keyspace 8b9062780c5b45c0:8b9062780c79d240 16jY7qLJnxb7CHZyqBP8qca9d51gAjyXQN
start /wait cuBitCrack.exe --device 0 -c -u -o 16jY7qLJnxb7CHZ.txt --keyspace 98b9c228d0c4e5c0:98b9c228d0e36a40 16jY7qLJnxb7CHZyqBP8qca9d51gAjyXQN
start /wait cuBitCrack.exe --device 0 -c -u -o 16jY7qLJnxb7CHZ.txt --keyspace 9e4b51ba17a305c0:9e4b51ba17c18a40 16jY7qLJnxb7CHZyqBP8qca9d51gAjyXQN
start /wait cuBitCrack.exe --device 0 -c -u -o 16jY7qLJnxb7CHZ.txt --keyspace a4f4f2563069bdc0:a4f4f25630884240 16jY7qLJnxb7CHZyqBP8qca9d51gAjyXQN
start /wait cuBitCrack.exe --device 0 -c -u -o 16jY7qLJnxb7CHZ.txt --keyspace af55fc59c32685c0:af55fc59c3450a40 16jY7qLJnxb7CHZyqBP8qca9d51gAjyXQN
start /wait cuBitCrack.exe --device 0 -c -u -o 16jY7qLJnxb7CHZ.txt --keyspace b19d6e14861745c0:b19d6e148635ca40 16jY7qLJnxb7CHZyqBP8qca9d51gAjyXQN
start /wait cuBitCrack.exe --device 0 -c -u -o 16jY7qLJnxb7CHZ.txt --keyspace b3802ec84d99cdc0:b3802ec84db85240 16jY7qLJnxb7CHZyqBP8qca9d51gAjyXQN
start /wait cuBitCrack.exe --device 0 -c -u -o 16jY7qLJnxb7CHZ.txt --keyspace b78a7e102a577dc0:b78a7e102a760a40 16jY7qLJnxb7CHZyqBP8qca9d51gAjyXQN
start /wait cuBitCrack.exe --device 0 -c -u -o 16jY7qLJnxb7CHZ.txt --keyspace c1e9a22ae9dc7dc0:c1e9a22ae9fb0240 16jY7qLJnxb7CHZyqBP8qca9d51gAjyXQN
start /wait cuBitCrack.exe --device 0 -c -u -o 16jY7qLJnxb7CHZ.txt --keyspace d26e12d90c5a6dc0:d26e12d90c78f240 16jY7qLJnxb7CHZyqBP8qca9d51gAjyXQN
start /wait cuBitCrack.exe --device 0 -c -u -o 16jY7qLJnxb7CHZ.txt --keyspace d41c589a82c9edc0:d41c589a82e87240 16jY7qLJnxb7CHZyqBP8qca9d51gAjyXQN
start /wait cuBitCrack.exe --device 0 -c -u -o 16jY7qLJnxb7CHZ.txt --keyspace d7035c8d37d035c0:d7035c8d37eec240 16jY7qLJnxb7CHZyqBP8qca9d51gAjyXQN
start /wait cuBitCrack.exe --device 0 -c -u -o 16jY7qLJnxb7CHZ.txt --keyspace d7035c8d37d035c0:d8f5507ad855f240 16jY7qLJnxb7CHZyqBP8qca9d51gAjyXQN
start /wait cuBitCrack.exe --device 0 -c -u -o 16jY7qLJnxb7CHZ.txt --keyspace d8f5507ad8376dc0:e92d9770f965d240 16jY7qLJnxb7CHZyqBP8qca9d51gAjyXQN
start /wait cuBitCrack.exe --device 0 -c -u -o 16jY7qLJnxb7CHZ.txt --keyspace ea1a5c66dcb1d5c0:ea1a5c66dcd06240 16jY7qLJnxb7CHZyqBP8qca9d51gAjyXQN
start /wait cuBitCrack.exe --device 0 -c -u -o 16jY7qLJnxb7CHZ.txt --keyspace f99cbdfb598f8dc0:f99cbdfb59ae1240 16jY7qLJnxb7CHZyqBP8qca9d51gAjyXQN
start /wait cuBitCrack.exe --device 0 -c -u -o 16jY7qLJnxb7CHZ.txt --keyspace fc07a182535875c0:fc07a18253770240 16jY7qLJnxb7CHZyqBP8qca9d51gAjyXQN

mistake in your command, puzzle address already confirmed its compressed address, you are useing command for search compressed and uncompressed, -c -u, it will eat your speed
start /wait cuBitCrack.exe --device 0 -c -u

remove -u from you command for better speed

[zahid888]

I have released a faster binary of bitcrack.

https://github.com/sp-hash/Bitcrack/releases/tag/sp-mod1

The build require Compute 61 or newer (pascal). Please test. What hashrates are you getting?

[2021-03-21.12:01:10] [Info] Compression: compressed
[2021-03-21.12:01:10] [Info] Starting at: 000000000000000000000000000000000000000000000000800000000AC82391
[2021-03-21.12:01:10] [Info] Ending at:   000000000000000000000000000000000000000000000000FFFFFFFFFFFFFFFF
[2021-03-21.12:01:10] [Info] Counting by: 0000000000000000000000000000000000000000000000000000000010000000
[2021-03-21.12:01:10] [Info] Initializing GeForce RTX 3060 Ti
[2021-03-21.12:01:16] [Info] Generating 33,554,432 starting points (1280.0MB)
[2021-03-21.12:01:19] [Info] 10.0%
[2021-03-21.12:01:20] [Info] 20.0%
[2021-03-21.12:01:20] [Info] 30.0%
[2021-03-21.12:01:21] [Info] 40.0%
[2021-03-21.12:01:21] [Info] 50.0%
[2021-03-21.12:01:21] [Info] 60.0%
[2021-03-21.12:01:21] [Info] 70.0%
[2021-03-21.12:01:21] [Info] 80.0%
[2021-03-21.12:01:21] [Info] 90.0%
[2021-03-21.12:01:21] [Info] 100.0%
[2021-03-21.12:01:21] [Info] Done
[2021-03-21.12:01:22] [Info] Loading addresses from 'C:/Users/pc/Desktop/1.txt'
[2021-03-21.12:01:22] [Info] 105 addresses loaded (0.0MB)
[2021-03-21.12:01:22] [Info] Allocating bloom filter (0.0MB)
[2021-03-21.12:01:22] [Info] Error: misaligned address
Execution time = 12 seconds

[sp_]

#2 released

Added support for compute 5.0 and compute 7.5
~20% faster generation of starting points
~1% kernel speedup

https://github.com/sp-hash/Bitcrack/releases/

[fxsniper]

#2 released

Added support for compute 5.0 and compute 7.5
~20% faster generation of starting points
~1% kernel speedup

https://github.com/sp-hash/Bitcrack/releases/

Thank you

this version 2 work better

generating point still feel slow than normal version (but ok when compare generating )
normal Generating 262,144 starting points (10.0MB)
modify  Generating 20,971,520 starting points (800.0MB)

I don't know use technic method generate more memory and calculate large size same time

but memory use better #1
first modify can run only 1 bitcrack only, program use all memory if open more will found out of memory
#2 modify can run with 1 normal bitcrack to tal 2 bitcrack may be optimize use memory enough to use more one 10mb point generate

[_Counselor]

Tesla V100 and Tesla P100 shows no difference between original and modified versions

What is the speed on the V100 and the P100, and what is the launch config?

V100 -b 80 -t 512 -p 2800  ~1575Mkey
P100 -b 112 -t 512 -p 2000  ~580Mkey

[sp_]

V100 -b 80 -t 512 -p 2800  ~1575Mkey
P100 -b 112 -t 512 -p 2000  ~580Mkey

try to run without the -b and -t parameter. My exe will autotune to a good launchconfig.

With sp-mod #2 I get

1070: 370 MKey
1070ti: 404Mkey
1080ti: 600Mkey
Titanx pascal: 560Mkey

[fxsniper]

V100 -b 80 -t 512 -p 2800  ~1575Mkey
P100 -b 112 -t 512 -p 2000  ~580Mkey

try to run without the -b and -t parameter. My exe will autotune to a good launchconfig.

With sp-mod #2 I get

1070: 370 MKey
1070ti: 404Mkey
1080ti: 600Mkey
Titanx pascal: 560Mkey

my 1050: 11-50 Mkey  just a little toy

but I think  make it faster is not answer puzzle challenge
make it fast 10Gigkey still use million year to scan
puzzle need algorithm to calculate
but make it faster is good to prepare for next algorithm

[Markzuberg64]

Is it possible to use this modified version to write all generated keypairs to some file rather than to compare. Or any fast method to write keypairs pvk:pubkey . I had read on different posts that its possible to generate 15 billion of keypairs in under a minute. Is it true ? If yes then is this jut generation or writing to disk is also possible at this speed.

[WanderingPhilospher]

Is it possible to use this modified version to write all generated keypairs to some file rather than to compare. Or any fast method to write keypairs pvk:pubkey . I had read on different posts that its possible to generate 15 billion of keypairs in under a minute. Is it true ? If yes then is this jut generation or writing to disk is also possible at this speed.

Generation/compare is easy at 15 billion in under a minute; it's the writing to disk that is unachievable at that speed, unless you have a high core count CPU. And even then, I don't know if you could write 15 billion keypairs in under a minute.

[Markzuberg64]

Hi guys ,

Can this tool or any modification of this be modified to write all private keys and respective uncompressed private keys and addresses) in range 1 to 56BC75E2D630FFFFF as a csv file . Since it generates 700 to xxxx million keys /s in some of its versions , so it will take many years on a single machine. But still looking for solutions. Writing regular outputs will consume too much time
So better it will save several millions or billions in some sort of memory operation and then write them once ,  till then next batch will find its space in memory to be written again.

If I understand you correctly, you are saying that Bitcrack should write the address of each private key it finds to a file?

How would that speed up key searching? Bitcrack doesn't even encode addresses anyway (it only decodes them to RIPEMD160 hash at the beginning of a search) so modifying it to make an address out of every address it finds will slow it down.

No sir , this question is not related to bitcrack real use  of key searching and i am looking to write sequential keypairs to file and not addresses , i.e. K and k*G . I saw that vanitygen and bitcracks are fast enough , so i am looking for ways to use these for my purpose or suggestions are welcome if using fastecdsa or other libraries directly from a c program will be faster . I believe it wont be .