Quote from: WanderingPhilospher on Today at 07:12:19 AM

Quote from: COBRAS on Today at 07:08:42 AM

Quote from: WanderingPhilospher on Today at 06:58:53 AM

Quote from: COBRAS on July 05, 2020, 03:37:39 PM

Quote from: Etar on July 05, 2020, 03:34:33 PM

Quote from: COBRAS on July 05, 2020, 03:28:00 PM

-snip-
Bro, Your code is making what is described there https://bitcointalk.org/index.php?topic=5238719.msg54296078#msg54296078 or something else ?

Python code do exactly what you need (substract startrange from public key). After you will find key, just add to key your startrange and you will get correct PK.

Big Thank You Bro !!!

@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:

Code:

0000000000000000000000000000000000000000000000001xxxxxxxxxxxxxxx

(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

Code:

0000000000000000000000000000000000000000000000001xxxxxxxxxxxxxxx

range. Let's go.

Hello

Endomorphism perate 1rpivkeyPt/2 bytes * 2 !!! So endomorhpism not operate not split ranges.

Bro, this is

0000000000000000000000000000000000000000000000001xxxxxxxxxxxxxxx

a ranges for kids bro

what you say about ranges for ex

1000000000000000000000000000000000000000000000001xxxxxxxxxxxxxxx
4000000000000000000000000000000000000000000000001xxxxxxxxxxxxxxx
8000000000000000000000000000000000000000000000001xxxxxxxxxxxxxxx
F000000000000000000000000000000000000000000000001xxxxxxxxxxxxxxx

Yous see ? real keys are not 65 bytes bro

Kid or not, I am just telling you the python script offsetting the pubkey with starting range is not going to help you with a range such as:

Code:

1000000000000000000000000000000000000000000000001xxxxxxxxxxxxxxx
4000000000000000000000000000000000000000000000001xxxxxxxxxxxxxxx
8000000000000000000000000000000000000000000000001xxxxxxxxxxxxxxx
F000000000000000000000000000000000000000000000001xxxxxxxxxxxxxxx

But it will for the smaller, "kid" ranges.
Also, if 0000000000000000000000000000000000000000000000001xxxxxxxxxxxxxxx is kid range, then there is an easy .64 bitcoin waiting for you

Ok Bro, help me fined privkey to this pubkey:

04eb838fb6782028a5adfc4082e52f30341ad2c0b3571ed8082062304a11eddeeb6d72b07bdf5c9 40efeeaa7f91e5a2552f632bb20e2744720973b26b4d16c61af

Huh

?