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

I don't work in Windows so I'm not sure how to do it.
Your CCAP value is "86". the default value "75" will not working.

I done a lot of test for gridsize and the result is that the default one that generate by Keyhunt (when you remove --gpux arrangement) is the best one.
So keep it empty and relax

wait up, take my medicine for headache first...  
any other easier way to understand?
what command do i have to write for 8xrtx3070ti, so this job can be done.  

btw what is the use of --gpux GPU gridsize: g0x,g0y,g1x,g1y,... : Specify GPU(s) kernel gridsize, default is 8*(Device MP count),128
and how can i use it?

You must change CCAP to match your GPU or otherwise will not working properly.
You can find CCAP value for your GPU in
here: https://github.com/oladas/ccminer/wiki/Compatibility
or here: https://arnon.dk/matching-sm-architectures-arch-and-gencode-for-various-nvidia-cards/

i didn't change any gpu value, except change setting on afterburner  to undervolt my gpu.

Did you change CCAP value to match your GPU CCAP?

after running awhile this problem occur :
"cudaSafeCall() failed at D:/PROGRAMMING/VisualStudioProjects/KeyHunt-Cuda-GIT-2017/KeyHunt-Cuda/KeyHunt-Cuda/GPU/GPUEngine.cu:686 : an illegal memory access was encountered'.
then stop,.. why is this? is it because lack of virtual memory?

https://askubuntu.com/questions/999509/which-cuda-cudnn-nvidia-versions-to-install-for-deep-learning

The link says:
Your Geforce 820M GPU has a CUDA compute capability of 2.1 (see Intel geforce gpu list This capability is too low for CUDA 9.0+, but does support CUDA 8.0. Try installing that CUDA version.

https://developer.nvidia.com/cuda-gpus#compute

 

I did the fast 260.000 keyspace test with the "main" desktop computer that i use for internet  
In the old laptop that i use for quite all the tests there is a Nvidia Geforce 820M with 2Gb.
There is Nvidia Cuda 8.0.0 driver installed (NVCUDA.dll)

C:\BitCrack>clbitcrack -o out.txt --keyspace f7051f27b08d1000:f7051f27b09112d4 16jY7qLJnxb7CHZyqBP8qca9d51gAjyXQN
[2022-10-03.08:32:22] [Info] Compression: compressed
[2022-10-03.08:32:22] [Info] Starting at: 000000000000000000000000000000000000000000000000F7051F27B08D1000
[2022-10-03.08:32:22] [Info] Ending at:   000000000000000000000000000000000000000000000000F7051F27B09112D4
[2022-10-03.08:32:22] [Info] Counting by: 0000000000000000000000000000000000000000000000000000000000000001
[2022-10-03.08:32:22] [Info] Compiling OpenCL kernels...
[2022-10-03.08:32:23] [Info] Initializing GeForce 820M
[2022-10-03.08:32:23] [Info] Generating 262,144 starting points (10.0MB)
[2022-10-03.08:32:24] [Info] 10.0%
[2022-10-03.08:32:25] [Info] 20.0%
[2022-10-03.08:32:26] [Info] 30.0%
[2022-10-03.08:32:26] [Info] 40.0%
[2022-10-03.08:32:27] [Info] 50.0%
[2022-10-03.08:32:27] [Info] 60.0%
[2022-10-03.08:32:28] [Info] 70.0%
[2022-10-03.08:32:29] [Info] 80.0%
[2022-10-03.08:32:29] [Info] 90.0%
[2022-10-03.08:32:30] [Info] 100.0%
[2022-10-03.08:32:30] [Info] Done
[2022-10-03.08:32:30] [Info] Found key for address '16jY7qLJnxb7CHZyqBP8qca9d51gAjyXQN'. Written to 'out.txt'
[2022-10-03.08:32:30] [Info] No targets remaining
[2022-10-03.08:32:30] [Info] Reached end of keyspace

C:\BitCrack>

unfortunate there is no arrangement for that job.
But you can redirect all output to file like ./Keyhunt .... > save/file1.txt
So you can keep track of progress status and if any thing happen then you just edit the start range+last progress status

i mean, is it any command that can be use if something happen, lets say like electric out, so it dont have to start all over again.
just like cubitcrack has it (--continue FILE)

I don't get it, Can you explain more?

does keyhunt-cuda has restore point command?

Clbitcrack is support both CPU and GPU.
From what I see in your result that you have the Intel GPU not Nvidia GPU so you can't run KeyHunt-Cuda because Cuda is for Nvidia GPU only.

prefix is mean start with. you can use it for search key start with puzzle address "1LeBZP5QC"
Or you can search for special address for yourself like address start with 1italiandigger

Clbitcrack detect my gpu, does it mean that it use gpu and cpu together? or gpu only? or cpu only? you see from the same test, it's faster than keyhunt.

About VanitySearch i don't understand well what does it mean:

As you can see, even with a competitive hardware, it is very unlikely that you find a collision. Birthday paradox doesn't apply in this context, it works only if we know already the public key (not the address, the hash of the public key) we want to find. This program doesn't look for collisions between public keys. It searchs only for collisions with addresses with a certain prefix.

We don't know the puzzle 66 pubkey.. we know only the address.

Collisions with addresses with a certain prefix??? 

For keyhunt-cuda you must run either GPU OR CPU(both is not supported)
"CPU and GPU can not be used together, because the program divides the whole input range into equal parts for all the threads, so use either CPU or GPU so that the whole range can increment by all the threads with consistency."

If you want to run both then use https://github.com/JeanLucPons/VanitySearch/

In conclusion Clbitcrack (0.30 version) complete the 100 billions keyspace test 45 minutes sooner than Keyhunt, because clbitcrack uses gpu+cpu and keyhunt the cpu only.

5.37Mkey/s against 3.99MKey/s on my laptop.  

A pity that clbitcrack doesn't work random.

Now i wait to test the cubitcrack and keyhunt-cuda (cpu+gpu) to see if it's faster than clbitcrack.
Let's see if i can solve my CUDA laptop problems.  

With clbitcrack (0.30) and my old laptop all the puzzle 64 keyspace can be completed in 210579 years  
Random becomes an obligatory choice, i presume.

Good news for Keyhunt-cuda (cpu only) too, the 100.000.000.000 keyspace test has been fullfilled fine in less than 6 hours.

C:\Keyhunt>KeyHunt-Cuda.exe -t 4 --gpui 0 -m addresses --coin BTC --range f7051f1d195d2800:f7051f3461d41000 -i puzzle64.bin

KeyHunt-Cuda v1.08

COMP MODE    : COMPRESSED
COIN TYPE    : BITCOIN
SEARCH MODE  : Multi Address
DEVICE       : CPU
CPU THREAD   : 4
SSE          : YES
RKEY         : 0 Mkeys
MAX FOUND    : 65536
BTC HASH160s : puzzle64.bin
OUTPUT FILE  : Found.txt

Loaded       : 1 Bitcoin addresses

Bloom at 000001DF33F13E20
  Version    : 2.1
  Entries    : 2
  Error      : 0.0000010000
  Bits       : 57
  Bits/Elem  : 28.755175
  Bytes      : 8 (0 MB)
  Hash funcs : 20

Start Time   : Sun Oct  2 10:47:02 2022
Global start : F7051F1D195D2800 (64 bit)
Global end   : F7051F3461D41000 (64 bit)
Global range : 174876E800 (37 bit)


[05:43:55] [CPU+GPU: 3.99 Mk/s] [GPU: 0.00 Mk/s] [C: 81.867672 %] [R: 0] [T: 81,867,671,552 (37 bit)] [F: 0]
=================================================================================
PubAddress: 16jY7qLJnxb7CHZyqBP8qca9d51gAjyXQN
Priv (WIF): p2pkh:KwDiBf89QgGbjEhKnhXJuH7LrciVrZi3qZ6FxoaD5r1kYegmtbaT
Priv (HEX): F7051F27B09112D4
PubK (HEX): 03100611C54DFEF604163B8358F7B7FAC13CE478E02CB224AE16D45526B25D9D4D
=================================================================================
[05:43:57] [CPU+GPU: 3.99 Mk/s] [GPU: 0.00 Mk/s] [C: 81.875855 %] [R: 0] [T: 81,875,855,360 (37 bit)] [F: 1]

BYE

C:\Keyhunt>

Just tried clbitcrack 3.0 (not the 3.1) and it works fine over the 260.000 keys of keyspace!  
https://github.com/brichard19/BitCrack/releases/tag/0.30

C:\>cd bitcrack

C:\BitCrack>clbitcrack -o out.txt --keyspace f7051f27b08d1000:f7051f27b09112d4 16jY7qLJnxb7CHZyqBP8qca9d51gAjyXQN
[2022-10-02.16:08:18] [Info] Compression: compressed
[2022-10-02.16:08:18] [Info] Starting at: 000000000000000000000000000000000000000000000000F7051F27B08D1000
[2022-10-02.16:08:18] [Info] Ending at:   000000000000000000000000000000000000000000000000F7051F27B09112D4
[2022-10-02.16:08:18] [Info] Counting by: 0000000000000000000000000000000000000000000000000000000000000001
[2022-10-02.16:08:18] [Info] Compiling OpenCL kernels...
[2022-10-02.16:10:02] [Info] Initializing Intel(R) UHD Graphics 605
[2022-10-02.16:10:02] [Info] Generating 262,144 starting points (10.0MB)
[2022-10-02.16:10:08] [Info] 10.0%
[2022-10-02.16:10:15] [Info] 20.0%
[2022-10-02.16:10:20] [Info] 30.0%
[2022-10-02.16:10:26] [Info] 40.0%
[2022-10-02.16:10:32] [Info] 50.0%
[2022-10-02.16:10:38] [Info] 60.0%
[2022-10-02.16:10:44] [Info] 70.0%
[2022-10-02.16:10:49] [Info] 80.0%
[2022-10-02.16:10:55] [Info] 90.0%
[2022-10-02.16:11:01] [Info] 100.0%
[2022-10-02.16:11:01] [Info] Done
[2022-10-02.16:11:01] [Info] Found key for address '16jY7qLJnxb7CHZyqBP8qca9d51gAjyXQN'. Written to 'out.txt'
[2022-10-02.16:11:01] [Info] No targets remaining
[2022-10-02.16:11:01] [Info] Reached end of keyspace

C:\BitCrack>

I think this unfair comparison.
Keyhunt is build for CPU only and it very optimize for that purpose.
Keyhunt-cuda is fork from VanitySearch by JeanLucPons. Its fully focus on GPU and the just keep the CPU because its work by inherited it So they decided to keep it.
You need to test Keyhunt-cuda on GPU to have a fair comparison.

Hi 7isce, i've looked the video until the end with interest.
From my last two tests (and according with the old tests with keyhunt) i can say that the random algorithm is different in keyhunt.exe and keyhunt-cuda.exe!
The random of keyhunt-cuda, using the language of the YT video, repeats MUCH MORE than keyhunt the possible candidate solution and it's evident from the number of iterations, and so it takes much more time to complete the process.
Keyhunt-cuda goes far below the 63% of probaility to get the reach of the solution before the end of keyspace.
Keyhunt probability is around the 63% and more until 99%, you can see it from the tests of 1.000.000.000 keys of keyspace done in my previous post, all before the 10 minutes (usually around the 1.000.000.000 keys examined).
Do you agree?

In conclusion from my tests:
Keyunt.exe works fine in the random mode.
Keyhunt-cuda.exe (cpu) works fine and faster only in secuential mode.