Quote from: zahid888 on Today at 03:37:25 PM

Quote from: WanderingPhilospher on Today at 03:21:48 PM

Quote from: zahid888 on March 19, 2025, 10:08:11 PM

Per core, I'm getting 4.8 MK/s with single Base58 address… Maybe that's close to Hash160 speed. @Nomachine, may i know the speed of a single core with Hash160?

Where was the 4.8 MK/s at? I saw a bunch of 2 MK/s speeds. Maybe you did not show that part? And you only get that speed if you only search 1 address at a time?

Yes 4.8 MK/s with single bas58_address

Quote from: WanderingPhilospher on Today at 03:21:48 PM

Also, your bit mechanism seems broken. If you are searching in 69, but you have 68 ranges in your saved progress, that seems broken. Or am I missing something and that video has nothing to do with your comments/questions lol.

May be you are not notice in video i set -sbl(start bit length) to 68 and -ebl(end bit length) to 69 that is why you see 69 and 68 both bitrange key in process_save.txt for only 68 its required -sbl 68 and -ebl 68... you can see this when i search for puzzle 25 in video..

Quote from: Ovixx on Today at 10:13:48 AM

Interesting your executable! I would like to test it. Have you published it somewhere, or you don't want to share it?

Not yet

maybe soon Roll Eyes

Ok, yeah, I missed some of those things. But regarding the 4.8 MK/s what am I missing there? What do you get on a standard public program like keyhunt-cuda or VS range limited version? I get 5 MK/s with out of the box keyhunt-cuda for address search on a single core.

Seems like you took cyclone or some other program and just added functionality to it versus changing the math or other type of real speed up. But it is early/late so maybe I missed something else too, especially since I am using my RDP to try and get a hint on the exact keyspace for 68