keyhunt not good
you should learn to configure it, defaul thread subrange is 32 bits, for small ranges with multiple threads you should lower the N value with "-n number" if the range is less than 1 Million keys you should use -n 0x10000
where 0x10000 its a 16 bits subrange per thread
Look
https://talkimg.com/images/2024/05/21/1iVIH.pngFound i less than a second
are you key hunt creator?
nice too meet you
It was my mistake, I apologize, dear friend
ok , thank you
I meant
https://github.com/WanderingPhilosopher/KeyHuntCudaClienti use of first version keyhunt cuda
Zero clues of how or what you ran, but with a single CPU core, using keyhunt-cuda, it is found pretty much as the program starts:
KeyHunt-Cuda v1.08
COMP MODE : COMPRESSED
COIN TYPE : BITCOIN
SEARCH MODE : Single Address
DEVICE : CPU
CPU THREAD : 1
SSE : YES
RKEY : 0 Mkeys
MAX FOUND : 65536
BTC ADDRESS : 1E5V4LbVrTbFrfj7VN876DamzkaNiGAvFo
OUTPUT FILE : Found.txt
Start Time : Sat May 25 10:11:49 2024
Global start : 20000000000000000 (66 bit)
Global end : 21000000000000000 (66 bit)
Global range : 1000000000000000 (61 bit)
[00:00:02] [CPU+GPU: 5.28 Mk/s] [GPU: 0.00 Mk/s] [C: 0.000000 %] [R: 0] [T: 10,706,944 (24 bit)] [F: 1]
BYE
SO maybe you entered wrong things/flags when trying to run the program.
this is 1 milion key after start 200000000000f4240
and this is p2ph compressed public key : 1E5V4LbVrTbFrfj7VN876DamzkaNiGAvFo
KeyHunt-Cuda.exe -t 0 -g --gpui 0 --gpux 24,256 -m address --coin BTC --range 20000000000000000:40000000000000000 1E5V4LbVrTbFrfj7VN876DamzkaNiGAvFo
my keyhunt cuda speed is 60 Mk/s . In fact, Cuda should find it in less than 1 second, but it takes about 1:40 minute
KeyHunt-Cuda.exe -t 0 -g --gpui 0 --gpux 24,256 -m address --coin BTC --range 20000000000000000:40000000000000000 1E5V4LbVrTbFrfj7VN876DamzkaNiGAvFo
KeyHunt-Cuda v1.07
COMP MODE : COMPRESSED
COIN TYPE : BITCOIN
SEARCH MODE : Single Address
DEVICE : GPU
CPU THREAD : 0
GPU IDS : 0
GPU GRIDSIZE : 24x256
SSE : YES
RKEY : 0 Mkeys
MAX FOUND : 65536
BTC ADDRESS : 1E5V4LbVrTbFrfj7VN876DamzkaNiGAvFo
OUTPUT FILE : Found.txt
Start Time : Sun May 26 14:04:50 2024
Global start : 20000000000000000 (66 bit)
Global end : 40000000000000000 (67 bit)
Global range : 20000000000000000 (66 bit)
GPU : GPU #0 Quadro P1000 (4x128 cores) Grid(24x256)
[00:01:36] [CPU+GPU: 62.21 Mk/s] [GPU: 62.21 Mk/s] [C: 0.000000 %] [R: 0] [T: 5,976,883,200 (33 bit)] [F: 0]
The problem is that Cuda performs the same task in all graphics cores in parallel and repetitively, and instead of the cores each helping the program, each of them repeats the same task as an island, for example, each core in parallel from the same start. He does and moves forward. And maybe in the best case, it divides the entire collection into the number of cores and each core starts working in that interval, in this case, once you exit the program, all your efforts will end in an unknown place, which will be used the next time you run the program. You don't know where to start
