Quote from: btcmitko on Today at 05:24:06 PM

Quote from: vhh on Today at 04:21:18 PM

Quote from: citb0in on Today at 06:06:17 AM

Quote from: batareyka on Today at 05:58:04 AM

There is even a way to find out the range in which the key is located, ...

Really? So tell us what the range is where #66 is lying

Not to be a smart pants, but the question is silly and the answer will follow the question : #66 lies somewhere between 0x20000000000000000 and 0x3ffffffffffffffff .

Quote from: albert0bsd on Today at 03:12:12 PM

Quote from: GoldTiger69 on Today at 03:01:14 PM

If you can determine the range of the private key from it's public key, ECC is broken. So, I don't believe that, yet.

Exactly, to determine the range, it mean determine one single bit position and that with the correct math operations can solve any key, so it is hard to believe

Totally agree with GoldTiger69 and albert0bsd here! One single bit position will break ECC!

Here is a pubkey 03995B8A5AD00A205BFB9837014E2978273B816CFB29CA9644AB6D44977C006C64

The first bit of the private key is 1

I will even give you range 2^144-2^145

Come on break the ECC with that bit.....

Sure : follow the same logic / algorithm that you applied when you discovered that the first bit is 1.

Nobody poses such an algorithm as we speak, modular math forbids it.