That's right, if you search for only for puzzle addresses which are compress public key then compress mode is where to go!
Thanks again 7isce!
Before buying a faster cpu i want to understand well how keyhunt works (i use version 0.2.211012 chocholate beta) and how to obtain the best performance.
I did several
random tests to identify
which is the better thread value (-t).
My cpu is an Intel Core i7-4500U 1,80-3,00Ghz (2 cores 4 threads)
Is it possible to calculate the best -t value from the cpu specifications?
I could ipotize 4 but it's not correct.
Let's see my tests statistic with a keyspace of 1.000.000.000 keys on puzzle 64 in
rmd106 mode (consider that the highest keys/s value takes 3-6 minutes):
-t 16 = 1.360.000 keys/s
-t 96 = 2.270.000.000 keys/s
-t 160 = 2.800.000-3.000.000 keys/s (found privkey in less than 6 minutes after 1020 million keys examined)
-t 192 = 3.000.000-3.300.000 keys/s (found privkey in less than 4 minutes after 804 million keys examined)
-t 208 = 3.300.000-3.600.000 keys/s (found privkey in less than 10.5 minutes after 2300 million keys examined)
-t 216 = 3.300.000-3.700.000 keys/s (found privkey in less than 7 minutes after 1585 million keys examined)
-t 220 = 3.300.000-3.500.000 keys/s (found privkey in less than 3.5 minutes after 692 million keys examined)
-t 224 = 3.600.000-3.900.000 keys/s (found privkey in less than 4 minutes after 872 million keys examined)
-t 228 = 3.500.000 keys/s (found privkey in less than 1 minute after 95 million keys examined)
-t 230 = 3.200.000 keys/s (found privkey in less than 1 minute after 74 million keys examined)
-t 256 = 3.500.000-3.800.000 keys/s (found privkey in less than 3.5 minute after 805 million keys examined)
-t 512 = 500.000 keys/s (found privkey in less than 3 minutes after 96 million keys examined)
-t 1024 = 700.000 keys/s (found privkey in less than 13 minutes after 515 million keys examined)
Sometime happened that that the key has been found in less than a minute, of course i skipped these tests results because the keys/s number was not readable.
Was it possible to get the 224 with a calculation considering the cpu specs?
Do you think that with a larger keyspace (for ex. 1.000.000.000.000 keys) the - t value statistic could be different for the keys/s?
Another question: to use
bsgs mode with keyhunt we need to write in the .txt file the pubkey in the long format.
In puzzle 64 the long format is : 03100611c54dfef604163b8358f7b7fac13ce478e02cb224ae16d45526b25d9d4d
But we haven't it for puzzle 66!!!
So to get it with keyhunt there is the
pub2rmd mode.
But why should i spend time to use the pub2rmd and only after (IF i get the pubkey) use the bsgs mode to get the privkey?
It seems faster to use the rmd160 mode and wait the privkey directly. Am i wrong?
Have you found the pubkey of puzzle 66???