@COBRAS, this code is not going to help you the way you think it might. You still have to know the starting range in order for it to help you, and with larger ranges, it will not help you at all, even if you know the starting range. Large range in what I think you are looking at, 2^256...it will not help you so do not waste time using the code and searching. It's not going to split the range in half, so you will not go from 2^256 to 2^128.
Now, what it can do, and what I can do with it, is split search time dramatically with smaller ranges.
Anyone can challenge, set up a test. I've seen several posts stating it doesn't help reduce search time but it does.
Test:
Someone create a random private key in let's say this range:
(keep it small so it's not a long test)
Once you've generated the private key in that range, find the public key and post it here.
Running CPU only, I bet I can find the private key in half the time than it would normally take someone else just running Kangaroo alone. I will post results of my time versus anyone else's time, running Kangaroo only.
COBRAS, I just don't want you wasting any time thinking it will cut range in half. JP says there is a quick mod to increase the Kangaroo search range from 128 to 256. I'd ask him what to do code wise, versus doing anything else.
Someone post pub key in the
range. Let's go.