UPDATE 2: Newest version, VBCr 2.0 has been released. Now works with full address and/or prefix/strings.
It has been tested on Windows 10 and Windows 11 on RTX 30xx cards, RTX 20xx cards and a GTX 1660 Ti card.
Link:
https://github.com/WanderingPhilosopher/VanBitCrackenRandom2SHA256 Checksum:
5415d56416632faa7058e1ddf2a6cde037d6df22778606128369df4557627dc3
Flags:
printf("VBCr [-check] [-v] [-u] [-b] [-c] [-gpu] [-stop] [-i inputfile]\n");
printf(" [-gpuId gpuId1[,gpuId2,...]] [-g g1x,g1y,[,g2x,g2y,...]]\n");
printf(" [-o outputfile] [-m maxFound] [-ps seed] [-s seed] [-t nbThread]\n");
printf(" [-bits bitsNumber] [-begr BeginRange] [-endr EndRange] [-dis Display Private Key] [-drk Display random keys] \n");
printf(" [-nosse] [-r rekey] [-check] [-kp] [-sp startPubKey] [-rp privkey partialkeyfile] [prefix]\n\n");
printf(" prefix: prefix to search (Can contain wildcard '?' or '*')\n");
printf(" -v: Print version\n");
printf(" -u: Search uncompressed addresses\n");
printf(" -b: Search both uncompressed or compressed addresses\n");
printf(" -c: Case unsensitive search\n");
printf(" -gpu: Enable gpu calculation\n");
printf(" -stop: Stop when all prefixes are found\n");
printf(" -i inputfile: Get list of prefixes to search from specified file\n");
printf(" -o outputfile: Output results to the specified file; Default is KeysFound.txt\n");
printf(" -gpu gpuId1,gpuId2,...: List of GPU(s) to use, default is 0\n");
printf(" -g g1x,g1y,g2x,g2y, ...: Specify GPU(s) kernel gridsize, default is 8*(MP number),128\n");
printf(" -m: Specify maximun number of prefixes found by each kernel call\n");
printf(" -s seed: Specify a seed for the base key, default is random\n");
printf(" -ps seed: Specify a seed concatened with a crypto secure random seed\n");
printf(" -t threadNumber: Specify number of CPU thread(s). Default is number of core(s)\n");
printf(" -bits bitsNumber: Specify bit length for private key. Default is 0 bits. -bits overrides -begr/-endr. \n");
printf(" -begr Begin Range: Specify Beginning Range in which you want to search, ex: 30000000000000000. Must use with -endr\n");
printf(" -endr End Range: Specify End of Range in which you want to search, ex: 3FFFFFFFFFFFFFFFF. Must use with -begr\n");
printf(" NOTE: when using -beginr and -endr, the program generates random keys in between those ranges. It will not\n");
printf(" search sequentially such as start at begr and stop at endr. Random keys in between the 2 ranges ONLY.\n");
printf(" -dis Display Private Key info on screen: 0 = off, 1 = on. Default is 0 / off.\n");
printf(" -drk Display random keys: 0 = off, 1 = on. Default is 0 / off.\n");
printf(" -nosse: Disable SSE hash function\n");
printf(" -l: List cuda enabled devices\n");
printf(" -check: Check CPU and GPU kernel vs CPU\n");
printf(" -cp privKey: Compute public key (privKey in hex hormat)\n");
printf(" -ca pubKey: Compute address (pubKey in hex hormat)\n");
printf(" -kp: Generate key pair\n");
printf(" -rp privkey partialkeyfile: Reconstruct final private key(s) from partial key(s) info.\n");
printf(" -sp startPubKey: Start the search with a pubKey (for private key splitting)\n");
printf(" -r rekey: Rekey interval in MegaKey (millions). Default is disabled / 0.\n");
Example batch file (for #66):
VBCr.exe -t 0 -bits 66 -gpu -g 360,512 -dis 1 -r 4800 -stop 13zb1hQbWVsc2S7ZTZnP2G4undNNpdh5so
pause
Or, if you want to narrow the search down in between a specific range:
VBCr.exe -t 0 -begr 20000000000000000 -endr 21000000000000000 -gpu -g 360,512 -dis 1 -r 4800 -stop 13zb1hQbWVsc2S7ZTZnP2G4undNNpdh5so
pause
UPDATE: The Random version is now available.
Link
https://github.com/WanderingPhilosopher/VanBitCrackenRandom
Read the readme to understand the different flags to use:
https://github.com/WanderingPhilosopher/VanBitCrackenRandom#readme
This thread is just to inform people of the release of the "Spread" version of VanBitCracken and now the Random version.
Link:
https://github.com/WanderingPhilosopher/VanBitCrakcenS
For now, I only have a Windows binary release. I will post source code later and may need help with Makefile since I am not a Linux/Makefile person; I mainly use Windows only, for better or for worse.
What is VanBitCracken? It is a cross between Vanity Search and Bitcrack. Telariust did the heavy lifting on this many months ago. I took the code and made minor tweaks and mods.
What does it do? Well, it can do what Vanity Search and Bitcrack do. But it's primary purpose is to help find the keys in the 32 BTC transaction challenge. AND, it does support RTX 30xx cards. Tested on a RTX 3070 card. For now, if you are using a 30xx card, you will have to use an address string, not the full address. Example: Use 16jY7qLJnxb7CHZyqBP8qca9d51 instead of full address 16jY7qLJnxb7CHZyqBP8qca9d51gAjyXQN
A few people have the newer RTX 30xx cards but no program to run them on. A few in the community are attempting to rewrite/rebuild/modify an existing program and that is great. This program can be a fill in the gap until they accomplish tweaking the other program.
THAT IS THE reason behind the release...people struggling to use 30xx cards.
Hopefully someone does tweak existing programs or writes a new one to fully utilize the 30xx cards.
This is the VanBitCracken Spread Version. The Spread means that this specific version is geared towards covering ranges, not doing any random mode. The random mode will come later.
You can use the flags/options that the program known as "Bitcrack" uses, except the -b -t -p options. This program uses the grid size options that JLPs version used in version 15. If you want to adjust grid size, use the -g option. Since this is based off of version 15, the y grid size is hard coded so all you can adjust is the x grid size.
Example: -gpu -g 512 -gpuId 0 .
The other bonus feature of this program versus Bitcrack is it supports multiple GPUs.
The other difference from Bitcrack is this program will search for partial/strings of addresses and does not need a full address and can search for wildcards.
I will update this more in-depth later.
Other flags include:
-t for CPU threads (not optimized for CPU use, that was not the intent/focus)
-gpu for gpu use
-gpuId 0 (if more than one gpu use -gpuId 0,1,2,3,4 etc.)
-g to adjust x grid size; -g 256
--keyspace to enter your start and end range; example 80000:FFFFF
--continue to save work/progress; --continue continue.txt
-o for output/results file; -o outputfile.txt
-i for input file of addresses/strings; -i inputfile.txt
-r for rekey; -r 100000 the -r is important because in this spread version, it really tells the program how often to save your continue file in MKey/s. Based on your gpu and its MKey/s, you need to adjust the -r. If your gpu's speed is 100 MKey/s and you want to save your continue file every minute, then you would calculate 60 (seconds) multiplied by 100 = 6000; so you would want to input -r 6000. If you do not input a -r it will go to the default of 10000 and depending on your card you could be saving every 5 to seconds (not recommended.)
You can also enter a single address/string at the end of your command line/batch file; command line ....... 19Hed12
More to follow...
