BitCrack - A tool for brute-forcing private keys

[WanderingPhilospher]

Please update when yours can run multi gpu and 30xx cards.

I have ordered new cards.  Will get them next month..

Good deal...the more important issue is to tackle multi gpu use. It makes it so much easier versus multiple instances.

[filo1992]

Hi, you made some great changes on the cuda version, I get about 220 Mk / s on gtx 970.

would you be able to improve and repair the opencl version too?

Another +10%

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

gtx 1070 375Mkeys
gtx 1070ti 445Mkeys
gtx 1080 480Mkeys
gtx 1080ti 650Mkeys
gtx titanx 610Mkeys

[Robert_BIT]

I have sent you the file to test, but nobody has reported the speed yet. #2 Should work on the gtx 750ti from 2014 and newer nvidia gpu's

 

Thanks for releasing this. On Tesla V100 it shows around 1100 Mkey with your sp-mod #3. Huge difference vs. the initial release.  

[WanderingPhilospher]

I have sent you the file to test, but nobody has reported the speed yet. #2 Should work on the gtx 750ti from 2014 and newer nvidia gpu's

 

Thanks for releasing this. On Tesla V100 it shows around 1100 Mkey with your sp-mod #3. Huge difference vs. the initial release.  

Not just you but for others as well; it is one thing to talk about the speed shown. How many have actually compared the two actually going through say a 40 bit range and finding a known key?

The shown speed means nothing, anyone can easily tweak code to show and increase, but how fast does it get through a range?

For those of you testing sp's new release(s), show comparison test, not just speed.

1100 MKey/s for a V100 seems slow. I get more than that with a 2080 (non Ti) with a different program. 

[renedx]

Care to share the source code? I’m really wondering what’ve been missing all this time.

[fxsniper]

Another +10%

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

gtx 1070 375Mkeys
gtx 1070ti 445Mkeys
gtx 1080 480Mkeys
gtx 1080ti 650Mkeys
gtx titanx 610Mkeys

cuBitCrack.exe -d 0 -b 20 -t 256 --keyspace 8000000000000000:+1000000000000000 16jY7qLJnxb7CHZyqBP8qca9d51gAjyXQN

laptop
GeForce GTX 1050 1436 / 4096MB | 1 target 81.70 MKey/s (3,342,336,000 total) [00:00:38]
GeForce GTX 1050 1436 / 4096MB | 1 target 83.18 MKey/s (5,827,461,120 total) [00:01:08]

[NotATether]

For those of you testing sp's new release(s), show comparison test, not just speed.

How would that work though? By posting a bunch of speeds reported from different programs, you're still relying on taking their speed at face value.

To see whether sp_ really did speed up the program and not simply multiplying the counter by 4 or 5, we must test it with a small range, such as 0 to 5 billion, which we can expect to finish in about 5 seconds on the regular Bitcrack on some GPU that does 1000MKeys/s.

If the mods are genuine then it will finish in about a second (again, I can't do this myself because no source code => no way to compile on Linux aaaaargh  )

[WanderingPhilospher]

For those of you testing sp's new release(s), show comparison test, not just speed.

How would that work though? By posting a bunch of speeds reported from different programs, you're still relying on taking their speed at face value.

Actually pretty easy. Set up a 32 bit (or 36 bit, or whatever your GPU can get through within 5 to 10 minutes) range/keyspace with 3 keys. One up front, one in middle, one at end.

Run sp's and then run original, with same exact settings.  Make sure to pause (pause at end of batch script for Windows) each program once it is done. Compare the times and see if both programs found all 3 keys.

[sp_]

1100 MKey/s for a V100 seems slow. I get more than that with a 2080 (non Ti) with a different program.  

What program? Is is a bitcrack solver?

[sp_]

would you be able to improve and repair the opencl version too?

I believe the opencl bug has been solved

https://github.com/BoGnY/BitCrack/commit/786ea3615a9b4dabae8f399e5db5daca0521e3fd

Build his github and you will be fine.

[sp_]

cuBitCrack.exe -d 0 -b 20 -t 256 --keyspace 8000000000000000:+1000000000000000 16jY7qLJnxb7CHZyqBP8qca9d51gAjyXQN
laptop
GeForce GTX 1050 1436 / 4096MB | 1 target 83.18 MKey/s (5,827,461,120 total) [00:01:08]

Try to run without the -b and -t parameter, the defaults has been improved in #3.

[sp_]

If the mods are genuine then it will finish in about a second (again, I can't do this myself because no source code => no way to compile on Linux aaaaargh  )

I have been a gpu miner dev since 2013 (with 1000 or more opensource commits to github in the ccminer project). All the optimizations in this mod are real, and I didn't change the algorithm so it's pure teqnique. With more work I can make it faster, but there is no money to be earned so I will probobly return to miner development. Check out my vertcoin miner with 1% fee. Vertcoin is halving in 2021, the price is low. Listed on bittrex.
Profitable to mine on old hardware with the sp-mod...

[fxsniper]

cuBitCrack.exe -d 0 -b 20 -t 256 --keyspace 8000000000000000:+1000000000000000 16jY7qLJnxb7CHZyqBP8qca9d51gAjyXQN
laptop
GeForce GTX 1050 1436 / 4096MB | 1 target 83.18 MKey/s (5,827,461,120 total) [00:01:08]

Try to run without the -b and -t parameter, the defaults has been improved in #3.

ok, here without use both -b and -t

cuBitCrack.exe -d 0 --keyspace 8000000000000000:+1000000000000000 16jY7qLJnxb7CHZyqBP8qca9d51gAjyXQN

GeForce GTX 1050 1436 / 4096MB | 1 target 81.03 MKey/s (1,942,487,040 total) [00:00:22]

[Twohundred]

Been following this thread for some time now.

Was running cuBitCrack on Windows with a Geforce GTX 1650 card. Using Nvidia 452.06 and Cuda 10.2.89. It did work and got around 49 Mkeys/s with cuBitCrack-0.32a 64/128/3200 settings and 634000 targets (compressed and uncompressed).
Don't recall how much on a single compressed target and don't want to take the computer apart just for that.

Bought yesterday an Asus RTX 3060 12 Gb. Off course the Nvidia 452.06 didn't work. Tried 457.30 as well with nil luck. Next step was 461.72 together with Cuda 11.2.2 and can confirm it does run with clBitCrack. However cuBitCrack doesn't work with current setup. At least not for me.

So at the moment I get 150 Mkeys/s on a Windows 10 Pro 64 (20H2), Nvidia 461.72 and Cuda 11.2.2 using clBitCrack (Yoydapros version v11.2-beta) settings 224/512/800 with 634000 targets (compressed and uncompressed). Its calculated to 91,750,400 starting points. If I try to push the slightest on any of the -b/-t/-p settings it gets an error.
Single compressed target gets 730 Mkeys/s with same settings.

I guess I should be happy getting three times the higher speed with the 3060 and running clBitCrack. Would like to try a working cuBitCrack to see if any difference. Does anybody know if there is a Cuda version BitCrack that works with RTX 3060 or higher?

[fxsniper]

Been following this thread for some time now.

Was running cuBitCrack on Windows with a Geforce GTX 1650 card. Using Nvidia 452.06 and Cuda 10.2.89. It did work and got around 49 Mkeys/s with cuBitCrack-0.32a 64/128/3200 settings and 634000 targets (compressed and uncompressed).
Don't recall how much on a single compressed target and don't want to take the computer apart just for that.

Bought yesterday an Asus RTX 3060 12 Gb. Off course the Nvidia 452.06 didn't work. Tried 457.30 as well with nil luck. Next step was 461.72 together with Cuda 11.2.2 and can confirm it does run with clBitCrack. However cuBitCrack doesn't work with current setup. At least not for me.

So at the moment I get 150 Mkeys/s on a Windows 10 Pro 64 (20H2), Nvidia 461.72 and Cuda 11.2.2 using clBitCrack (Yoydapros version v11.2-beta) settings 224/512/800 with 634000 targets (compressed and uncompressed). Its calculated to 91,750,400 starting points. If I try to push the slightest on any of the -b/-t/-p settings it gets an error.
Single compressed target gets 730 Mkeys/s with same settings.

I guess I should be happy getting three times the higher speed with the 3060 and running clBitCrack. Would like to try a working cuBitCrack to see if any difference. Does anybody know if there is a Cuda version BitCrack that works with RTX 3060 or higher?

Do you try this version already or not yet?

https://github.com/yoyodapro/BitCrack/releases/tag/v11.2-beta

[fxsniper]

Been following this thread for some time now.

Was running cuBitCrack on Windows with a Geforce GTX 1650 card. Using Nvidia 452.06 and Cuda 10.2.89. It did work and got around 49 Mkeys/s with cuBitCrack-0.32a 64/128/3200 settings and 634000 targets (compressed and uncompressed).
Don't recall how much on a single compressed target and don't want to take the computer apart just for that.

Bought yesterday an Asus RTX 3060 12 Gb. Off course the Nvidia 452.06 didn't work. Tried 457.30 as well with nil luck. Next step was 461.72 together with Cuda 11.2.2 and can confirm it does run with clBitCrack. However cuBitCrack doesn't work with current setup. At least not for me.

So at the moment I get 150 Mkeys/s on a Windows 10 Pro 64 (20H2), Nvidia 461.72 and Cuda 11.2.2 using clBitCrack (Yoydapros version v11.2-beta) settings 224/512/800 with 634000 targets (compressed and uncompressed). Its calculated to 91,750,400 starting points. If I try to push the slightest on any of the -b/-t/-p settings it gets an error.
Single compressed target gets 730 Mkeys/s with same settings.

I guess I should be happy getting three times the higher speed with the 3060 and running clBitCrack. Would like to try a working cuBitCrack to see if any difference. Does anybody know if there is a Cuda version BitCrack that works with RTX 3060 or higher?

Sorry I skip read line,  you try Yoydapros version already

still have issue with RTX 3060 and newest GPU
Waiting developer help to fix it

[NotATether]

If the mods are genuine then it will finish in about a second (again, I can't do this myself because no source code => no way to compile on Linux aaaaargh  )

I have been a gpu miner dev since 2013 (with 1000 or more opensource commits to github in the ccminer project). All the optimizations in this mod are real, and I didn't change the algorithm so it's pure teqnique. With more work I can make it faster, but there is no money to be earned so I will probobly return to miner development. Check out my vertcoin miner with 1% fee. Vertcoin is halving in 2021, the price is low. Listed on bittrex.
Profitable to mine on old hardware with the sp-mod...

OK but I don't understand why you're not releasing the code so that it can be run on Linux.

If (or when) you stop developing, all the optimizations will be lost because nobody else has the code to integrate them into some other fork!

[sp_]

OK but I don't understand why you're not releasing the code so that it can be run on Linux.
If (or when) you stop developing, all the optimizations will be lost because nobody else has the code to integrate them into some other fork!

Work in progress. Might release when I am happy with the results. In the next version I will include the ptx assembly code so it might work on compute 8.0 cards(rtx 3080, rtx 3060ti etc..) . sp-mod #3 only works for compressed keys, so #4 will include kernels for non compressed and both as well. Cuda 11.2 doesn't work on my dev machine. (windows 8.1) so I will try a bin with cuda 10.2 with ptx code included.

[zahid888]

Only way you’ll see me party a pool with my GPUs is when NotATether is the only, verified, owner. Based of the open and honesty he shares in the findings and improving CUDA, it’s a no-brainer he’s here to improve everyone.

Regarding the sp-mod, your V2 link has a Trojan in it per Win10 findings (conteban).
Your V1 doesn’t run on ampere. 3060, 3070, 3080 or 3090.

Nevertheless nice to see some activity on it again 
Very curious what the fix would be.

 

[zahid888]

Do you try this version already or not yet?

https://github.com/yoyodapro/BitCrack/releases/tag/v11.2-beta

[2021-03-24.17:11:47] [Info] Compression: compressed
[2021-03-24.17:11:47] [Info] Starting at: 0000000000000000000000000000000000000000000000008000000002CC9308
[2021-03-24.17:11:47] [Info] Ending at:   000000000000000000000000000000000000000000000000FFFFFFFFFFFFFFFF
[2021-03-24.17:11:47] [Info] Counting by: 0000000000000000000000000000000000000000000000000000000010000000
[2021-03-24.17:11:47] [Info] Compiling OpenCL kernels...
[2021-03-24.17:11:47] [Info] Initializing GeForce RTX 3060 Ti
[2021-03-24.17:11:49] [Info] Generating 33,554,432 starting points (1280.0MB)
[2021-03-24.17:11:51] [Info] 10.0%
[2021-03-24.17:11:52] [Info] 20.0%
[2021-03-24.17:11:52] [Info] 30.0%
[2021-03-24.17:11:52] [Info] 40.0%
[2021-03-24.17:11:52] [Info] 50.0%
[2021-03-24.17:11:53] [Info] 60.0%
[2021-03-24.17:11:53] [Info] 70.0%
[2021-03-24.17:11:53] [Info] 80.0%
[2021-03-24.17:11:53] [Info] 90.0%
[2021-03-24.17:11:53] [Info] 100.0%
[2021-03-24.17:11:53] [Info] Done
GeForce RTX 3060 3072 / 8192MB | 1 target 800.65 MKey/s (28,152,168,448 total) [00:00:32][2021-03-24.17:12:29] [Info] Address:     1LvaMg5NbndanhcCPADJnuzB5FyNhSCzcw
                             Private key: 0000000000000000000000000000000000000000000000008012507042CC9308 WRONG ACTUAL PVK IS EC12506982CC9308
                             Compressed:  yes
                             Public key:
                             0304F099DDA213CE96B9C1AC32A333AB796CC239D0F1258991C113D636A414F033

[2021-03-24.17:12:29] [Info] No targets remaining