Topic: BitCrack - A tool for brute-forcing private keys - page 46. (Read 77647 times)

obvious i click on release not debug let me roll back my driver and try again.. if i can't please share your compiled cubitcrack with me i am very exited to know this will work in 30 series or not..

download in progress...
 

Did you compile it for release? Or debug?

@Zahid888, you need to install cuda 10.2. Doesnt matter if you have higher version, you need that exact version in order to compile. I can share my build but i'm against precompilled sources (you never know)

On V100 speed is drastically slower than normal:

Tesla V100-SXM2- 10809 / 16160MB | 1 target 224.55 MKey/s (6,422,528,000 total) [00:00:26]

I am always impressed with the rocket engineer level discussions in this thread and the puzzle one.
I know a large number of the puzzle ?wallets? have been cracked with this, correct? The prize is then able to be self claimed because with the private key, it would be the same as having the wallet.dat correct?

old one BitCrack-master compile error

G:\BitCrack-master\BitCrack-master\CudaKeySearchDevice\CudaKeySearchDevice.vcxproj(59,5): error MSB4019: The imported project "C:\Program Files (x86)\Microsoft Visual Studio\2019\Enterprise\MSBuild\Microsoft\VC\v160\BuildCustomizations\CUDA 10.1.props" was not found. Confirm that the expression in the Import declaration "C:\Program Files (x86)\Microsoft Visual Studio\2019\Enterprise\MSBuild\Microsoft\VC\v160\\BuildCustomizations\CUDA 10.1.props" is correct, and that the file exists on disk.

new one BitCrack-3000-master compile error

G:\BitCrack-3000-master\BitCrack-3000-master\CudaKeySearchDevice\CudaKeySearchDevice.vcxproj(59,5): error MSB4019: The imported project "C:\Program Files (x86)\Microsoft Visual Studio\2019\Enterprise\MSBuild\Microsoft\VC\v160\BuildCustomizations\CUDA 10.2.props" was not found. Confirm that the expression in the Import declaration "C:\Program Files (x86)\Microsoft Visual Studio\2019\Enterprise\MSBuild\Microsoft\VC\v160\\BuildCustomizations\CUDA 10.2.props" is correct, and that the file exists on disk.

what can i do 

Good to hear that speeds aren't abysmal on GeForce cards. Maybe it was because I used the default points/blocks/threads and never bothered turning them for my Tesla card.

old one BitCrack-master compile error

G:\BitCrack-master\BitCrack-master\CudaKeySearchDevice\CudaKeySearchDevice.vcxproj(59,5): error MSB4019: The imported project "C:\Program Files (x86)\Microsoft Visual Studio\2019\Enterprise\MSBuild\Microsoft\VC\v160\BuildCustomizations\CUDA 10.1.props" was not found. Confirm that the expression in the Import declaration "C:\Program Files (x86)\Microsoft Visual Studio\2019\Enterprise\MSBuild\Microsoft\VC\v160\\BuildCustomizations\CUDA 10.1.props" is correct, and that the file exists on disk.

new one BitCrack-3000-master compile error

G:\BitCrack-3000-master\BitCrack-3000-master\CudaKeySearchDevice\CudaKeySearchDevice.vcxproj(59,5): error MSB4019: The imported project "C:\Program Files (x86)\Microsoft Visual Studio\2019\Enterprise\MSBuild\Microsoft\VC\v160\BuildCustomizations\CUDA 10.2.props" was not found. Confirm that the expression in the Import declaration "C:\Program Files (x86)\Microsoft Visual Studio\2019\Enterprise\MSBuild\Microsoft\VC\v160\\BuildCustomizations\CUDA 10.2.props" is correct, and that the file exists on disk.

what can i do 

It is also possible to bring a AMD Radeon RX 6800 also to work good or do you prefer GTX with CUDA? I can get 8GB with GTX or 16GB with AMD for same price.

Will it also have an effect if i use another prozessor maybe with 18 cores?

Thank you for your optimizations, i tested it and from 610-615/MK now i have 700-720MK/s (impressive). RTX 2060

Also i found a bug in random mode (i will try to fix it and maybe do a PR to github, never codded in C/C++, other languages like C#/PHP)
The problem with random is that the keyspace ending is ignored and the keys will increase above the predefined range.

old one BitCrack-master compile error

G:\BitCrack-master\BitCrack-master\CudaKeySearchDevice\CudaKeySearchDevice.vcxproj(59,5): error MSB4019: The imported project "C:\Program Files (x86)\Microsoft Visual Studio\2019\Enterprise\MSBuild\Microsoft\VC\v160\BuildCustomizations\CUDA 10.1.props" was not found. Confirm that the expression in the Import declaration "C:\Program Files (x86)\Microsoft Visual Studio\2019\Enterprise\MSBuild\Microsoft\VC\v160\\BuildCustomizations\CUDA 10.1.props" is correct, and that the file exists on disk.

So it looks like that BitCrack hates any kind of cicc optimization and will immediately throw a misaligned address even on optimization level 1.

Ptxas optimization still works though, and setting it to the default level 3 triples the speed on my T4. Now before anyone gets excited about this, the speed still sucks compared to older cards (only 60MKeys/s now).  

Meanwhile I have pushed the updates to https://github.com/ZenulAbidin/BitCrack-3000

Go get 'em boys.

Excellent... Now I am waiting for such an important person. Who will come and compile it in the Windows version. I think someone must have done this work. I request him to share it with us. So that we can see different results and benchmarks..

So it looks like that BitCrack hates any kind of cicc optimization and will immediately throw a misaligned address even on optimization level 1.

Ptxas optimization still works though, and setting it to the default level 3 triples the speed on my T4. Now before anyone gets excited about this, the speed still sucks compared to older cards (only 60MKeys/s now).  

Meanwhile I have pushed the updates to https://github.com/ZenulAbidin/BitCrack-3000

Go get 'em boys.

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?

Is there any 3000 edition that works? i mean someone here has posted a result with gtx 3060 and 800mio keys/s.
i am not inside this forum since beginning i am here since 3 days.

Since we are in the Bitrack forum, I imagine you are wanting to use it.  Currently, the RTX 30xx cards are not supported with Bitcrack. The AMD cards do not perform well with the openCL version of bitcrack and you have to make sure you are using a version that actually finds the keys.

All things equal, and if it worked, the 3070 should get a little more MKey/s than a 2080Ti.

I think About buying an GTX 3070 do anybody know how many keys/s it can load? i have seen an answear with 1080 ti and 500mio keys/s will the 3070 find more maybe?

It is also possible to bring a AMD Radeon RX 6800 also to work good or do you prefer GTX with CUDA? I can get 8GB with GTX or 16GB with AMD for same price.

Will it also have an effect if i use another prozessor maybe with 18 cores?

Can you hack a wallet with a lot of bitcoins using this tool?