BitCrack - A tool for brute-forcing private keys

[citb0in]

yes! that is correct. Congrats!  

so it took only 6 seconds ? why is your program much faster than other available WIF CUDA solvers out there ?

[1715700611]

1715700611

[1715700611]

1715700611

[WanderingPhilospher]

yes! that is correct. Congrats!  

so it took only 6 seconds ? why is your program much faster than other available WIF CUDA solvers out there ?

Here is CPU only with 1 thread (Just luck though LOL):

Code:

VBCr v2.00
 Search For: 1CPHidfp1KfF79A54RA4MkMtdFwPSGjZwV [Compressed]
 Started on: Thu Jan 26 04:25:08 2023
 Randomness: New Random Keys Every 4 Mkeys
  Beg Range: 3A72698A3D348F69ED4B8DB3CD7FD0B7CABBB1978D18912038E8F2BCF177E7A (250 bit)
  End Range: 3A72698A3D348F69ED4B8DB3CD7FD0B7CABBB1978D18912038E8F2C1DA78935 (250 bit)
  Rng Width: 4E900ABB (31 bit)
CPU Threads: 1

 [00:00:00:02 Run Time][Total 3.19 MK/s][GPU 0.00 MK/s][Keys 6,536,192][Found 0][Rekeys: 0]
Random Key :  3A72698A3D348F69ED4B8DB3CD7FD0B7CABBB1978D18912038E8F2C0FEAEFBB

PubAddress: 1CPHidfp1KfF79A54RA4MkMtdFwPSGjZwV
Priv (WIF): p2pkh: KwLp2q49zihR4tgPrJaWSqcquiMhW2dRaXNkrM1Fq2XcEfdakLmJ
Priv (HEX): 3A72698A3D348F69ED4B8DB3CD7FD0B7CABBB1978D18912038E8F2C1025137F (250 bit)

Well I don't think you can really compare programs with such a small bit range (31 bits). Again, random versus sequential (over a huge space like #66) will be a true test...who gets luckier faster LOL.
This was just a brute force test in response to NotATether...if those characters were missing in the middle or towards the beginning, if the pubkey is known, I am sure a WIF solver like WIF Cuda would be much faster or a program like Kangaroo.

[Lolo54]

8 or 9 characters in a month? Depending on location of missing characters, and if they are sequentially missing, which seems to be what you are referring to (a fourth of a piece of paper); 8 or 9 missing from the end can be brute forced solved in seconds. Missing 13 or 14 from the end can be brute force solved in under an hour.

I am very curious to see if with the last 14 characters missing you put less than 1 hour to find this WIF

WIF (the last 14 are missing)
KwLp2q49zihR4tgPrJaWSqcqui

Compressed address
1KECKoV4CvqBeJaA1t7EgF2dYd4VQdHRfA

Good luck 

[WanderingPhilospher]

8 or 9 characters in a month? Depending on location of missing characters, and if they are sequentially missing, which seems to be what you are referring to (a fourth of a piece of paper); 8 or 9 missing from the end can be brute forced solved in seconds. Missing 13 or 14 from the end can be brute force solved in under an hour.

I am very curious to see if with the last 14 characters missing you put less than 1 hour to find this WIF

WIF (the last 14 are missing)
KwLp2q49zihR4tgPrJaWSqcqui

Compressed address
1KECKoV4CvqBeJaA1t7EgF2dYd4VQdHRfA

Good luck 

Is it missing 14 or 26?

[Lolo54]

Sorry, I made a mistake in my previous post. 
here is

WIF (the last 14 are missing)
KxQxHMsPZatAoe4g2xrZW2RFCXHm38LE5JuB6i??


Compressed address
1PA7i6w5pAvc72zhXJs7n1TpdtQ4isELKc

[WanderingPhilospher]

Sorry, I made a mistake in my previous post.  
here is

WIF (the last 14 are missing)
KxQxHMsPZatAoe4g2xrZW2RFCXHm38LE5JuB6i??


Compressed address
1PA7i6w5pAvc72zhXJs7n1TpdtQ4isELKc

Ok, this WIF looks better LOL...will try to find 1PA7i6w5pAvc72zhXJs7n1TpdtQ4isELKc

TBC...

Well....the old VBCr found it in under 4 minutes...For this test I used a 6 card RTX 3060 rig. Not bad, right?

Results:

Code:

VBCr v2.00
 Search For: 1PA7i6w5pAvc72zhXJs7n1TpdtQ4isELKc [Compressed]
 Started on: Thu Jan 26 12:07:31 2023
 Randomness: New Random Keys Every 297777 Mkeys
  Beg Range: 239F0AE394E704882B84E8E254E8EED6476203D11779341B72C67B769CA06018 (254 bit)
  End Range: 239F0AE394E704882B84E8E254E8EED6476203D11779341B72C724D5D6434B71 (254 bit)
  Rng Width: A95F39A2EB59 (48 bit)
CPU Threads: 0
GPU: GPU #0 NVIDIA GeForce RTX 3060 (28x128 cores) Grid(304x512)

Random Key :  239F0AE394E704882B84E8E254E8EED6476203D11779341B72C71433CDD89A79
Random Key :  239F0AE394E704882B84E8E254E8EED6476203D11779341B72C6CDFF4C971449
Random Key :  239F0AE394E704882B84E8E254E8EED6476203D11779341B72C6BAAF39184F66
Random Key :  239F0AE394E704882B84E8E254E8EED6476203D11779341B72C6B2D9A0BC40B9
Random Key :  239F0AE394E704882B84E8E254E8EED6476203D11779341B72C6F2B279B9C9EEGPU: GPU #1 NVIDIA GeForce RTX 3060 (28x128 cores) Grid(304x512)

Random Key :  239F0AE394E704882B84E8E254E8EED6476203D11779341B72C6C189C3FFC6AB
Random Key :  239F0AE394E704882B84E8E254E8EED6476203D11779341B72C6DD387E7AEFBC
Random Key :  239F0AE394E704882B84E8E254E8EED6476203D11779341B72C7109C945112F8
Random Key :  239F0AE394E704882B84E8E254E8EED6476203D11779341B72C6D618147B0DD1
Random Key :  239F0AE394E704882B84E8E254E8EED6476203D11779341B72C7081090ED2EE4GPU: GPU #3 NVIDIA GeForce RTX 3060 (28x128 cores) Grid(304x512)

Random Key :  239F0AE394E704882B84E8E254E8EED6476203D11779341B72C724D551E4F0F5
Random Key :  239F0AE394E704882B84E8E254E8EED6476203D11779341B72C7162856C43236
Random Key :  239F0AE394E704882B84E8E254E8EED6476203D11779341B72C708013561A548
Random Key :  239F0AE394E704882B84E8E254E8EED6476203D11779341B72C6BF976EC70563
Random Key :  239F0AE394E704882B84E8E254E8EED6476203D11779341B72C6DED54ECB2C7DGPU: GPU #4 NVIDIA GeForce RTX 3060 (28x128 cores) Grid(304x512)
GPU: GPU #2 NVIDIA GeForce RTX 3060 (28x128 cores) Grid(304x512)

Random Key :  239F0AE394E704882B84E8E254E8EED6476203D11779341B72C6C2A6FD0473C2
Random Key :  239F0AE394E704882B84E8E254E8EED6476203D11779341B72C7087352C151A2
Random Key :  239F0AE394E704882B84E8E254E8EED6476203D11779341B72C6BB66DB09A803
Random Key :  239F0AE394E704882B84E8E254E8EED6476203D11779341B72C7031DE6F6B16E
Random Key :  239F0AE394E704882B84E8E254E8EED6476203D11779341B72C6AB4F350CDD01
Random Key :  239F0AE394E704882B84E8E254E8EED6476203D11779341B72C711A52C95078D
Random Key :  239F0AE394E704882B84E8E254E8EED6476203D11779341B72C6BF086FFEBB39
Random Key :  239F0AE394E704882B84E8E254E8EED6476203D11779341B72C6AE6A1B8F276F
Random Key :  239F0AE394E704882B84E8E254E8EED6476203D11779341B72C70369E3469E01
Random Key :  239F0AE394E704882B84E8E254E8EED6476203D11779341B72C6D07F18F9460EGPU: GPU #5 NVIDIA GeForce RTX 3060 (28x128 cores) Grid(304x512)

 [00:00:00:30 Run Time][Total 5085.40 MK/s][GPU 5085.40 MK/s][Keys 156,674,031,616][Found 0][Rekeys: 0]

............

 [00:00:03:15 Run Time][Total 5111.14 MK/s][GPU 5111.14 MK/s][Keys 908,008,095,744][Found 0][Rekeys: 5]
Random Key :  239F0AE394E704882B84E8E254E8EED6476203D11779341B72C6E6AE0C5A3737
Random Key :  239F0AE394E704882B84E8E254E8EED6476203D11779341B72C6CA356DA81D53
Random Key :  239F0AE394E704882B84E8E254E8EED6476203D11779341B72C714902765A11D
Random Key :  239F0AE394E704882B84E8E254E8EED6476203D11779341B72C71AC0B846A60C
Random Key :  239F0AE394E704882B84E8E254E8EED6476203D11779341B72C6E3D27C6CCD54
Random Key :  239F0AE394E704882B84E8E254E8EED6476203D11779341B72C6F05D65DD0695
Random Key :  239F0AE394E704882B84E8E254E8EED6476203D11779341B72C6AD1A75713C27
Random Key :  239F0AE394E704882B84E8E254E8EED6476203D11779341B72C70DB63C099790
Random Key :  239F0AE394E704882B84E8E254E8EED6476203D11779341B72C6C521B823759E
Random Key :  239F0AE394E704882B84E8E254E8EED6476203D11779341B72C6B47DA710BB9A
Random Key :  239F0AE394E704882B84E8E254E8EED6476203D11779341B72C6A6350AC77FC5
Random Key :  239F0AE394E704882B84E8E254E8EED6476203D11779341B72C6C117A9A9EF19
Random Key :  239F0AE394E704882B84E8E254E8EED6476203D11779341B72C70BBF08275CCD
Random Key :  239F0AE394E704882B84E8E254E8EED6476203D11779341B72C6A601E695257C
Random Key :  239F0AE394E704882B84E8E254E8EED6476203D11779341B72C6ECB9664BACDF
Random Key :  239F0AE394E704882B84E8E254E8EED6476203D11779341B72C6F6CB7E862A00
Random Key :  239F0AE394E704882B84E8E254E8EED6476203D11779341B72C6FD9E8DEF21D6
Random Key :  239F0AE394E704882B84E8E254E8EED6476203D11779341B72C6E8D88B3ADFC1
Random Key :  239F0AE394E704882B84E8E254E8EED6476203D11779341B72C6B357C4B1390D
Random Key :  239F0AE394E704882B84E8E254E8EED6476203D11779341B72C6EB0C53378154
Random Key :  239F0AE394E704882B84E8E254E8EED6476203D11779341B72C6E2F5F0EAA62F
Random Key :  239F0AE394E704882B84E8E254E8EED6476203D11779341B72C6BACCAFEBDBB0
Random Key :  239F0AE394E704882B84E8E254E8EED6476203D11779341B72C6EE2D6E2E17D9
Random Key :  239F0AE394E704882B84E8E254E8EED6476203D11779341B72C6DDC0EDEFE40C
Random Key :  239F0AE394E704882B84E8E254E8EED6476203D11779341B72C6BB64630BC158
Random Key :  239F0AE394E704882B84E8E254E8EED6476203D11779341B72C7016A943486BD
Random Key :  239F0AE394E704882B84E8E254E8EED6476203D11779341B72C709D84247CF7D
Random Key :  239F0AE394E704882B84E8E254E8EED6476203D11779341B72C6B3903FA7684D
Random Key :  239F0AE394E704882B84E8E254E8EED6476203D11779341B72C6CAB8F0E93F89
 [00:00:03:38 Run Time][Total 5111.13 MK/s][GPU 5111.13 MK/s][Keys 1,006,347,747,328][Found 0][Rekeys: 6]

PubAddress: 1PA7i6w5pAvc72zhXJs7n1TpdtQ4isELKc
Priv (WIF): p2pkh: KxQxHMsPZatAoe4g2xrZW2RFCXHm38LE5JuB6itaciJedwdWB7iE
Priv (HEX): 239F0AE394E704882B84E8E254E8EED6476203D11779341B72C724638EC32D6E (254 bit)

PubAddress: 1PA7i6w5pAvc72zhXJs7n1TpdtQ4isELKc
Priv (WIF): p2pkh: KxQxHMsPZatAoe4g2xrZW2RFCXHm38LE5JuB6itaciJedwdWB7iE
Priv (HEX): 239F0AE394E704882B84E8E254E8EED6476203D11779341B72C724638EC32D6E (254 bit)

[Lolo54]

Exactly that's right!
Yes nice result but you have 6 nice GPUs . With one GPU let's say you would have taken about 15 min it's a good result
If you want to test 17 missing (as you have 6 beautiful GPU  )

wif  (the last 17 are missing)
KwRPC6Be7ukp2fh4rVYU4GrmfSdCweo2RxL

Compressed address
1MpqX7tzAWAo1bZv6msHM3mkQ6fHFh2mjE

good luck

What would be nice is if you post command lines to run

[WanderingPhilospher]

Exactly that's right!
Yes nice result but you have 6 nice GPUs . With one GPU let's say you would have taken about 15 min it's a good result

Well I did say in my original post, "As always, it depends on the program you are running and how much hardware you have."

That was a 48 bit range; which could take up to 4-5 hours to check every key, so I leaned on the side of caution and ran with 6 GPUs lol...

Thank you for the testing of 14 missing characters, I appreciate it.

wif  (the last 17 are missing)
KwRPC6Be7ukp2fh4rVYU4GrmfSdCweo2RxL

Compressed address
1MpqX7tzAWAo1bZv6msHM3mkQ6fHFh2mjE

That's a 60 bit range C018588C2B6CC47... I'm gonna have to pass on that one lol.

[Lolo54]

I understand lol ....but how long do you think it would take you to find with your material?

[Cyperh]

Exactly that's right!
Yes nice result but you have 6 nice GPUs . With one GPU let's say you would have taken about 15 min it's a good result

Well I did say in my original post, "As always, it depends on the program you are running and how much hardware you have."

That was a 48 bit range; which could take up to 4-5 hours to check every key, so I leaned on the side of caution and ran with 6 GPUs lol...

Thank you for the testing of 14 missing characters, I appreciate it.

wif  (the last 17 are missing)
KwRPC6Be7ukp2fh4rVYU4GrmfSdCweo2RxL

Compressed address
1MpqX7tzAWAo1bZv6msHM3mkQ6fHFh2mjE

That's a 60 bit range C018588C2B6CC47... I'm gonna have to pass on that one lol.

Very nice work! When the release of this new tool?

[Lolo54]

Exactly that's right!
Yes nice result but you have 6 nice GPUs . With one GPU let's say you would have taken about 15 min it's a good result

Well I did say in my original post, "As always, it depends on the program you are running and how much hardware you have."

That was a 48 bit range; which could take up to 4-5 hours to check every key, so I leaned on the side of caution and ran with 6 GPUs lol...

Thank you for the testing of 14 missing characters, I appreciate it.

wif  (the last 17 are missing)
KwRPC6Be7ukp2fh4rVYU4GrmfSdCweo2RxL

Compressed address
1MpqX7tzAWAo1bZv6msHM3mkQ6fHFh2mjE

That's a 60 bit range C018588C2B6CC47... I'm gonna have to pass on that one lol.

Can you insert for example the command line you used to perform this search and can you use it randomly?

[WanderingPhilospher]

Exactly that's right!
Yes nice result but you have 6 nice GPUs . With one GPU let's say you would have taken about 15 min it's a good result

Well I did say in my original post, "As always, it depends on the program you are running and how much hardware you have."

That was a 48 bit range; which could take up to 4-5 hours to check every key, so I leaned on the side of caution and ran with 6 GPUs lol...

Thank you for the testing of 14 missing characters, I appreciate it.

wif  (the last 17 are missing)
KwRPC6Be7ukp2fh4rVYU4GrmfSdCweo2RxL

Compressed address
1MpqX7tzAWAo1bZv6msHM3mkQ6fHFh2mjE

That's a 60 bit range C018588C2B6CC47... I'm gonna have to pass on that one lol.

Can you insert for example the command line you used to perform this search and can you use it randomly?

Sure, no problem:

Code:

VBCr.exe -stop -t 0 -drk 1 -dis 1 -gpu -g 480,512 -r 2900 -begr 6013a6d9493032a55781798cbba36961d73fb72d4a86ac940fcecb3e9857bf1 -endr 6013a6d9493032a55781798cbba36961d73fb72d4a86ac94cfe723cac3c4838 1MpqX7tzAWAo1bZv6msHM3mkQ6fHFh2mjE
pause

Note: This is searching with a GPU. You can change it to CPU by adding -t 4 (or whatever number of cores you want to use) and deleting the -gpu, -g flags.  You can also redo the -r flag to however often you want the CPU/GPU to generate new random keys. The -r is in millions so if you use -r 10, it will generate new random keys after 10,000,000 keys have been checked.

[proseller01]

How much estimated time will BitcCrack take to solve puzzle 65 with 4 GPU 2080

[citb0in]

How much estimated time will BitcCrack take to solve puzzle 65 with 4 GPU 2080

not too long. Save yourself the power consumption and the noise from the GPU fan volume. Here's the private key for it

Code:

1A838B13505B26867

SCNR  

[Lolo54]

Exactly that's right!
Yes nice result but you have 6 nice GPUs . With one GPU let's say you would have taken about 15 min it's a good result

Well I did say in my original post, "As always, it depends on the program you are running and how much hardware you have."

That was a 48 bit range; which could take up to 4-5 hours to check every key, so I leaned on the side of caution and ran with 6 GPUs lol...

Thank you for the testing of 14 missing characters, I appreciate it.

wif  (the last 17 are missing)
KwRPC6Be7ukp2fh4rVYU4GrmfSdCweo2RxL

Compressed address
1MpqX7tzAWAo1bZv6msHM3mkQ6fHFh2mjE

That's a 60 bit range C018588C2B6CC47... I'm gonna have to pass on that one lol.

Can you insert for example the command line you used to perform this search and can you use it randomly?

Sure, no problem:

Code:

VBCr.exe -stop -t 0 -drk 1 -dis 1 -gpu -g 480,512 -r 2900 -begr 6013a6d9493032a55781798cbba36961d73fb72d4a86ac940fcecb3e9857bf1 -endr 6013a6d9493032a55781798cbba36961d73fb72d4a86ac94cfe723cac3c4838 1MpqX7tzAWAo1bZv6msHM3mkQ6fHFh2mjE
pause

Note: This is searching with a GPU. You can change it to CPU by adding -t 4 (or whatever number of cores you want to use) and deleting the -gpu, -g flags.  You can also redo the -r flag to however often you want the CPU/GPU to generate new random keys. The -r is in millions so if you use -r 10, it will generate new random keys after 10,000,000 keys have been checked.

Thanks. can you put an example of using the -rp command?

[WanderingPhilospher]

Exactly that's right!
Yes nice result but you have 6 nice GPUs . With one GPU let's say you would have taken about 15 min it's a good result

Well I did say in my original post, "As always, it depends on the program you are running and how much hardware you have."

That was a 48 bit range; which could take up to 4-5 hours to check every key, so I leaned on the side of caution and ran with 6 GPUs lol...

Thank you for the testing of 14 missing characters, I appreciate it.

wif  (the last 17 are missing)
KwRPC6Be7ukp2fh4rVYU4GrmfSdCweo2RxL

Compressed address
1MpqX7tzAWAo1bZv6msHM3mkQ6fHFh2mjE

That's a 60 bit range C018588C2B6CC47... I'm gonna have to pass on that one lol.

Can you insert for example the command line you used to perform this search and can you use it randomly?

Sure, no problem:

Code:

VBCr.exe -stop -t 0 -drk 1 -dis 1 -gpu -g 480,512 -r 2900 -begr 6013a6d9493032a55781798cbba36961d73fb72d4a86ac940fcecb3e9857bf1 -endr 6013a6d9493032a55781798cbba36961d73fb72d4a86ac94cfe723cac3c4838 1MpqX7tzAWAo1bZv6msHM3mkQ6fHFh2mjE
pause

Note: This is searching with a GPU. You can change it to CPU by adding -t 4 (or whatever number of cores you want to use) and deleting the -gpu, -g flags.  You can also redo the -r flag to however often you want the CPU/GPU to generate new random keys. The -r is in millions so if you use -r 10, it will generate new random keys after 10,000,000 keys have been checked.

Thanks. can you put an example of using the -rp command?

https://github.com/JeanLucPons/VanitySearch#step-1

[humerh3]

How to run BitCrack with linux

As detailed as possible here: https://www.cryptoxploit.com/bitcrack/#

First time using linux in life, I'm stuck at command not found using root@ or even sudo, lol can't even get to github from linux command shell. I wonder what this error is ~#  lol

Linux:
1) sudo su - superuser/admin rights
2) then run the commands.
You must also enter your system password before using the console and press Enter.

[NotATether]

Linux:
1) sudo su - superuser/admin rights
2) then run the commands.
You must also enter your system password before using the console and press Enter.

I don't know why cryptoxploit wrote that instruction there but you don't need to be root to run GPU bitcrack or any of the commands listed. It just so happens that GPU systems you can rent online are automatically provisioned with a root account so that is what most people end up using to run it.

[Robert_BIT]

Hello,

Does anyone know how to best search for multiple addresses at once? Do we just add them line by line in a .txt file? What if we want to search for a large number of addresses, can we use a database / bloom of some sorts?

I am not sure of the limitations of searching a large number of addresses at once...I guess even for a small range like 2^40 it will make the search harder as you use more addresses. But haven't found any data on this on GitHub...

 

[npuath]

Does anyone know how to best search for multiple addresses at once?

As is often the case, the problem as stated is massively underspecified.

For instance:
- Are your target addresses correlated, perhaps even strictly sequential (in which case the solution is trivial)?
- How large is the dataset; is it feasible to transfer it to several kernels for parallellisation?
- Is the dataset mutable, or is it feasible to perform an initial, heavy transformation (in which case perfect hashing might outperform probabilistic/Bloom)?

Et cetera. A general database engine is almost certainly not optimal in either case.