I'm getting 750 Mkey/s (...) but I'm also hearing a buzzing sound in my headphones while it is running. Is there any way to fix this issue (...)?
Unplug headphones.
Topic: BitCrack - A tool for brute-forcing private keys - page 76. (Read 74414 times)
Unplug headphones.
I'm getting 734.23 Mkey/s with these parameters -b 64 -t 512 -p 1024 but I'm also hearing a buzzing sound in my headphones while it is running. Is there any way to fix this issue or should I just try to run it on a cloud server or something? Also if someone has a different set of parameters that they think would be better I'm all ears.
Ok I figured out how to compile it in release mode by reading this https://stackoverflow.com/questions/933739/what-is-the-difference-between-release-and-debug-modes-in-visual-studio. Now I am getting approximately 720 Mkey/s 
It is running at 73 Celsius now when it was only 60 Celsius before. I'm using these parameters -d 0 -b 64 -t 512 -p 1024. Are these parameters optimal or no and also can someone explain what that d does and do I even need it? And one more question can I install the 446.14 graphics update in GeForce Experience or does that not support the 10.1 toolkit?
It is running at 73 Celsius now when it was only 60 Celsius before. I'm using these parameters -d 0 -b 64 -t 512 -p 1024. Are these parameters optimal or no and also can someone explain what that d does and do I even need it? And one more question can I install the 446.14 graphics update in GeForce Experience or does that not support the 10.1 toolkit?
If you don't know what's release mode, you probably don't know how to compile ...
It looks like this has been talked about before but what does he mean by building it in release mode? https://github.com/brichard19/BitCrack/issues/142. Here is someone trying to explain it but it still doesn't make much sense to me. https://stackoverflow.com/questions/46979464/unable-to-build-in-release-mode-in-visual-studio. Can you explain it in simpler terms for me?
Now I'm only getting 8.5 with that one you just showed me 
So do you think maybe it's because I'm using CUDA v11.0? My GPU runs at 100% load so I'm sure that it's not a problem with energy draw.
I don't know all the code you changed...here's one way to check real quick. Go download the latest compiled version and run it instead of your compiled cuda 11 version. See what kind of Mkey/s you get. So do you think maybe it's because I'm using CUDA v11.0? My GPU runs at 100% load so I'm sure that it's not a problem with energy draw.So I tried this and now I get this error code when trying to build the file. I have tried reinstalling the Toolkit and Visual studio a couple of times and I just can't seem to get back the CUDA props and targets files that should be in the Visual Studio folder. So other than just completely uninstalling everything and trying over is there anything else that I can try?
Severity Code Description Project File Line Suppression State
Error MSB4019 The imported project "C:\Program Files (x86)\Microsoft Visual Studio\2019\Community\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\Community\MSBuild\Microsoft\VC\v160\\BuildCustomizations\CUDA 10.1.props" is correct, and that the file exists on disk. cuKeyFinder C:\Users\bieni\Downloads\BitCrack-master\CudaKeySearchDevice\CudaKeySearchDevice.vcxproj 59
Yeah that cuda props is ugly. If you don't have it on your computer yet, you will have to download and place it in that folder where it says its not.
some helpful links:
https://cudaeducation.com/cudatargetsnotfound/
https://developer.nvidia.com/cuda-10.1-download-archive-update2
Thanks so much for your help man! I installed from that link that you gave me and also found this link that explains how to do it manually https://stackoverflow.com/questions/12136808/cuda-4-2-props-and-target-file-is-missing-visual-studio-2010. So I have the program up and running again. Only problem now is that it is still running at 8 Mkey/s. I used those parameters that you had suggested above. So is there anything else I could try to get this running faster?
Now I'm only getting 8.5 with that one you just showed me So do you think maybe it's because I'm using CUDA v11.0? My GPU runs at 100% load so I'm sure that it's not a problem with energy draw.
I don't know all the code you changed...here's one way to check real quick. Go download the latest compiled version and run it instead of your compiled cuda 11 version. See what kind of Mkey/s you get. So do you think maybe it's because I'm using CUDA v11.0? My GPU runs at 100% load so I'm sure that it's not a problem with energy draw.So I tried this and now I get this error code when trying to build the file. I have tried reinstalling the Toolkit and Visual studio a couple of times and I just can't seem to get back the CUDA props and targets files that should be in the Visual Studio folder. So other than just completely uninstalling everything and trying over is there anything else that I can try?
Severity Code Description Project File Line Suppression State
Error MSB4019 The imported project "C:\Program Files (x86)\Microsoft Visual Studio\2019\Community\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\Community\MSBuild\Microsoft\VC\v160\\BuildCustomizations\CUDA 10.1.props" is correct, and that the file exists on disk. cuKeyFinder C:\Users\bieni\Downloads\BitCrack-master\CudaKeySearchDevice\CudaKeySearchDevice.vcxproj 59
Yeah that cuda props is ugly. If you don't have it on your computer yet, you will have to download and place it in that folder where it says its not.
some helpful links:
https://cudaeducation.com/cudatargetsnotfound/
https://developer.nvidia.com/cuda-10.1-download-archive-update2
Now I'm only getting 8.5 with that one you just showed me So do you think maybe it's because I'm using CUDA v11.0? My GPU runs at 100% load so I'm sure that it's not a problem with energy draw.
I don't know all the code you changed...here's one way to check real quick. Go download the latest compiled version and run it instead of your compiled cuda 11 version. See what kind of Mkey/s you get. So do you think maybe it's because I'm using CUDA v11.0? My GPU runs at 100% load so I'm sure that it's not a problem with energy draw.So I tried this and now I get this error code when trying to build the file. I have tried reinstalling the Toolkit and Visual studio a couple of times and I just can't seem to get back the CUDA props and targets files that should be in the Visual Studio folder. So other than just completely uninstalling everything and trying over is there anything else that I can try?
Severity Code Description Project File Line Suppression State
Error MSB4019 The imported project "C:\Program Files (x86)\Microsoft Visual Studio\2019\Community\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\Community\MSBuild\Microsoft\VC\v160\\BuildCustomizations\CUDA 10.1.props" is correct, and that the file exists on disk. cuKeyFinder C:\Users\bieni\Downloads\BitCrack-master\CudaKeySearchDevice\CudaKeySearchDevice.vcxproj 59
How to run bitcrack for work not with step ".......00000000000000000000001", but step ".........000000000000000000000003" ?
Br.
Br.
--stride 3
How to run bitcrack for work not with step ".......00000000000000000000001", but step ".........000000000000000000000003" ?
Br.
Br.
I tried using BitCrack with CUDA v11.0 and it works if I modify some of the files. I'm only getting around 14 Mkey/s though. Is this because I am not using CUDA v10.1? Also, what would be the optimal parameters for an RTX 2070 GPU?
14?? What are your current -b -t -p settings? You'll have to play with the numbers but try something like -b 64 -t 128 -p 256 to start. You'll have to play with those numbers but any of the RTX20xx should be getting at least 700 Mkey/s, except for the 2080Ti, it's up there around 1300-1500 (depending on what you read).+-350MK on 1080Ti - anything to improve? 112/512/768
Share please link to offline version of bitcrack ?
Thx !
Thx !
I tried using BitCrack with CUDA v11.0 and it works if I modify some of the files. I'm only getting around 14 Mkey/s though. Is this because I am not using CUDA v10.1? Also, what would be the optimal parameters for an RTX 2070 GPU?
14?? What are your current -b -t -p settings? You'll have to play with the numbers but try something like -b 64 -t 128 -p 256 to start. You'll have to play with those numbers but any of the RTX20xx should be getting at least 700 Mkey/s, except for the 2080Ti, it's up there around 1300-1500 (depending on what you read).+-350MK on 1080Ti - anything to improve? 112/512/768
Now I'm only getting 8.5 with that one you just showed me So do you think maybe it's because I'm using CUDA v11.0? My GPU runs at 100% load so I'm sure that it's not a problem with energy draw.
I don't know all the code you changed...here's one way to check real quick. Go download the latest compiled version and run it instead of your compiled cuda 11 version. See what kind of Mkey/s you get. So do you think maybe it's because I'm using CUDA v11.0? My GPU runs at 100% load so I'm sure that it's not a problem with energy draw.
Now I'm only getting 8.5 with that one you just showed me So do you think maybe it's because I'm using CUDA v11.0? My GPU runs at 100% load so I'm sure that it's not a problem with energy draw.
So do you think maybe it's because I'm using CUDA v11.0? My GPU runs at 100% load so I'm sure that it's not a problem with energy draw. I tried using BitCrack with CUDA v11.0 and it works if I modify some of the files. I'm only getting around 14 Mkey/s though. Is this because I am not using CUDA v10.1? Also, what would be the optimal parameters for an RTX 2070 GPU?
14?? What are your current -b -t -p settings? You'll have to play with the numbers but try something like -b 64 -t 128 -p 256 to start. You'll have to play with those numbers but any of the RTX20xx should be getting at least 700 Mkey/s, except for the 2080Ti, it's up there around 1300-1500 (depending on what you read).
I tried using BitCrack with CUDA v11.0 and it works if I modify some of the files. I'm only getting around 14 Mkey/s though. Is this because I am not using CUDA v10.1? Also, what would be the optimal parameters for an RTX 2070 GPU?
Every time I use keyspace for specific range bitcrack always show staring 483481624912735df1212313C96A3742F6490623432523847279273198
& ending 483481624912739df1212313C96A3742F6490623432523847279273198.
Also how to use --continue
Why its not start from my chosen range, anyone have idea.
& ending 483481624912739df1212313C96A3742F6490623432523847279273198.
Also how to use --continue
Why its not start from my chosen range, anyone have idea.
There is no such range.
What address is the range for?
000000483481624912735df1212313C96A3742F6490623432523847279273198
Any solution.
Also how to use --continue so I dont have to start evry tim from beginning.
your keyspace command should look like this:
Code:
--keyspace edd2dc711a85146c:edd2dc711a95146b
replace with your start and end range.I also explained the --continue option, did you read or not understand?
Also, are you using cuBitcrack or clBitcrack? the clBitcrack has known bugs.
I am using cuBitcrack.
Is there any way to increase speed, bitcrack wont use even 1% from cpu & 0% from gpu.
Can someone throw off the working version of pikachunakapika / bitcrack??? I searched the Internet and cannot find anywhere. need a random function. on https://github.com/ deleted. Please friends help.
Your best bet is to create a batch file that does the random for you. The random function in the version you are speaking about is slower because it takes more time to regen the randomness than to just go in sequential order. A batch function lets you jump in and out of ranges randomly. I have python script that writes batch script with random ranges. You can select the low and high of the range for example:Low: 8B00000
High: 8BFFFFF
So the script will randomly generate a start and end range inside of that range. Or, use the --share option for "randomness"
Share the script. Itself could not write as it should.
Here is the python script (I run python 2.7 on Windows):
Code:
# Randomizer for BitCrack
# Amateur Coding by the Wandering Philosopher
import os
import random
from datetime import datetime
random.seed(datetime.now())
arq1 = open('RandomBitCrack.bat', 'w')
y = ("FFFFF")
Y1 = int(y, 16)
arq1.write(":while1" + '\n')
for x in range(20):
low = 0x000000000000000000000000000000000000000000000000ED00000000000000
high = 0x000000000000000000000000000000000000000000000000EDFFFFFFFFFFFFFF
blah1 = random.randrange(low, high)
blah = str( hex( random.randrange( low, high ) ) ).rstrip("L").replace("0x", "00000000000000000000000000000000000000000000000")
eazy = hex(blah1 + Y1).rstrip("L").lstrip("0x")
arq1.write("start cb1 -d 1 -b 64 -t 256 -p 256 --keyspace " + hex(blah1).rstrip("L").lstrip("0x") +":" + eazy + " -i 64.txt -o FOUNDTHEPRIVATEKEY.txt" + '\n' + "timeout /t 6 /nobreak" + '\n' + "taskkill /im cb1.exe /f" + '\n' + "timeout /t 1 /nobreak" + '\n')
arq1.close()
# Amateur Coding by the Wandering Philosopher
import os
import random
from datetime import datetime
random.seed(datetime.now())
arq1 = open('RandomBitCrack.bat', 'w')
y = ("FFFFF")
Y1 = int(y, 16)
arq1.write(":while1" + '\n')
for x in range(20):
low = 0x000000000000000000000000000000000000000000000000ED00000000000000
high = 0x000000000000000000000000000000000000000000000000EDFFFFFFFFFFFFFF
blah1 = random.randrange(low, high)
blah = str( hex( random.randrange( low, high ) ) ).rstrip("L").replace("0x", "00000000000000000000000000000000000000000000000")
eazy = hex(blah1 + Y1).rstrip("L").lstrip("0x")
arq1.write("start cb1 -d 1 -b 64 -t 256 -p 256 --keyspace " + hex(blah1).rstrip("L").lstrip("0x") +":" + eazy + " -i 64.txt -o FOUNDTHEPRIVATEKEY.txt" + '\n' + "timeout /t 6 /nobreak" + '\n' + "taskkill /im cb1.exe /f" + '\n' + "timeout /t 1 /nobreak" + '\n')
arq1.close()
Batch file produced:
Code:
:while1
start cb1 -d 1 -b 64 -t 256 -p 256 --keyspace ed5f9f957a417cae:ed5f9f957a517cad -i 64.txt -o FOUNDTHEPRIVATEKEY.txt
timeout /t 6 /nobreak
taskkill /im cb1.exe /f
timeout /t 1 /nobreak
start cb1 -d 1 -b 64 -t 256 -p 256 --keyspace ed5ce1cdf696c89f:ed5ce1cdf6a6c89e -i 64.txt -o FOUNDTHEPRIVATEKEY.txt
timeout /t 6 /nobreak
taskkill /im cb1.exe /f
timeout /t 1 /nobreak
start cb1 -d 1 -b 64 -t 256 -p 256 --keyspace ede87bf0498ffc93:ede87bf0499ffc92 -i 64.txt -o FOUNDTHEPRIVATEKEY.txt
timeout /t 6 /nobreak
taskkill /im cb1.exe /f
timeout /t 1 /nobreak
start cb1 -d 1 -b 64 -t 256 -p 256 --keyspace ed4482d8f1e25b9e:ed4482d8f1f25b9d -i 64.txt -o FOUNDTHEPRIVATEKEY.txt
timeout /t 6 /nobreak
taskkill /im cb1.exe /f
timeout /t 1 /nobreak
start cb1 -d 1 -b 64 -t 256 -p 256 --keyspace edbd36f37234898c:edbd36f37244898b -i 64.txt -o FOUNDTHEPRIVATEKEY.txt
timeout /t 6 /nobreak
taskkill /im cb1.exe /f
timeout /t 1 /nobreak
start cb1 -d 1 -b 64 -t 256 -p 256 --keyspace ed8511d049941d6f:ed8511d049a41d6e -i 64.txt -o FOUNDTHEPRIVATEKEY.txt
timeout /t 6 /nobreak
taskkill /im cb1.exe /f
timeout /t 1 /nobreak
start cb1 -d 1 -b 64 -t 256 -p 256 --keyspace ed5f9b5cd289b8ef:ed5f9b5cd299b8ee -i 64.txt -o FOUNDTHEPRIVATEKEY.txt
timeout /t 6 /nobreak
taskkill /im cb1.exe /f
timeout /t 1 /nobreak
start cb1 -d 1 -b 64 -t 256 -p 256 --keyspace ed8a07e85d77b716:ed8a07e85d87b715 -i 64.txt -o FOUNDTHEPRIVATEKEY.txt
timeout /t 6 /nobreak
taskkill /im cb1.exe /f
timeout /t 1 /nobreak
start cb1 -d 1 -b 64 -t 256 -p 256 --keyspace ed91263ac5f6d2ca:ed91263ac606d2c9 -i 64.txt -o FOUNDTHEPRIVATEKEY.txt
timeout /t 6 /nobreak
taskkill /im cb1.exe /f
timeout /t 1 /nobreak
start cb1 -d 1 -b 64 -t 256 -p 256 --keyspace ed1d4a9023dd6bfb:ed1d4a9023ed6bfa -i 64.txt -o FOUNDTHEPRIVATEKEY.txt
timeout /t 6 /nobreak
taskkill /im cb1.exe /f
timeout /t 1 /nobreak
start cb1 -d 1 -b 64 -t 256 -p 256 --keyspace ed72d72cee1da3ca:ed72d72cee2da3c9 -i 64.txt -o FOUNDTHEPRIVATEKEY.txt
timeout /t 6 /nobreak
taskkill /im cb1.exe /f
timeout /t 1 /nobreak
start cb1 -d 1 -b 64 -t 256 -p 256 --keyspace ed1b50d6fc437042:ed1b50d6fc537041 -i 64.txt -o FOUNDTHEPRIVATEKEY.txt
timeout /t 6 /nobreak
taskkill /im cb1.exe /f
timeout /t 1 /nobreak
start cb1 -d 1 -b 64 -t 256 -p 256 --keyspace ed71ac3573476040:ed71ac357357603f -i 64.txt -o FOUNDTHEPRIVATEKEY.txt
timeout /t 6 /nobreak
taskkill /im cb1.exe /f
timeout /t 1 /nobreak
start cb1 -d 1 -b 64 -t 256 -p 256 --keyspace ed2ac546cac9806e:ed2ac546cad9806d -i 64.txt -o FOUNDTHEPRIVATEKEY.txt
timeout /t 6 /nobreak
taskkill /im cb1.exe /f
timeout /t 1 /nobreak
start cb1 -d 1 -b 64 -t 256 -p 256 --keyspace eddf6d5744433345:eddf6d5744533344 -i 64.txt -o FOUNDTHEPRIVATEKEY.txt
timeout /t 6 /nobreak
taskkill /im cb1.exe /f
timeout /t 1 /nobreak
start cb1 -d 1 -b 64 -t 256 -p 256 --keyspace edb5ca5f89c2c400:edb5ca5f89d2c3ff -i 64.txt -o FOUNDTHEPRIVATEKEY.txt
timeout /t 6 /nobreak
taskkill /im cb1.exe /f
timeout /t 1 /nobreak
start cb1 -d 1 -b 64 -t 256 -p 256 --keyspace edbaa4935a4fda3e:edbaa4935a5fda3d -i 64.txt -o FOUNDTHEPRIVATEKEY.txt
timeout /t 6 /nobreak
taskkill /im cb1.exe /f
timeout /t 1 /nobreak
start cb1 -d 1 -b 64 -t 256 -p 256 --keyspace edbe2cbe32f92f56:edbe2cbe33092f55 -i 64.txt -o FOUNDTHEPRIVATEKEY.txt
timeout /t 6 /nobreak
taskkill /im cb1.exe /f
timeout /t 1 /nobreak
start cb1 -d 1 -b 64 -t 256 -p 256 --keyspace ede9ad4e751e6975:ede9ad4e752e6974 -i 64.txt -o FOUNDTHEPRIVATEKEY.txt
timeout /t 6 /nobreak
taskkill /im cb1.exe /f
timeout /t 1 /nobreak
start cb1 -d 1 -b 64 -t 256 -p 256 --keyspace ed7484d8f9fb1ee7:ed7484d8fa0b1ee6 -i 64.txt -o FOUNDTHEPRIVATEKEY.txt
timeout /t 6 /nobreak
taskkill /im cb1.exe /f
timeout /t 1 /nobreak
start cb1 -d 1 -b 64 -t 256 -p 256 --keyspace ed5f9f957a417cae:ed5f9f957a517cad -i 64.txt -o FOUNDTHEPRIVATEKEY.txt
timeout /t 6 /nobreak
taskkill /im cb1.exe /f
timeout /t 1 /nobreak
start cb1 -d 1 -b 64 -t 256 -p 256 --keyspace ed5ce1cdf696c89f:ed5ce1cdf6a6c89e -i 64.txt -o FOUNDTHEPRIVATEKEY.txt
timeout /t 6 /nobreak
taskkill /im cb1.exe /f
timeout /t 1 /nobreak
start cb1 -d 1 -b 64 -t 256 -p 256 --keyspace ede87bf0498ffc93:ede87bf0499ffc92 -i 64.txt -o FOUNDTHEPRIVATEKEY.txt
timeout /t 6 /nobreak
taskkill /im cb1.exe /f
timeout /t 1 /nobreak
start cb1 -d 1 -b 64 -t 256 -p 256 --keyspace ed4482d8f1e25b9e:ed4482d8f1f25b9d -i 64.txt -o FOUNDTHEPRIVATEKEY.txt
timeout /t 6 /nobreak
taskkill /im cb1.exe /f
timeout /t 1 /nobreak
start cb1 -d 1 -b 64 -t 256 -p 256 --keyspace edbd36f37234898c:edbd36f37244898b -i 64.txt -o FOUNDTHEPRIVATEKEY.txt
timeout /t 6 /nobreak
taskkill /im cb1.exe /f
timeout /t 1 /nobreak
start cb1 -d 1 -b 64 -t 256 -p 256 --keyspace ed8511d049941d6f:ed8511d049a41d6e -i 64.txt -o FOUNDTHEPRIVATEKEY.txt
timeout /t 6 /nobreak
taskkill /im cb1.exe /f
timeout /t 1 /nobreak
start cb1 -d 1 -b 64 -t 256 -p 256 --keyspace ed5f9b5cd289b8ef:ed5f9b5cd299b8ee -i 64.txt -o FOUNDTHEPRIVATEKEY.txt
timeout /t 6 /nobreak
taskkill /im cb1.exe /f
timeout /t 1 /nobreak
start cb1 -d 1 -b 64 -t 256 -p 256 --keyspace ed8a07e85d77b716:ed8a07e85d87b715 -i 64.txt -o FOUNDTHEPRIVATEKEY.txt
timeout /t 6 /nobreak
taskkill /im cb1.exe /f
timeout /t 1 /nobreak
start cb1 -d 1 -b 64 -t 256 -p 256 --keyspace ed91263ac5f6d2ca:ed91263ac606d2c9 -i 64.txt -o FOUNDTHEPRIVATEKEY.txt
timeout /t 6 /nobreak
taskkill /im cb1.exe /f
timeout /t 1 /nobreak
start cb1 -d 1 -b 64 -t 256 -p 256 --keyspace ed1d4a9023dd6bfb:ed1d4a9023ed6bfa -i 64.txt -o FOUNDTHEPRIVATEKEY.txt
timeout /t 6 /nobreak
taskkill /im cb1.exe /f
timeout /t 1 /nobreak
start cb1 -d 1 -b 64 -t 256 -p 256 --keyspace ed72d72cee1da3ca:ed72d72cee2da3c9 -i 64.txt -o FOUNDTHEPRIVATEKEY.txt
timeout /t 6 /nobreak
taskkill /im cb1.exe /f
timeout /t 1 /nobreak
start cb1 -d 1 -b 64 -t 256 -p 256 --keyspace ed1b50d6fc437042:ed1b50d6fc537041 -i 64.txt -o FOUNDTHEPRIVATEKEY.txt
timeout /t 6 /nobreak
taskkill /im cb1.exe /f
timeout /t 1 /nobreak
start cb1 -d 1 -b 64 -t 256 -p 256 --keyspace ed71ac3573476040:ed71ac357357603f -i 64.txt -o FOUNDTHEPRIVATEKEY.txt
timeout /t 6 /nobreak
taskkill /im cb1.exe /f
timeout /t 1 /nobreak
start cb1 -d 1 -b 64 -t 256 -p 256 --keyspace ed2ac546cac9806e:ed2ac546cad9806d -i 64.txt -o FOUNDTHEPRIVATEKEY.txt
timeout /t 6 /nobreak
taskkill /im cb1.exe /f
timeout /t 1 /nobreak
start cb1 -d 1 -b 64 -t 256 -p 256 --keyspace eddf6d5744433345:eddf6d5744533344 -i 64.txt -o FOUNDTHEPRIVATEKEY.txt
timeout /t 6 /nobreak
taskkill /im cb1.exe /f
timeout /t 1 /nobreak
start cb1 -d 1 -b 64 -t 256 -p 256 --keyspace edb5ca5f89c2c400:edb5ca5f89d2c3ff -i 64.txt -o FOUNDTHEPRIVATEKEY.txt
timeout /t 6 /nobreak
taskkill /im cb1.exe /f
timeout /t 1 /nobreak
start cb1 -d 1 -b 64 -t 256 -p 256 --keyspace edbaa4935a4fda3e:edbaa4935a5fda3d -i 64.txt -o FOUNDTHEPRIVATEKEY.txt
timeout /t 6 /nobreak
taskkill /im cb1.exe /f
timeout /t 1 /nobreak
start cb1 -d 1 -b 64 -t 256 -p 256 --keyspace edbe2cbe32f92f56:edbe2cbe33092f55 -i 64.txt -o FOUNDTHEPRIVATEKEY.txt
timeout /t 6 /nobreak
taskkill /im cb1.exe /f
timeout /t 1 /nobreak
start cb1 -d 1 -b 64 -t 256 -p 256 --keyspace ede9ad4e751e6975:ede9ad4e752e6974 -i 64.txt -o FOUNDTHEPRIVATEKEY.txt
timeout /t 6 /nobreak
taskkill /im cb1.exe /f
timeout /t 1 /nobreak
start cb1 -d 1 -b 64 -t 256 -p 256 --keyspace ed7484d8f9fb1ee7:ed7484d8fa0b1ee6 -i 64.txt -o FOUNDTHEPRIVATEKEY.txt
timeout /t 6 /nobreak
taskkill /im cb1.exe /f
timeout /t 1 /nobreak
If you want to produce more than 20 random ranges, adjust the "for x in range(20):" in the code for however many you want. I normally run 1000.
If your bitcrack .exe file is named something else (which it probably is) change the "cb1" in both spots to the name of your bitcrack .exe file.
If your device number is something different, change it from -d 1 to whatever yours is, example -d 0.
You can adjust the time the script runs in each range by changing the "timeout /t 6 /nobreak" example, if you want each range to be searched for 60 seconds, change it to "timeout /t 60 /nobreak".
If you want to have different gpu settings other than "-b 64 -t 256 -p 256" adjust them.
If your input file is named something else besides "64.txt" change it to whatever your input file is (input file of what addresses you are searching for).
If you want your output file to be something other than "FOUNDTHEPRIVATEKEY.txt" change it to your desired output name.
Once you've made any changes, run the python script and it will automatically generate the batch file. Place the batch file inside your bitcrack folder, with the bitcrack.exe file, and your input file, and let it rip.
It's nothing fancy, just a low down and dirty python script that allows me to search random ranges without modifying/hacking the code inside bitcrack code and slowing it down any.
Edit: one last thing, I have it set up to randomly generate a range of "FFFFF", change that if you want a larger or smaller range. Change the "y = ("FFFFF")" option. I chose that range b/c my GPU can get through that range within the 6 seconds.
Can someone throw off the working version of pikachunakapika / bitcrack??? I searched the Internet and cannot find anywhere. need a random function. on https://github.com/ deleted. Please friends help.
Your best bet is to create a batch file that does the random for you. The random function in the version you are speaking about is slower because it takes more time to regen the randomness than to just go in sequential order. A batch function lets you jump in and out of ranges randomly. I have python script that writes batch script with random ranges. You can select the low and high of the range for example:Low: 8B00000
High: 8BFFFFF
So the script will randomly generate a start and end range inside of that range. Or, use the --share option for "randomness"
Share the script. Itself could not write as it should.
Jump to: