Help please find a short (I apologise not more 26-64 byts) privatekey ?

[COBRAS]

I need find a privkey for this address:

026923e0e37ab6797deb3fd486ccc5616f29b6024b88372ae762e748e0b9d903a1

046923e0e37ab6797deb3fd486ccc5616f29b6024b88372ae762e748e0b9d903a1d783cdb52c91a 8413b879b42d78e57b55fee79121105fe86f19e47cf88cb08ba

Unfortunately I have no GPU now, whats why I looking for help. This is a screen of my progress    https://ibb.co/Xs5kP8r

This public key differs from the base point of the SECP256k1 curve quite a bit, so I assume that the private key is very small.

This private key is a necessary intermediate step in my task. If I manage to solve the whole problem in the future(it requires 1-2 additional actions after finding this private key) then I will thank three people who responded and helped with a some amount in bitcoins.


Please, those who will be engaged in the search write in this thread about the beginning of the search.


Thx a lot.

[Kostelooscoin]

i see for you

[COBRAS]

i see for you

Thank YOU Bro !!!

I will waiting any news from you 

[WanderingPhilospher]

BSGS says the key is NOT in the 0-64 bit range...

[COBRAS]

BSGS says the key is NOT in the 0-64 bit range...

fuck ((( Interesting why ((((((

Bro, try please max range what you thant(can do) ?

[COBRAS]

BSGS says the key is NOT in the 0-64 bit range...

fuck ((( Interesting why ((((((

Bro, try please max range what you thant(can do) ?

Base points coordinates is

DEC:

x - 55066263022277343669578718895168534326250603453777594175500187360389116729240

y - 32670510020758816978083085130507043184471273380659243275938904335757337482424


mypubkey(Q)

x- 55066364869024817002202674482993163092766258607206729045322400651809226176411

y - 32714787012288702374484989837137541040814237973437713939282832421332403071190


BP(x)-Q(x) = 55066263022277343669578718895168534326250603453777594175500187360389116729240  

-

55066364869024817002202674482993163092766258607206729045322400651809226176411

= 101846747473332623955587824628766515655153429134869822213291420109447171

BP(y)-Q(y)= 32714787012288702374484989837137541040814237973437713939282832421332403071190

-

                   32670510020758816978083085130507043184471273380659243275938904335757337482424

=                 44276991529885396401904706630497856342964592778470663343928085575065588766

SQRT(44276991529885396401904706630497856342964592778470663343928085575065588766)

= 4919665725542821822433856292277539593662732530941184815992009508340620974

in hex = 2c8d08b2ef247a54c9cf810ce21d638a5d38ae370346b3954205a5dcfdeae

Fuc*g sh*t. I'm sorry friends, It turns out that the potential range for the calculation is larger than I told you.

So. IF SOMEONE FOUD PRIVKEY I WILL GIVE 1 BTC TO 3 PEPLE IF TASK WILL BE SUCCESS

p.s. I think all no so bad

First candidates for the rages with respect to X:

10000000000000000
6386c0450946b9c00000

try this range please 

[WanderingPhilospher]

I took 3 minutes and ran through your new range with Kangaroo (went 2.1 over expected ops)...key is not there, or is but program needs to run a lot longer. I know you are merely guessing where the key may be located but your figures are slightly off...better luck next time

[Kostelooscoin]

how can you tell that the private key is small?

[NotATether]

This public key differs from the base point of the SECP256k1 curve quite a bit, so I assume that the private key is very small.

how can you tell that the private key is small?

It's not. A curve point being only a short distance away from the base point is not an indicator that it was multiplied only a few times.

Doubling G, and adding G to some multiple of G, completely moves away the x and y coordinates. This is the math behind doubling at least, which is done a few several dozen times for a given private key number.

First, take lambda = (3Bx² + a)/(2By) , where (Bx, By) are the coordinates of the point B you are trying to double, and a is a parameter whose value is given along with the type of curve you are using. Since you are using the secp256k1 curve, a = 0.

So for the secp256k1 this expression becomes lambda = (3Bx²)/(2By) (I'm using red to color x coordinates and blue to color y coordinates).

Next you compute Cx = lambda² -2Bx, then you compute Cy = lambda*(Bx - Cx) - By . And this is how you get coordinates (Cx, Cy) of the point C = B*2.

Point addition does a similar warping of the x and y coordinates.

The very fact that you're multiplying the new points with a huge lambda implies that public key ranges do not correspond to private key ranges.