Pollard's kangaroo ECDLP solver

[wedom]

i know private key of this pub but cant take money out 

020000000000000000000000000000000000000000000000000000000000000000

 

Can't write to PM
If it's not a secret, what is the private key of this public key? Me not for money, but for understanding curves. You can at PM

its 0 as a.a said   

I already thought that there is still a point when x = 0 ))

[1714487802]

1714487802

[ssxb]

i know private key of this pub but cant take money out 

020000000000000000000000000000000000000000000000000000000000000000

 

Can't write to PM
If it's not a secret, what is the private key of this public key? Me not for money, but for understanding curves. You can at PM

its 0 as a.a said   

I already thought that there is still a point when x = 0 ))

if you check associated address 15wJjXvfQzo3SXqoWGbWZmNYND1Si4siqV    with PK 020000000000000000000000000000000000000000000000000000000000000000 ~   350USD there waiting for you 

[COBRAS]

i know private key of this pub but cant take money out  

020000000000000000000000000000000000000000000000000000000000000000

 

Can't write to PM
If it's not a secret, what is the private key of this public key? Me not for money, but for understanding curves. You can at PM

its 0 as a.a said  

I already thought that there is still a point when x = 0 ))

if you check associated address 15wJjXvfQzo3SXqoWGbWZmNYND1Si4siqV    with PK 020000000000000000000000000000000000000000000000000000000000000000 ~   350USD there waiting for you  

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

1:124bff742a76f92fa3a76f8f6552f

0313ee32399b1441d0c8cf7caf6d10641b30d280fe1b59fcaa09eb0326cad5cb6f

0213ee32399b1441d0c8cf7caf6d10641b30d280fe1b59fcaa09eb0326cad5cb6f

[ssxb]

i know private key of this pub but cant take money out  

020000000000000000000000000000000000000000000000000000000000000000

 

Can't write to PM
If it's not a secret, what is the private key of this public key? Me not for money, but for understanding curves. You can at PM

its 0 as a.a said  

I already thought that there is still a point when x = 0 ))

if you check associated address 15wJjXvfQzo3SXqoWGbWZmNYND1Si4siqV    with PK 020000000000000000000000000000000000000000000000000000000000000000 ~   350USD there waiting for you  

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

1:124bff742a76f92fa3a76f8f6552f

0313ee32399b1441d0c8cf7caf6d10641b30d280fe1b59fcaa09eb0326cad5cb6f

0213ee32399b1441d0c8cf7caf6d10641b30d280fe1b59fcaa09eb0326cad5cb6f

1124bff742a76f92fa3a76f8f6552f
124bff742a76f92fa3a76f8f6552f    taking out 100000000000000000000000000000 does not mean your calculations are precise

Dude , you posted before different key and now different ~ do you actually have any idea what you are doing lol . provide a logic behind it and i will use my all 3 rigs to solve it

[WanderingPhilospher]

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.

[ssxb]

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.

looks good , can i have hand on program? , maybe can help in some optimization

[COBRAS]

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....

[WanderingPhilospher]

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....

You two do not read lol...it can't find an 85 bit pubkey. I've ran it for a day looking for several 85 bit pubkeys, no luck. I will not waste time on 117-120 pubkey that may or may not be there.

[COBRAS]

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....

You two do not read lol...it can't find an 85 bit pubkey. I've ran it for a day looking for several 85 bit pubkeys, no luck. I will not waste time on 117-120 pubkey that may or may not be there.

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.

[WanderingPhilospher]

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....

You two do not read lol...it can't find an 85 bit pubkey. I've ran it for a day looking for several 85 bit pubkeys, no luck. I will not waste time on 117-120 pubkey that may or may not be there.

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.

I have no idea what practice you mean...I've never seen any ranges ran by you, just a lot of math questions lol.
All is well, we will find 120 at the pool...

[ssxb]

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....

You two do not read lol...it can't find an 85 bit pubkey. I've ran it for a day looking for several 85 bit pubkeys, no luck. I will not waste time on 117-120 pubkey that may or may not be there.

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 ,

[dextronomous]

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....

You two do not read lol...it can't find an 85 bit pubkey. I've ran it for a day looking for several 85 bit pubkeys, no luck. I will not waste time on 117-120 pubkey that may or may not be there.

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 ,

same here bro, will test and share, and prolly you will put it up on git to, like vanbitcrackn,

[Glasial0]

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.

[_Counselor]

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.

If it were possible, the ECDLP problem would not exist

[a.a]

What is the "k" number?

[Glasial0]

What is the "k" number?

k is number of point,  from 1 to 115792089237316195423570985008687907852837564279074904382605163141518161494336. Every point is g added k times.

[NotATether]

What is the "k" number?

k is number of point,  from 1 to 115792089237316195423570985008687907852837564279074904382605163141518161494336. Every point is g added k times.

In other words, the shorthand for the private key.

[dextronomous]

hi there, wandering any demo releases of your program upto 84? please thanks .
getting bored doing nothing, have some time. 2days off.   

[BlackHatCoiner]

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.

[tonylinux2008]

with iceland bsgs repo create bpfile and bloomfile:
python bsgs_create_bpfile_bloomfile.py  2000000000 bpfile2000.bin bloomfile2000.bin 32

bpfile only 1398KB,but bloomfile2000.bin about 10GB,is this right?