VanBitCracken - a program to use for 32 BTC challenge (supports RTX 30xx cards)

[WanderingPhilospher]

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/VanBitCrackenRandom2

SHA256 Checksum:

Code:

5415d56416632faa7058e1ddf2a6cde037d6df22778606128369df4557627dc3

Flags:

Code:

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):

Code:

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:

Code:

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...

[1714943756]

1714943756

[1714943756]

1714943756

[1714943756]

1714943756

[WanderingPhilospher]

Some benchmarks:

36 bit range:

Code:

VanBitCrackenS v1.0
Keyspace start=800000000
Keyspace   end=FFFFFFFFF
Difficulty: 49015701099621550400511978774011251513098240
Search: 1Be2UF9NLfyLFbtm3TCbmuocc9 [Compressed]
Started at Fri Apr  2 14:18:43 2021
CPU threads used: 0
GPU: GPU #1 GeForce RTX 3070 (46x128 cores) Grid(368x512)

Finish at Fri Apr  2 14:18:47 2021

(Yes, it finds the key before any MKey/s are displayed, it took 4 seconds, start to finish)

37 bit range:

Code:

VanBitCrackenS v1.0
Keyspace start=1000000000
Keyspace   end=1FFFFFFFFF
Difficulty: 2842910663778049606317044711835302213583896576
Search: 14iXhn8bGajVWegZHJ18vJLHhnt [Compressed]
Started at Fri Apr  2 13:53:18 2021
CPU threads used: 0
GPU: GPU #1 GeForce RTX 3070 (46x128 cores) Grid(368x512)
1291.518 MK/s (GPU 1291.518 MK/s) (2^35.06) [00:00:26 Elapsed Time][0]
Finish at Fri Apr  2 13:53:48 2021

Multi GPU support:

Code:

VanBitCrackenS v1.0
Keyspace start=8000000000
Keyspace   end=FFFFFFFFFF
Difficulty: 49015701099621550400511978774011251513098240
Search: 1EeAxcprB2PpCnr34VfZdFrkUW [Compressed]
Started at Fri Apr  2 14:30:51 2021
CPU threads used: 0
GPU: GPU #1 GeForce RTX 3070 (46x128 cores) Grid(1024x512)
GPU: GPU #2 GeForce RTX 3070 (46x128 cores) Grid(1024x512)
GPU: GPU #3 GeForce RTX 3070 (46x128 cores) Grid(1024x512)
GPU: GPU #0 GeForce RTX 3070 (46x128 cores) Grid(1024x512)
5063.635 MK/s (GPU 5063.635 MK/s) (2^38.89) [00:01:46 Elapsed Time][0]
Finish at Fri Apr  2 14:32:47 2021

The first 36 keys/addresses in 32BTC challenge transaction:

Code:

VanBitCrackenS v1.0
Keyspace start=1
Keyspace   end=FFFFFFFFF
Search: 36 prefixes (Lookup size 36) [Compressed]
Started at Fri Apr  2 15:15:27 2021
CPU threads used: 0
GPU: GPU #0 GeForce RTX 3070 (46x128 cores) Grid(46x512)
1160.747 MK/s (GPU 1160.747 MK/s) (2^35.34) [00:00:37 Elapsed Time][35]
Finish at Fri Apr  2 15:16:07 2021

Opened up in bigger range:

Code:

VanBitCrackenS v1.0
Keyspace start=8000000000000000
Keyspace   end=FFFFFFFFFFFFFFFF
Difficulty: 49015701099621550400511978774011251513098240
Search: 1Be2UF9NLfyLFbtm3TCbmuocc9 [Compressed]
Started at Fri Apr  2 15:44:17 2021
CPU threads used: 0
GPU: GPU #0 GeForce RTX 3070 (46x128 cores) Grid(512x512)
1502.555 MK/s (GPU 1502.555 MK/s) (2^33.52) [00:00:08 Elapsed Time][0]

[WanderingPhilospher]

Reserved for OP...

[WanderingPhilospher]

Reserved for OP...

[WanderingPhilospher]

For those who may have used a similar version and worried about not stopping after key range has been exhausted.

Code:

VanBitCrackenS v1.0
Keyspace start=800000000
Keyspace   end=FFFFFFFFF
Difficulty: 1287559351899699109443338982391808
Search: 1DZwL7cMCYXeRjXTBzXA [Compressed]
Started at Fri Apr  2 14:23:20 2021
CPU threads used: 0
GPU: GPU #1 GeForce RTX 3070 (46x128 cores) Grid(368x512)
1295.291 MK/s (GPU 1295.291 MK/s) (2^36.01) [00:00:43 Elapsed Time][0]
[EXIT] Reached end of keyspace.

Finish at Fri Apr  2 14:24:06 2021

I ran the above with a key not in the range so it would run the entire range/keyspace.

[zahid888]

Its just awesome speed is bit low maybe i have to play with -g please suggest best grid size ??

[WanderingPhilospher]

Its just awesome speed is bit low maybe i have to play with -g please suggest best grid size ??

What is your card and speed?

Try -gpu -g 256 -gpuId 0 (or -g 512, or -g 1024)

[zahid888]

Its just awesome speed is bit low maybe i have to play with -g please suggest best grid size ??

What is your card and speed?

here is my benchmark

C:\Users\VanBitCrackenS1.exe  -t 0 -gpu -g 256 -i C:/puzzleprefix.txt -o C:/Result.txt --keyspace A36D5FE700000000:A36D5FE7ffffffff
VanBitCrackenS v1.0
Keyspace start=A36D5FE700000000
Keyspace   end=A36D5FE7FFFFFFFF
Search: 13 prefixes (Lookup size 13) [Compressed]
Started at Sat Apr  3 01:04:43 2021
CPU threads used: 0
GPU: GPU #0 GeForce RTX 3060 Ti (38x128 cores) Grid(256x512)
714.845 MK/s (GPU 714.845 MK/s) (2^32.00) [00:00:06 Elapsed Time][0]
[EXIT] Reached end of keyspace.

Finish at Sat Apr  3 01:04:51 2021

[zahid888]

Is it working with full prefixes

[WanderingPhilospher]

Its just awesome speed is bit low maybe i have to play with -g please suggest best grid size ??

What is your card and speed?

here is my benchmark

C:\Users\VanBitCrackenS1.exe  -t 0 -gpu -g 256 -i C:/puzzleprefix.txt -o C:/Result.txt --keyspace A36D5FE700000000:A36D5FE7ffffffff
VanBitCrackenS v1.0
Keyspace start=A36D5FE700000000
Keyspace   end=A36D5FE7FFFFFFFF
Search: 13 prefixes (Lookup size 13) [Compressed]
Started at Sat Apr  3 01:04:43 2021
CPU threads used: 0
GPU: GPU #0 GeForce RTX 3060 Ti (38x128 cores) Grid(256x512)
714.845 MK/s (GPU 714.845 MK/s) (2^32.00) [00:00:06 Elapsed Time][0]
[EXIT] Reached end of keyspace.

Finish at Sat Apr  3 01:04:51 2021

8 seconds to get through the range? May need to open it up a bit.  Also, the MKey/s rate will drop when the program is getting ready to roll over to the next keys and then pick right back up. Try adding -r if you try a larger range.

[WanderingPhilospher]

Is it working with full prefixes

No, 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

But you can still use input file with many addresses you just have to cut off last 7-8 characters of address.

[zahid888]

https://imgur.com/PnFz735

[WanderingPhilospher]

https://imgur.com/PnFz735

In smaller range with mulitple prefixes, I actually drop the x grid size.

I match it up with the actual x size. So for 3070 it is 46 so I put in a -g 46.  But you can tweak to your liking.  Have you tried one prefix/address?

If it could use full address and search for RIPE, would be faster.

[zahid888]

I am very happy if --stride has also enabled here it would be icing on the cake 

[WanderingPhilospher]

I am very happy if --stride has also enabled here it would be icing on the cake 

Honestly, I never understood the point of stride. I was always "afraid" I would "stride" right over the key!

I prefer random over stride.  May have to get with Pawgo; I know he has implemented a stride function in one of JLPs other programs.  If it's something easy, I could possibly implement, but I haven't even thought about it since I really didn't understand the "why" behind it.

[zahid888]

In smaller range with mulitple prefixes, I actually drop the x grid size.

I match it up with the actual x size. So for 3070 it is 46 so I put in a -g 46.  But you can tweak to your liking.  Have you tried one prefix/address?

If it could use full address and search for RIPE, would be faster.

in full address

C:\VanBitCracken\VanBitCrackenS1.exe -gpu --keyspace 8000000000000000:ffffffffffffffff 16jY7qLJnxb7CHZyqBP8qca9d51gAjyXQN
VanBitCrackenS v1.0
Keyspace start=8000000000000000
Keyspace   end=FFFFFFFFFFFFFFFF
Difficulty: 1461501637330902918203684832716283019655932542976
Search: 16jY7qLJnxb7CHZyqBP8qca9d51gAjyXQN [Compressed]
Started at Sat Apr  3 02:26:04 2021
CPU threads used: 5
GPU: GPU #0 GeForce RTX 3060 Ti (38x128 cores) Grid(304x512)
794.487 MK/s (GPU 775.923 MK/s) (2^32.19) [00:00:06 Elapsed Time][0]GPUEngine: Launch: misaligned address

Finish at Sat Apr  3 02:26:13 2021

Can you release 512, 256 and 128 also

[WanderingPhilospher]

In smaller range with mulitple prefixes, I actually drop the x grid size.

I match it up with the actual x size. So for 3070 it is 46 so I put in a -g 46.  But you can tweak to your liking.  Have you tried one prefix/address?

If it could use full address and search for RIPE, would be faster.

in full address

C:\VanBitCracken\VanBitCrackenS1.exe -gpu --keyspace 8000000000000000:ffffffffffffffff 16jY7qLJnxb7CHZyqBP8qca9d51gAjyXQN
VanBitCrackenS v1.0
Keyspace start=8000000000000000
Keyspace   end=FFFFFFFFFFFFFFFF
Difficulty: 1461501637330902918203684832716283019655932542976
Search: 16jY7qLJnxb7CHZyqBP8qca9d51gAjyXQN [Compressed]
Started at Sat Apr  3 02:26:04 2021
CPU threads used: 5
GPU: GPU #0 GeForce RTX 3060 Ti (38x128 cores) Grid(304x512)
794.487 MK/s (GPU 775.923 MK/s) (2^32.19) [00:00:06 Elapsed Time][0]GPUEngine: Launch: misaligned address

Finish at Sat Apr  3 02:26:13 2021

Right, as I said, must use string vs full address. I usally chop 7 to 8 characters off.
That's what I don't get. Everyone trying to tweak the other program which won't even run with updated drivers, with any 20xx or 30xx cards, and try to fix the misaligned address issue. Where as VS/VBC only has the issue of using full address.  Maybe everyone loves the "stride" version as you stated  
Anywho, hopefully someone figures it all out or Jean Luc comes back to save the day!

Can you release 512, 256 and 128 also

I ran those for comparisons but the 512 always got through a range faster. I even recompiled newer version where you could manually enter -g x,y and it didn't even perform as well.

[fxsniper]

Thank you WanderingPhilospher for VanBitCracken

my test for small GPU

Code:

VanBitCrackenS1 -t 0 -gpu -gpuId 0 -r 150000 --keyspace d555555555555400:ffffffffffffffff -o output.txt -i input.txt 16jY7qLJnxb7CHZyqBP8qca9d51gAjyXQN
VanBitCrackenS v1.0
Keyspace start=D555555555555400
Keyspace   end=FFFFFFFFFFFFFFFF
Search: 11 prefixes (Lookup size 1) [Compressed]
Started at Sat Apr  3 08:11:22 2021
CPU threads used: 0
GPU: GPU #0 GeForce GTX 1050 (5x128 cores) Grid(40x512)
68.915 MK/s (GPU 68.915 MK/s) (2^29.64) [00:00:12 Elapsed Time][194]

I scan by strategy search (random keyspace) not scan by power of GPU my GPU is very very small

[fxsniper]

Code:

VanBitCrackenS1 -t 0 -gpu -gpuId 0 -r 150000 --keyspace 800000000:FFFFFFFFF 1Be2UF9NLfyLFbtm3TCbmuocc9
VanBitCrackenS v1.0
Keyspace start=800000000
Keyspace   end=FFFFFFFFF
Difficulty: 49015701099621550400511978774011251513098240
Search: 1Be2UF9NLfyLFbtm3TCbmuocc9 [Compressed]
Started at Sat Apr  3 08:45:35 2021
CPU threads used: 0
GPU: GPU #0 GeForce GTX 1050 (5x128 cores) Grid(40x512)
67.027 MK/s (GPU 67.027 MK/s) (2^31.85) [00:00:56 Elapsed Time][0]
65.763 MK/s (GPU 65.763 MK/s) (2^37.13) [00:37:06 Elapsed Time][1]
[EXIT] Reached end of keyspace.

Finish at Sat Apr  3 09:22:44 2021

compare
GeForce RTX 3060 Ti use time 1 second

my GTX 1050 use time near 1 hour for scan all key space

Can possible to print out key if not use options output
or print both may be safety

Scan found key but not use -o out.txt for save it make mission key

[WanderingPhilospher]

Code:

VanBitCrackenS1 -t 0 -gpu -gpuId 0 -r 150000 --keyspace 800000000:FFFFFFFFF 1Be2UF9NLfyLFbtm3TCbmuocc9
VanBitCrackenS v1.0
Keyspace start=800000000
Keyspace   end=FFFFFFFFF
Difficulty: 49015701099621550400511978774011251513098240
Search: 1Be2UF9NLfyLFbtm3TCbmuocc9 [Compressed]
Started at Sat Apr  3 08:45:35 2021
CPU threads used: 0
GPU: GPU #0 GeForce GTX 1050 (5x128 cores) Grid(40x512)
67.027 MK/s (GPU 67.027 MK/s) (2^31.85) [00:00:56 Elapsed Time][0]
65.763 MK/s (GPU 65.763 MK/s) (2^37.13) [00:37:06 Elapsed Time][1]
[EXIT] Reached end of keyspace.

Finish at Sat Apr  3 09:22:44 2021

compare
GeForce RTX 3060 Ti use time 1 second

my GTX 1050 use time near 1 hour for scan all key space

Can possible to print out key if not use options output
or print both may be safety

Scan found key but not use -o out.txt for save it make mission key

I'll look into it fxsniper...I do understand the concern.
Also, since you are using a 1050, you should be able to use full address and gain speed.