SexObIllo , find privkey for this and I give you 0.6 Btc ??

1:124bff742a76f92fa3a76f8f6552f

0313ee32399b1441d0c8cf7caf6d10641b30d280fe1b59fcaa09eb0326cad5cb6f

0213ee32399b1441d0c8cf7caf6d10641b30d280fe1b59fcaa09eb0326cad5cb6f

A prototype in work. Solves an 84 bit range search in under 1 minute, but cannot solve 85 bits for some reason! More work tomorrow. It is something in the GPU...more troubleshooting!
It does not work above 84 bit range. It is not for sale nor available to test. If I ever get it to work right, will use in the pool for the larger challenges with x points exposed.

CPU walks the baby steps with DP method (with limit setting). GPU burns through the range with giant steps, looking for collisions.

Try my pubkeys....

Try run your cangaroo again, and you find 85 bit. Kangaroo and BSGS some time need run again for find a key as show my practice.

lol , i read what you say and understand as well , just i asked  if you like to share  send me codes so will try to fix bug and do optimization ,

I apologize in advance for asking, but is it possible to check which of  two points is greater? k number of one point is known.

What is the "k" number?

In other words, the shorthand for the private key.

It is indeed a number between the same range of the private key's, but it's not the private key unless I'm missing something. The value k is the one which if multiplied by G you get r where signature is [r, s]. The private key is d and the public key is dG.

At least that's how I've studied them. They're just names, but they may bring confusion if we don't decide which designation we'll all consider correct.