I would like to look at other keys (unknownhostname has too much cpu power)
time ./gen-hrdcore-avx2-linux64 -I 0000000000000000000000000000000000000000000000000000000000000001 -c 10000 -L 8
what stand for options "-c" and "-L" ?
-c is the challenge. 10000 is for testing purposes (normally you can see the challenges if you look at the process table when LBC is running)
-L is the number of loops = number of times 16,7 Mkeys consecutive blocks search to perform
if you want to check individual keys, LBC -p is a way better option:
https://lbc.cryptoguru.org/man/user#manual-modeas you can give them in binary form, LBC correctly "snaps" the key range into block boundary form and you can give a from-to range without having to worry about the loops or challenges. You can even mix hexadecimal and binary from-to parameters. And even key and block numbers. I had an attack of genericity when implementing that.
If you are afraid not to give away any information about privkeys, either pull the network plug, or simply give the "to" parameter with some more distance and end the LBC hard with Ctrl+C before it ends.
With the -p parameter, LBC does not even send a promise (to do work) to the server and if you end it hard before the work is done, it does not send its PoW -> as if it never happened.
edit: But not sending PoW will of course freeze your stats. So unless you are testing privkeys you do not want to disclose, send the PoW.
Rico
