Pages:
Author

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

full member
Activity: 1162
Merit: 237
Shooters Shoot...
Maybe someone can give me a WIF missing the last 12 characters and the public address, compressed or uncompressed, doesn't matter, so I can show that it works and not just me picking and choosing the WIF?

here you go

WIF:
KwLp2q49zihR4tgPrJaWSqcquiMhW2dRaXNkrM1F

legacy addressed compressed:
1CPHidfp1KfF79A54RA4MkMtdFwPSGjZwV

on my machine, it takes 3min to find the correct WIF with last 8 missing characters. But it would take a huge time for 12 missing characters at the end so I am curious to see your results and how much time it took.

Code:
VBCr v2.00
 Search For: 1CPHidfp1KfF79A54RA4MkMtdFwPSGjZwV [Compressed]
 Started on: Thu Jan 26 03:36:58 2023
  Beg Range: 3A72698A3D348F69ED4B8DB3CD7FD0B7CABBB1978D18912038E8F2BCF177E7A (250 bit)
  End Range: 3A72698A3D348F69ED4B8DB3CD7FD0B7CABBB1978D18912038E8F2C1DA78935 (250 bit)
  Rng Width: 4E900ABB (31 bit)
CPU Threads: 0
GPU: GPU #0 NVIDIA GeForce GTX 1660 Ti (24x64 cores) Grid(2800x512)

Random Key :  3A72698A3D348F69ED4B8DB3CD7FD0B7CABBB1978D18912038E8F2BEDB5F735
Random Key :  3A72698A3D348F69ED4B8DB3CD7FD0B7CABBB1978D18912038E8F2C1AB8CC4D
Random Key :  3A72698A3D348F69ED4B8DB3CD7FD0B7CABBB1978D18912038E8F2BD15473E0
Random Key :  3A72698A3D348F69ED4B8DB3CD7FD0B7CABBB1978D18912038E8F2C0D180787
Random Key :  3A72698A3D348F69ED4B8DB3CD7FD0B7CABBB1978D18912038E8F2BD482D190
Random Key :  3A72698A3D348F69ED4B8DB3CD7FD0B7CABBB1978D18912038E8F2BD5988CC3
Random Key :  3A72698A3D348F69ED4B8DB3CD7FD0B7CABBB1978D18912038E8F2C02B27041
Random Key :  3A72698A3D348F69ED4B8DB3CD7FD0B7CABBB1978D18912038E8F2BDA860272
Random Key :  3A72698A3D348F69ED4B8DB3CD7FD0B7CABBB1978D18912038E8F2BD1E2CEEB
Random Key :  3A72698A3D348F69ED4B8DB3CD7FD0B7CABBB1978D18912038E8F2BDB62B358Divide by 0!
 [00:00:00:06 Run Time][Total 476.33 MK/s][GPU 476.33 MK/s][Keys 2,936,012,800][Found 0][Rekeys: 0]

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

Code:
VBCr v2.00
 Search For: 1CPHidfp1KfF79A54RA4MkMtdFwPSGjZwV [Compressed]
 Started on: Thu Jan 26 03:38:51 2023
  Beg Range: 3A72698A3D348F69ED4B8DB3CD7FD0B7CABBB1978D18912038E8F2BCF177E7A (250 bit)
  End Range: 3A72698A3D348F69ED4B8DB3CD7FD0B7CABBB1978D18912038E8F2C1DA78935 (250 bit)
  Rng Width: 4E900ABB (31 bit)
CPU Threads: 0
GPU: GPU #0 NVIDIA GeForce GTX 1660 Ti (24x64 cores) Grid(480x512)

Random Key :  3A72698A3D348F69ED4B8DB3CD7FD0B7CABBB1978D18912038E8F2BDC57421E
Random Key :  3A72698A3D348F69ED4B8DB3CD7FD0B7CABBB1978D18912038E8F2BF1915AE7
Random Key :  3A72698A3D348F69ED4B8DB3CD7FD0B7CABBB1978D18912038E8F2C0D7866CA
Random Key :  3A72698A3D348F69ED4B8DB3CD7FD0B7CABBB1978D18912038E8F2BF4D70D69
Random Key :  3A72698A3D348F69ED4B8DB3CD7FD0B7CABBB1978D18912038E8F2C1D05AC94
Random Key :  3A72698A3D348F69ED4B8DB3CD7FD0B7CABBB1978D18912038E8F2BD50D0A5E
Random Key :  3A72698A3D348F69ED4B8DB3CD7FD0B7CABBB1978D18912038E8F2BDF95E0DF
Random Key :  3A72698A3D348F69ED4B8DB3CD7FD0B7CABBB1978D18912038E8F2C055A62A9
Random Key :  3A72698A3D348F69ED4B8DB3CD7FD0B7CABBB1978D18912038E8F2BE4C9739D
 [00:00:00:06 Run Time][Total 610.07 MK/s][GPU 610.07 MK/s][Keys 3,774,873,600][Found 0][Rekeys: 0]

PubAddress: 1CPHidfp1KfF79A54RA4MkMtdFwPSGjZwV
Priv (WIF): p2pkh: KwLp2q49zihR4tgPrJaWSqcquiMhW2dRaXNkrM1Fq2XcEfdakLmJ
Priv (HEX): 3A72698A3D348F69ED4B8DB3CD7FD0B7CABBB1978D18912038E8F2C1025137F (250 bit)
legendary
Activity: 2912
Merit: 1091
--- ChainWorks Industries ---
Can you explain what you mean by 40 characters?
L2Dxz8UtQhVhC7WAedJRnoHYnhawTukMerG2XTpUdRHNkpQX2Nw4

and

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 just guesstimated the 40 characters in a WIF from memory. Apparently it is closer to 50.

The 8-9 chars metric is independent of the WIF length and I basically multiplied 1 billion tries (keys) * 60 seconds * 60 minutes * 24 hours * 30 days.

CPUs of course cannot check that many keys per second but newer GPUs certainly can, particularly if they are used in SLI or whatever the heck NVIDIA calls it today.

Or used in Parallel ...

Wink

#crysx #cwi
legendary
Activity: 1568
Merit: 6660
bitcoincleanup.com / bitmixlist.org
Can you explain what you mean by 40 characters?
L2Dxz8UtQhVhC7WAedJRnoHYnhawTukMerG2XTpUdRHNkpQX2Nw4

and

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 just guesstimated the 40 characters in a WIF from memory. Apparently it is closer to 50.

The 8-9 chars metric is independent of the WIF length and I basically multiplied 1 billion tries (keys) * 60 seconds * 60 minutes * 24 hours * 30 days.

CPUs of course cannot check that many keys per second but newer GPUs certainly can, particularly if they are used in SLI or whatever the heck NVIDIA calls it today.
hero member
Activity: 630
Merit: 731
Bitcoin g33k
Maybe someone can give me a WIF missing the last 12 characters and the public address, compressed or uncompressed, doesn't matter, so I can show that it works and not just me picking and choosing the WIF?

here you go

WIF:
KwLp2q49zihR4tgPrJaWSqcquiMhW2dRaXNkrM1F

legacy addressed compressed:
1CPHidfp1KfF79A54RA4MkMtdFwPSGjZwV

on my machine, it takes 3min to find the correct WIF with last 8 missing characters. But it would take a huge time for 12 missing characters at the end so I am curious to see your results and how much time it took.
full member
Activity: 1162
Merit: 237
Shooters Shoot...
VBCR v2 ? which tool is this and where can we download ?

VBCR v2 on development stage.
If I'm not mistaken, it will soon be available for download here: https://github.com/WanderingPhilosopher/VanBitCrackenRandom2
Correct...

New GPU test and result (last 12 characters from WIF missing) for the WIF statement above:

Code:
VBCr v2.00
 Search For: 1KECKoV4CvqBeJaA1t7EgF2dYd4VQdHRfA [Uncompressed]
 Started on: Wed Jan 25 13:35:55 2023
 Randomness: New Random Keys Every 500 Mkeys
  Beg Range: 955179C4C20FADBAA6E568FC22BADC890A8F6712844E51E2F0363442BFCAC919 (256 bit)
  End Range: 955179C4C20FADBAA6E568FC22BADC890A8F6712844E51E2F03634914FD5846C (256 bit)
  Rng Width: 4E900ABB53 (39 bit)
CPU Threads: 0
GPU: GPU #0 NVIDIA GeForce GTX 1660 Ti (24x64 cores) Grid(224x256)

Random Key :  955179C4C20FADBAA6E568FC22BADC890A8F6712844E51E2F0363448C3EC6D93
Random Key :  955179C4C20FADBAA6E568FC22BADC890A8F6712844E51E2F036345F3DEED11D
Random Key :  955179C4C20FADBAA6E568FC22BADC890A8F6712844E51E2F036344ECE043049
Random Key :  955179C4C20FADBAA6E568FC22BADC890A8F6712844E51E2F0363472878B4058
Random Key :  955179C4C20FADBAA6E568FC22BADC890A8F6712844E51E2F036346690F1411C
Random Key :  955179C4C20FADBAA6E568FC22BADC890A8F6712844E51E2F03634469BFF3125
Random Key :  955179C4C20FADBAA6E568FC22BADC890A8F6712844E51E2F036344F060DDC1D
Random Key :  955179C4C20FADBAA6E568FC22BADC890A8F6712844E51E2F03634703F81B3CA
Random Key :  955179C4C20FADBAA6E568FC22BADC890A8F6712844E51E2F036345A51B1B298
 [00:00:00:02 Run Time][Total 512.54 MK/s][GPU 512.54 MK/s][Keys 1,056,964,608][Found 0][Rekeys: 0]

.........
 [00:00:07:27 Run Time][Total 338.08 MK/s][GPU 338.08 MK/s][Keys 150,852,337,664][Found 0][Rekeys: 108]
Random Key :  955179C4C20FADBAA6E568FC22BADC890A8F6712844E51E2F036346A4FACC2CA
Random Key :  955179C4C20FADBAA6E568FC22BADC890A8F6712844E51E2F036345FAE9DA7C1
Random Key :  955179C4C20FADBAA6E568FC22BADC890A8F6712844E51E2F03634895AA21905
Random Key :  955179C4C20FADBAA6E568FC22BADC890A8F6712844E51E2F0363468980E9B7E
 [00:00:07:31 Run Time][Total 338.09 MK/s][GPU 338.09 MK/s][Keys 152,261,623,808][Found 0][Rekeys: 109]
Random Key :  955179C4C20FADBAA6E568FC22BADC890A8F6712844E51E2F036348FCAB98C6F
Random Key :  955179C4C20FADBAA6E568FC22BADC890A8F6712844E51E2F03634496E9C1B68
Random Key :  955179C4C20FADBAA6E568FC22BADC890A8F6712844E51E2F036348BCEC345B7
Random Key :  955179C4C20FADBAA6E568FC22BADC890A8F6712844E51E2F03634459566102E
 [00:00:07:33 Run Time][Total 338.09 MK/s][GPU 338.09 MK/s][Keys 152,672,665,600][Found 0][Rekeys: 110]

PubAddress: 1KECKoV4CvqBeJaA1t7EgF2dYd4VQdHRfA
Priv (WIF): p2pkh: 5Jx3iVRtyaC2reGfta9UpXsshiNHRDrhUcBCg5GHgWyGoePGMMf
Priv (HEX): 955179C4C20FADBAA6E568FC22BADC890A8F6712844E51E2F036345958325B50 (256 bit)


I put a short leash on the -r (rekey factor, I used -r 500, so GPU was generating new keys every 4 seconds) to jump in and out of more ranges more quickly...I do not think there is a right or wrong; I was giving insight into the amount of rekeys and the slowed down hash rate.

There were 337,424,071,507 keys to check but the program only reached 152,672,665,600 keys checked before finding the key. Sequentially spread out over the range may have worked faster, or a lot slower. It's all luck when you get into these higher bit ranges, IMO.

Maybe someone can give me a WIF missing the last 12 characters and the public address, compressed or uncompressed, doesn't matter, so I can show that it works and not just me picking and choosing the WIF?

Sequential test using my KeyHunter (modified version of keyhunt cuda and rotor cuda):
Code:
 KeyHunter v1.43 (Dec.19.2022)

  COMP MODE    : UNCOMPRESSED
  COIN TYPE    : BITCOIN
  SEARCH MODE  : Single Address
  DEVICE       : GPU
  CPU THREAD   : 0
  GPU IDS      : 0
  GPU GRIDSIZE : 224x256
  SSE          : YES
  BTC ADDRESS  : 1KECKoV4CvqBeJaA1t7EgF2dYd4VQdHRfA
  OUTPUT FILE  : testwif.txt

  Start Time   : Wed Jan 25 14:09:39 2023
  Start Range  : 955179C4C20FADBAA6E568FC22BADC890A8F6712844E51E2F0363442BFCAC919 (256 bit)
  End Range    : 955179C4C20FADBAA6E568FC22BADC890A8F6712844E51E2F03634914FD5846C (256 bit)
  Range Width  : 4E900ABB53 (39 bit)

  GPU          : GPU #0 NVIDIA GeForce GTX 1660 Ti (24x64 cores) Grid(224x256)

  Thread info  : Dividing the range 4E900ABB53 (39 bit) by 57344 GPU threads

  Thread 00000 : 955179C4C20FADBAA6E568FC22BADC890A8F6712844E51E2F0363442BFCAC919 -> 955179C4C20FADBAA6E568FC22BADC890A8F6712844E51E2F0363442C0249249
  Thread 00001 : 955179C4C20FADBAA6E568FC22BADC890A8F6712844E51E2F0363442C0249249 -> 955179C4C20FADBAA6E568FC22BADC890A8F6712844E51E2F0363442C07E5B79
  Thread 00002 : 955179C4C20FADBAA6E568FC22BADC890A8F6712844E51E2F0363442C07E5B79 -> 955179C4C20FADBAA6E568FC22BADC890A8F6712844E51E2F0363442C0D824A9
  Thread 00003 : 955179C4C20FADBAA6E568FC22BADC890A8F6712844E51E2F0363442C0D824A9 -> 955179C4C20FADBAA6E568FC22BADC890A8F6712844E51E2F0363442C131EDD9
           ... :
  Thread 19114 : 955179C4C20FADBAA6E568FC22BADC890A8F6712844E51E2F036345CEF9242F9 -> 955179C4C20FADBAA6E568FC22BADC890A8F6712844E51E2F036345CEFEC0C29
  Thread 19115 : 955179C4C20FADBAA6E568FC22BADC890A8F6712844E51E2F036345CEFEC0C29 -> 955179C4C20FADBAA6E568FC22BADC890A8F6712844E51E2F036345CF045D559
  Thread 19116 : 955179C4C20FADBAA6E568FC22BADC890A8F6712844E51E2F036345CF045D559 -> 955179C4C20FADBAA6E568FC22BADC890A8F6712844E51E2F036345CF09F9E89
           ... :
  Thread 28672 : 955179C4C20FADBAA6E568FC22BADC890A8F6712844E51E2F036346A07CFC919 -> 955179C4C20FADBAA6E568FC22BADC890A8F6712844E51E2F036346A08299249
  Thread 28673 : 955179C4C20FADBAA6E568FC22BADC890A8F6712844E51E2F036346A08299249 -> 955179C4C20FADBAA6E568FC22BADC890A8F6712844E51E2F036346A08835B79
  Thread 28674 : 955179C4C20FADBAA6E568FC22BADC890A8F6712844E51E2F036346A08835B79 -> 955179C4C20FADBAA6E568FC22BADC890A8F6712844E51E2F036346A08DD24A9
           ... :
  Thread 57342 : 955179C4C20FADBAA6E568FC22BADC890A8F6712844E51E2F03634914F2136B9 -> 955179C4C20FADBAA6E568FC22BADC890A8F6712844E51E2F03634914F7AFFE9
  Thread 57343 : 955179C4C20FADBAA6E568FC22BADC890A8F6712844E51E2F03634914F7AFFE9 -> 955179C4C20FADBAA6E568FC22BADC890A8F6712844E51E2F03634914FD4C919
  Thread 57344 : 955179C4C20FADBAA6E568FC22BADC890A8F6712844E51E2F03634914FD4C919 -> 955179C4C20FADBAA6E568FC22BADC890A8F6712844E51E2F0363491502E9249

  [00:07:20] [955179C4C20FADBAA6E568FC22BADC890A8F6712844E51E2F03634747C8EA990] [F: 0] [00:03:54] [C: 65.329021 %] [GPU: 498.23 Mk/s] [T: 220,435,841,024]
  =================================================================================
  PubAddress: 1KECKoV4CvqBeJaA1t7EgF2dYd4VQdHRfA
  Priv (WIF): p2pkh:5Jx3iVRtyaC2reGfta9UpXsshiNHRDrhUcBCg5GHgWyGoePGMMf
  Priv (HEX): 955179C4C20FADBAA6E568FC22BADC890A8F6712844E51E2F036345958325B50
  PubK (HEX): 04FA35DA91A41FF83CC228CBF6BFFFB3C8BC355ED2619A723807FDC72A036E241CFCEB66C998061569A1368CFFF26EB49FFEB173B773BF4195F15081FD86E6072C
  =================================================================================
  [00:07:21] [955179C4C20FADBAA6E568FC22BADC890A8F6712844E51E2F03634749A40F0A2] [F: 1] [00:03:53] [C: 65.468241 %] [GPU: 498.22 Mk/s] [T: 220,905,603,072]
[EXIT] Reached end of keyspace.
Overall speed was quicker, but that is because the GPU speed was roughly 120 MKey/s faster due to no rekey involved. A small rekey chokes the GPU speed. But it had to check almost 50 billion more keys.
Why do I say it's luck? Let's say our beginning range was different. Let's move it up by 2,000,000 keys. New starting range of: 955179c4c20fadbaa6e568fc22badc890a8f6712844e51e2f0363442bfe94d99
Now let's rerun the sequential test:

Code:
 KeyHunter v1.43 (Dec.19.2022)

  COMP MODE    : UNCOMPRESSED
  COIN TYPE    : BITCOIN
  SEARCH MODE  : Single Address
  DEVICE       : GPU
  CPU THREAD   : 0
  GPU IDS      : 0
  GPU GRIDSIZE : 224x256
  SSE          : YES
  BTC ADDRESS  : 1KECKoV4CvqBeJaA1t7EgF2dYd4VQdHRfA
  OUTPUT FILE  : testwif.txt

  Start Time   : Wed Jan 25 14:24:59 2023
  Start Range  : 955179C4C20FADBAA6E568FC22BADC890A8F6712844E51E2F0363442BFE94D99 (256 bit)
  End Range    : 955179C4C20FADBAA6E568FC22BADC890A8F6712844E51E2F03634914FD5846C (256 bit)
  Range Width  : 4E8FEC36D3 (39 bit)

  GPU          : GPU #0 NVIDIA GeForce GTX 1660 Ti (24x64 cores) Grid(224x256)

  Thread info  : Dividing the range 4E8FEC36D3 (39 bit) by 57344 GPU threads

  Thread 00000 : 955179C4C20FADBAA6E568FC22BADC890A8F6712844E51E2F0363442BFE94D99 -> 955179C4C20FADBAA6E568FC22BADC890A8F6712844E51E2F0363442C04316A6
  Thread 00001 : 955179C4C20FADBAA6E568FC22BADC890A8F6712844E51E2F0363442C04316A6 -> 955179C4C20FADBAA6E568FC22BADC890A8F6712844E51E2F0363442C09CDFB3
  Thread 00002 : 955179C4C20FADBAA6E568FC22BADC890A8F6712844E51E2F0363442C09CDFB3 -> 955179C4C20FADBAA6E568FC22BADC890A8F6712844E51E2F0363442C0F6A8C0
  Thread 00003 : 955179C4C20FADBAA6E568FC22BADC890A8F6712844E51E2F0363442C0F6A8C0 -> 955179C4C20FADBAA6E568FC22BADC890A8F6712844E51E2F0363442C15071CD
           ... :
  Thread 19114 : 955179C4C20FADBAA6E568FC22BADC890A8F6712844E51E2F036345CEFA6923B -> 955179C4C20FADBAA6E568FC22BADC890A8F6712844E51E2F036345CF0005B48
  Thread 19115 : 955179C4C20FADBAA6E568FC22BADC890A8F6712844E51E2F036345CF0005B48 -> 955179C4C20FADBAA6E568FC22BADC890A8F6712844E51E2F036345CF05A2455
  Thread 19116 : 955179C4C20FADBAA6E568FC22BADC890A8F6712844E51E2F036345CF05A2455 -> 955179C4C20FADBAA6E568FC22BADC890A8F6712844E51E2F036345CF0B3ED62
           ... :
  Thread 28672 : 955179C4C20FADBAA6E568FC22BADC890A8F6712844E51E2F036346A07DEFD99 -> 955179C4C20FADBAA6E568FC22BADC890A8F6712844E51E2F036346A0838C6A6
  Thread 28673 : 955179C4C20FADBAA6E568FC22BADC890A8F6712844E51E2F036346A0838C6A6 -> 955179C4C20FADBAA6E568FC22BADC890A8F6712844E51E2F036346A08928FB3
  Thread 28674 : 955179C4C20FADBAA6E568FC22BADC890A8F6712844E51E2F036346A08928FB3 -> 955179C4C20FADBAA6E568FC22BADC890A8F6712844E51E2F036346A08EC58C0
           ... :
  Thread 57342 : 955179C4C20FADBAA6E568FC22BADC890A8F6712844E51E2F03634914F211B7F -> 955179C4C20FADBAA6E568FC22BADC890A8F6712844E51E2F03634914F7AE48C
  Thread 57343 : 955179C4C20FADBAA6E568FC22BADC890A8F6712844E51E2F03634914F7AE48C -> 955179C4C20FADBAA6E568FC22BADC890A8F6712844E51E2F03634914FD4AD99
  Thread 57344 : 955179C4C20FADBAA6E568FC22BADC890A8F6712844E51E2F03634914FD4AD99 -> 955179C4C20FADBAA6E568FC22BADC890A8F6712844E51E2F0363491502E76A6

  [00:04:36] [955179C4C20FADBAA6E568FC22BADC890A8F6712844E51E2F036346209925603] [F: 0] [00:06:27] [C: 41.070166 %] [GPU: 513.54 Mk/s] [T: 138,579,804,160]
  =================================================================================
  PubAddress: 1KECKoV4CvqBeJaA1t7EgF2dYd4VQdHRfA
  Priv (WIF): p2pkh:5Jx3iVRtyaC2reGfta9UpXsshiNHRDrhUcBCg5GHgWyGoePGMMf
  Priv (HEX): 955179C4C20FADBAA6E568FC22BADC890A8F6712844E51E2F036345958325B50
  PubK (HEX): 04FA35DA91A41FF83CC228CBF6BFFFB3C8BC355ED2619A723807FDC72A036E241CFCEB66C998061569A1368CFFF26EB49FFEB173B773BF4195F15081FD86E6072C
  =================================================================================
  [00:04:37] [955179C4C20FADBAA6E568FC22BADC890A8F6712844E51E2F0363462274537B5] [F: 1] [00:06:38] [C: 41.209387 %] [GPU: 498.26 Mk/s] [T: 139,049,566,208]
[EXIT] Reached end of keyspace.

A lot faster than the original. The point, it all depends on where you start and end your range check, how many threads (GPU grid size), and how many keys per thread you let it run...basically, all luck LOL.

Same for random...all about luck:
Code:
Random Key :  955179C4C20FADBAA6E568FC22BADC890A8F6712844E51E2F0363476F71008B7
Random Key :  955179C4C20FADBAA6E568FC22BADC890A8F6712844E51E2F036344DF26E4057
Random Key :  955179C4C20FADBAA6E568FC22BADC890A8F6712844E51E2F0363443A12C64BA
Random Key :  955179C4C20FADBAA6E568FC22BADC890A8F6712844E51E2F036344432F7B979
 [00:00:05:27 Run Time][Total 402.10 MK/s][GPU 402.10 MK/s][Keys 125,015,425,024][Found 0][Rekeys: 52]
Random Key :  955179C4C20FADBAA6E568FC22BADC890A8F6712844E51E2F0363467AB2FE2CD
Random Key :  955179C4C20FADBAA6E568FC22BADC890A8F6712844E51E2F036346A0D558A17
Random Key :  955179C4C20FADBAA6E568FC22BADC890A8F6712844E51E2F03634477C8C176B
Random Key :  955179C4C20FADBAA6E568FC22BADC890A8F6712844E51E2F03634594BCE4713
 [00:00:05:33 Run Time][Total 405.69 MK/s][GPU 405.69 MK/s][Keys 127,364,235,264][Found 0][Rekeys: 53]
Random Key :  955179C4C20FADBAA6E568FC22BADC890A8F6712844E51E2F036348DCDC059D9
Random Key :  955179C4C20FADBAA6E568FC22BADC890A8F6712844E51E2F03634697D1FA73C
Random Key :  955179C4C20FADBAA6E568FC22BADC890A8F6712844E51E2F036346EF39E75BE
Random Key :  955179C4C20FADBAA6E568FC22BADC890A8F6712844E51E2F03634806C5BDEB9
 [00:00:05:40 Run Time][Total 402.13 MK/s][GPU 402.13 MK/s][Keys 129,713,045,504][Found 0][Rekeys: 54]
Random Key :  955179C4C20FADBAA6E568FC22BADC890A8F6712844E51E2F0363472C1A57BF6
Random Key :  955179C4C20FADBAA6E568FC22BADC890A8F6712844E51E2F0363470B288DF7B
Random Key :  955179C4C20FADBAA6E568FC22BADC890A8F6712844E51E2F0363465E6BED52D
Random Key :  955179C4C20FADBAA6E568FC22BADC890A8F6712844E51E2F036348C089BE450
 [00:00:05:46 Run Time][Total 402.13 MK/s][GPU 402.13 MK/s][Keys 132,061,855,744][Found 0][Rekeys: 55]
Random Key :  955179C4C20FADBAA6E568FC22BADC890A8F6712844E51E2F0363465209295A3
Random Key :  955179C4C20FADBAA6E568FC22BADC890A8F6712844E51E2F036344B182264D3
Random Key :  955179C4C20FADBAA6E568FC22BADC890A8F6712844E51E2F036344670439636
Random Key :  955179C4C20FADBAA6E568FC22BADC890A8F6712844E51E2F0363461955C1928
 [00:00:05:48 Run Time][Total 366.55 MK/s][GPU 366.55 MK/s][Keys 132,414,177,280][Found 0][Rekeys: 56]

PubAddress: 1KECKoV4CvqBeJaA1t7EgF2dYd4VQdHRfA
Priv (WIF): p2pkh: 5Jx3iVRtyaC2reGfta9UpXsshiNHRDrhUcBCg5GHgWyGoePGMMf
Priv (HEX): 955179C4C20FADBAA6E568FC22BADC890A8F6712844E51E2F036345958325B50 (256 bit)

It's key to watch and tinker with your GPU grid size. I increased the grid size to 996,512 (now more random starting points( and almost found key immediately.

Code:
VBCr v2.00
 Search For: 1KECKoV4CvqBeJaA1t7EgF2dYd4VQdHRfA [Uncompressed]
 Started on: Wed Jan 25 16:40:13 2023
 Randomness: New Random Keys Every 500 Mkeys
  Beg Range: 955179C4C20FADBAA6E568FC22BADC890A8F6712844E51E2F0363442BFCAC919 (256 bit)
  End Range: 955179C4C20FADBAA6E568FC22BADC890A8F6712844E51E2F03634914FD5846C (256 bit)
  Rng Width: 4E900ABB53 (39 bit)
CPU Threads: 0
GPU: GPU #0 NVIDIA GeForce GTX 1660 Ti (24x64 cores) Grid(996x512)

Random Key :  955179C4C20FADBAA6E568FC22BADC890A8F6712844E51E2F03634440236BA5C
Random Key :  955179C4C20FADBAA6E568FC22BADC890A8F6712844E51E2F0363473F8636EDD
Random Key :  955179C4C20FADBAA6E568FC22BADC890A8F6712844E51E2F0363449D8724FAE
Random Key :  955179C4C20FADBAA6E568FC22BADC890A8F6712844E51E2F036344C3A63B3A7
Random Key :  955179C4C20FADBAA6E568FC22BADC890A8F6712844E51E2F0363469E0C15E07
Random Key :  955179C4C20FADBAA6E568FC22BADC890A8F6712844E51E2F03634525862B5E4
Random Key :  955179C4C20FADBAA6E568FC22BADC890A8F6712844E51E2F036344E5C297011
Random Key :  955179C4C20FADBAA6E568FC22BADC890A8F6712844E51E2F036345F24EF3CAF
Random Key :  955179C4C20FADBAA6E568FC22BADC890A8F6712844E51E2F03634698D0832DD
 [00:00:00:02 Run Time][Total 255.40 MK/s][GPU 255.40 MK/s][Keys 522,190,848][Found 0][Rekeys: 0]
Random Key :  955179C4C20FADBAA6E568FC22BADC890A8F6712844E51E2F036346CB62AC27E
Random Key :  955179C4C20FADBAA6E568FC22BADC890A8F6712844E51E2F036344DDFEDEA8C
Random Key :  955179C4C20FADBAA6E568FC22BADC890A8F6712844E51E2F03634645F1412E8
Random Key :  955179C4C20FADBAA6E568FC22BADC890A8F6712844E51E2F03634526C416396
 [00:00:00:14 Run Time][Total 109.09 MK/s][GPU 109.09 MK/s][Keys 1,566,572,544][Found 0][Rekeys: 2]
Random Key :  955179C4C20FADBAA6E568FC22BADC890A8F6712844E51E2F036347B3373B27C
Random Key :  955179C4C20FADBAA6E568FC22BADC890A8F6712844E51E2F036344EC1D8291F
Random Key :  955179C4C20FADBAA6E568FC22BADC890A8F6712844E51E2F036345BF4F5E66E
Random Key :  955179C4C20FADBAA6E568FC22BADC890A8F6712844E51E2F03634759E5C49AA
 [00:00:00:26 Run Time][Total 94.95 MK/s][GPU 94.95 MK/s][Keys 2,610,954,240][Found 0][Rekeys: 4]
Random Key :  955179C4C20FADBAA6E568FC22BADC890A8F6712844E51E2F036347ECB3FB02F
Random Key :  955179C4C20FADBAA6E568FC22BADC890A8F6712844E51E2F0363442E4460541
Random Key :  955179C4C20FADBAA6E568FC22BADC890A8F6712844E51E2F0363458D7F1B2A3
Random Key :  955179C4C20FADBAA6E568FC22BADC890A8F6712844E51E2F03634521819396D
 [00:00:00:39 Run Time][Total 63.06 MK/s][GPU 63.06 MK/s][Keys 3,133,145,088][Found 0][Rekeys: 6]

PubAddress: 1KECKoV4CvqBeJaA1t7EgF2dYd4VQdHRfA
Priv (WIF): p2pkh: 5Jx3iVRtyaC2reGfta9UpXsshiNHRDrhUcBCg5GHgWyGoePGMMf
Priv (HEX): 955179C4C20FADBAA6E568FC22BADC890A8F6712844E51E2F036345958325B50 (256 bit)

Larger grid size with no rekey. Grid size of 2800x512 = 1,433,600 random starting points.:
Code:
VBCr v2.00
 Search For: 1KECKoV4CvqBeJaA1t7EgF2dYd4VQdHRfA [Uncompressed]
 Started on: Wed Jan 25 16:47:40 2023
  Beg Range: 955179C4C20FADBAA6E568FC22BADC890A8F6712844E51E2F0363442BFCAC919 (256 bit)
  End Range: 955179C4C20FADBAA6E568FC22BADC890A8F6712844E51E2F03634914FD5846C (256 bit)
  Rng Width: 4E900ABB53 (39 bit)
CPU Threads: 0
GPU: GPU #0 NVIDIA GeForce GTX 1660 Ti (24x64 cores) Grid(2800x512)

Random Key :  955179C4C20FADBAA6E568FC22BADC890A8F6712844E51E2F0363455F42F2ABF
Random Key :  955179C4C20FADBAA6E568FC22BADC890A8F6712844E51E2F036348B25B2E63D
Random Key :  955179C4C20FADBAA6E568FC22BADC890A8F6712844E51E2F0363473C50660E8
Random Key :  955179C4C20FADBAA6E568FC22BADC890A8F6712844E51E2F036346166A93286
Random Key :  955179C4C20FADBAA6E568FC22BADC890A8F6712844E51E2F0363442D4CF4323
Random Key :  955179C4C20FADBAA6E568FC22BADC890A8F6712844E51E2F03634585106710B
Random Key :  955179C4C20FADBAA6E568FC22BADC890A8F6712844E51E2F0363469763233B2
Random Key :  955179C4C20FADBAA6E568FC22BADC890A8F6712844E51E2F036344F1CC27871
Random Key :  955179C4C20FADBAA6E568FC22BADC890A8F6712844E51E2F03634594CD908EF
Random Key :  955179C4C20FADBAA6E568FC22BADC890A8F6712844E51E2F0363444E9EB7541Divide by 0!
 [00:00:00:45 Run Time][Total 534.52 MK/s][GPU 534.52 MK/s][Keys 23,488,102,400][Found 0][Rekeys: 0]

PubAddress: 1KECKoV4CvqBeJaA1t7EgF2dYd4VQdHRfA
Priv (WIF): p2pkh: 5Jx3iVRtyaC2reGfta9UpXsshiNHRDrhUcBCg5GHgWyGoePGMMf
Priv (HEX): 955179C4C20FADBAA6E568FC22BADC890A8F6712844E51E2F036345958325B50 (256 bit)

Smaller grid = faster counting but covers less of keyspace/range. Larger grid = slower counting but covers much more of the keyspace/range.

newbie
Activity: 49
Merit: 0
VBCR v2 ? which tool is this and where can we download ?

VBCR v2 on development stage.
If I'm not mistaken, it will soon be available for download here: https://github.com/WanderingPhilosopher/VanBitCrackenRandom2
hero member
Activity: 630
Merit: 731
Bitcoin g33k
VBCR v2 ? which tool is this and where can we download ?
full member
Activity: 1162
Merit: 237
Shooters Shoot...
As for right now, it's nearly impossible to brute force private keys. You literally need a quantum computer that will work 24/7 for that. So I think it's literally easier to just fish for the private keys.

Fishing for keys   Grin good one.

Depends on how many WIF chars are missing though. Right now you can brute force about 8 or 9 chars in about a month. There are ~40some characters in a WIF so this means roughly a fourth of a piece of paper. But it should be possible to brute force more chars with specialized ASICS (not the kind used in mining).
Can you explain what you mean by 40 characters?
L2Dxz8UtQhVhC7WAedJRnoHYnhawTukMerG2XTpUdRHNkpQX2Nw4

and

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.

As always, it depends on the program you are running and how much hardware you have.

I did a quick test, using random versus sequential (to make it a little harder lol). I took a WIF and removed the last 10 characters.
Results using 2 CPU threads:
Code:
VBCr v2.00
 Search For: 1KECKoV4CvqBeJaA1t7EgF2dYd4VQdHRfA [Uncompressed]
 Started on: Wed Jan 25 07:46:22 2023
 Randomness: New Random Keys Every 12 Mkeys
  Beg Range: 955179C4C20FADBAA6E568FC22BADC890A8F6712844E51E2F0363459551B7E08 (256 bit)
  End Range: 955179C4C20FADBAA6E568FC22BADC890A8F6712844E51E2F03634595B16042D (256 bit)
  Rng Width: 5FA8625 (27 bit)
CPU Threads: 2

Random Key :  955179C4C20FADBAA6E568FC22BADC890A8F6712844E51E2F036345955A6C694
 [00:00:00:04 Run Time][Total 4.38 MK/s][GPU 0.00 MK/s][Keys 18,593,792][Found 0][Rekeys: 0]
Random Key :  955179C4C20FADBAA6E568FC22BADC890A8F6712844E51E2F03634595721AF30
 [00:00:00:08 Run Time][Total 4.07 MK/s][GPU 0.00 MK/s][Keys 34,675,712][Found 0][Rekeys: 1]
Random Key :  955179C4C20FADBAA6E568FC22BADC890A8F6712844E51E2F036345959959C78
 [00:00:00:12 Run Time][Total 4.05 MK/s][GPU 0.00 MK/s][Keys 51,905,536][Found 0][Rekeys: 2]
Random Key :  955179C4C20FADBAA6E568FC22BADC890A8F6712844E51E2F03634595AB7901B
Random Key :  955179C4C20FADBAA6E568FC22BADC890A8F6712844E51E2F036345958324EB5

PubAddress: 1KECKoV4CvqBeJaA1t7EgF2dYd4VQdHRfA
Priv (WIF): p2pkh: 5Jx3iVRtyaC2reGfta9UpXsshiNHRDrhUcBCg5GHgWyGoePGMMf
Priv (HEX): 955179C4C20FADBAA6E568FC22BADC890A8F6712844E51E2F036345958325B50 (256 bit)

Random mode with GPU, last 11 WIF characters missing:
Code:
VBCr v2.00
 Search For: 1KECKoV4CvqBeJaA1t7EgF2dYd4VQdHRfA [Uncompressed]
 Started on: Wed Jan 25 08:03:32 2023
 Randomness: New Random Keys Every 8000 Mkeys
  Beg Range: 955179C4C20FADBAA6E568FC22BADC890A8F6712844E51E2F03634586BF10E6D (256 bit)
  End Range: 955179C4C20FADBAA6E568FC22BADC890A8F6712844E51E2F0363459C6B372C3 (256 bit)
  Rng Width: 15AC26456 (33 bit)
CPU Threads: 0
GPU: GPU #0 NVIDIA GeForce GTX 1660 Ti (24x64 cores) Grid(224x256)

Random Key :  955179C4C20FADBAA6E568FC22BADC890A8F6712844E51E2F0363458FE752AAE
Random Key :  955179C4C20FADBAA6E568FC22BADC890A8F6712844E51E2F036345912F5A494
Random Key :  955179C4C20FADBAA6E568FC22BADC890A8F6712844E51E2F0363458B9D40C67
Random Key :  955179C4C20FADBAA6E568FC22BADC890A8F6712844E51E2F0363458F572DCEB
Random Key :  955179C4C20FADBAA6E568FC22BADC890A8F6712844E51E2F036345934F3D458
Random Key :  955179C4C20FADBAA6E568FC22BADC890A8F6712844E51E2F0363458B905BD1E
Random Key :  955179C4C20FADBAA6E568FC22BADC890A8F6712844E51E2F03634593036E850
Random Key :  955179C4C20FADBAA6E568FC22BADC890A8F6712844E51E2F036345880B6304F
Random Key :  955179C4C20FADBAA6E568FC22BADC890A8F6712844E51E2F0363459299B92F6
 [00:00:00:02 Run Time][Total 487.65 MK/s][GPU 487.65 MK/s][Keys 998,244,352][Found 0][Rekeys: 0]

PubAddress: 1KECKoV4CvqBeJaA1t7EgF2dYd4VQdHRfA
Priv (WIF): p2pkh: 5Jx3iVRtyaC2reGfta9UpXsshiNHRDrhUcBCg5GHgWyGoePGMMf
Priv (HEX): 955179C4C20FADBAA6E568FC22BADC890A8F6712844E51E2F036345958325B50 (256 bit)
legendary
Activity: 1568
Merit: 6660
bitcoincleanup.com / bitmixlist.org
As for right now, it's nearly impossible to brute force private keys. You literally need a quantum computer that will work 24/7 for that. So I think it's literally easier to just fish for the private keys.

Fishing for keys   Grin good one.

Depends on how many WIF chars are missing though. Right now you can brute force about 8 or 9 chars in about a month. There are ~40some characters in a WIF so this means roughly a fourth of a piece of paper. But it should be possible to brute force more chars with specialized ASICS (not the kind used in mining).
sr. member
Activity: 873
Merit: 268
As for right now, it's nearly impossible to brute force private keys. You literally need a quantum computer that will work 24/7 for that. So I think it's literally easier to just fish for the private keys.
legendary
Activity: 1568
Merit: 6660
bitcoincleanup.com / bitmixlist.org
--snip--
What is the risk of using root? Good thing I was unable to execute the given commands on that site, sometimes ignorance is a friend.😄

Using root to execute application is equal to giving application full access to your device. In this case, the risk is depends on whether CryptoXploit modify the binary/source to perform malicious task. Although in general, few non-malicious application would either refuse to run or cannot run properly.

There is no reason to run any computational program as root or administrator as all you will accomplish is making it easier for hackers to infect your system with phony copies of the software. You should actually run it from within a jail so that it can't gain any privileges with `sudo` or other stuff.
copper member
Activity: 1330
Merit: 899
🖤😏
How to run BitCrack with linux

As detailed as possible here: cryptoxploit[dot]com/bitcrack/#

How did you find this guide? I did quick seems and few things seems to be fishy (or at least unusual),
1. This guide perform git clone from his own repository, not https://github.com/brichard19/BitCrack.
2. His repository seems provide both binary executable (for Windows) and source code inside compressed file.
3. The guide lack few detail (e.g. which linux distro is used and why the guide use user root on Linux).
What is the risk of using root? Good thing I was unable to execute the given commands on that site, sometimes ignorance is a friend.😄
copper member
Activity: 1330
Merit: 899
🖤😏
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
member
Activity: 628
Merit: 17
legendary
Activity: 1568
Merit: 6660
bitcoincleanup.com / bitmixlist.org
How to run BitCrack with linux

You have to compile BitCrack from source code. In past i tried to run compiled .exe with Wine, but i experience few problem. With cuBitCrack.exe, i receive error about missing .dll for CUDA library. As for clBitCrack.exe, it failed to detect any device even though i already install OpenCL device.

Why would someone try to run a performance program through WINE anyway. That's just dumb. Even if the CUDA or OpenCL drivers do manage to get emulated, the performance will be greatly inferior to the native alternative.
newbie
Activity: 2
Merit: 0
How to run BitCrack with linux
legendary
Activity: 2534
Merit: 6080
Self-proclaimed Genius
The program is no longer functional. Even though I double-tap the Bitcrack64 record, the software ends. My outdated GTX 1050ti is collecting dust. I could use it again.
-snip-
Those executables aren't supposed to be double-clicked, you need to run it in a command line.
If you're using Windows, that's either your "Command Prompt" or "PoweShell".

Also, "BitCrack64.exe" is only available in the very old version, the latest only has the OpenCL and Cuda versions (go to releases for the updated binaries)
Then, use "cuBitCrack.exe" instead.
full member
Activity: 1162
Merit: 237
Shooters Shoot...
Darn, I installed CUDA, now my RAM doesn't show GDDR5 in task manager, my GPU meter used to show temperature, but now it doesn't show that. Lol what have I done.

Did you install the correct CUDA version for your NVIDIA card?

When you install CUDA, it replaces your GeForce/Quadro drivers with CUDA-bundled ones. It's quite a mess, I admit.

That's what happens when your video card market consists of 2 or 3 vendors only.
I'm not sure if it was the right one, however I'm using unigine benchmark tool for now, might reinstall my old drivers and compare the results.
I just wanted a executable, I had to install VS CUDA, spending 2 days to figure out what compiling, building actually is.🤣
You don't have to download the whole cuda package, you can run the exe in a folder with vcruntime, nvrtc, and msvcp .dll(s) files inside the same folder.

For the CUDA10.props error; you can change your props inside the VS code to whatever props you have, such as 10.1, 10.2, 11, etc.
copper member
Activity: 1330
Merit: 899
🖤😏
Darn, I installed CUDA, now my RAM doesn't show GDDR5 in task manager, my GPU meter used to show temperature, but now it doesn't show that. Lol what have I done.

Did you install the correct CUDA version for your NVIDIA card?

When you install CUDA, it replaces your GeForce/Quadro drivers with CUDA-bundled ones. It's quite a mess, I admit.

That's what happens when your video card market consists of 2 or 3 vendors only.
I'm not sure if it was the right one, however I'm using unigine benchmark tool for now, might reinstall my old drivers and compare the results.
I just wanted a executable, I had to install VS CUDA, spending 2 days to figure out what compiling, building actually is.🤣
legendary
Activity: 1568
Merit: 6660
bitcoincleanup.com / bitmixlist.org
Darn, I installed CUDA, now my RAM doesn't show GDDR5 in task manager, my GPU meter used to show temperature, but now it doesn't show that. Lol what have I done.

Did you install the correct CUDA version for your NVIDIA card?

When you install CUDA, it replaces your GeForce/Quadro drivers with CUDA-bundled ones. It's quite a mess, I admit.

That's what happens when your video card market consists of 2 or 3 vendors only.
Pages:
Jump to: