Pollard's kangaroo ECDLP solver - page 100.

JDScreesh

jr. member

Activity: 47

Merit: 13

Quote from: Jean_Luc on June 16, 2020, 03:00:26 AM

We (me and zielar) solved #115 after ~2^33.36 DP (DP25) (More than 300GB of DP). I do not know exactly how long the run takes due to unwanted interruption.
Cheesy

Congratulations for breaking the World Record too. Good job

The last world record was 112 bits, right? Huh

Jean_Luc

sr. member

Activity: 462

Merit: 696

We (me and zielar) solved #115 after ~2^33.36 DP (DP25) (More than 300GB of DP). I do not know exactly how long the run takes due to unwanted interruption.
Cheesy

JDScreesh

jr. member

Activity: 47

Merit: 13

And finaly the #115 was found. Congratulations Zielar and Jean_Luc_Pons

We are all wondering which was the privkey Wink

zielar

full member

Activity: 281

Merit: 114

Quote from: dextronomous on June 15, 2020, 07:50:27 PM

hi there zielar, was and guess we are all waiting for your exact statistics,

and was wondering could we enable some more stats inside kangaroo like current sampled or checked collisions,
at long waiting times these could help maybe somewhat to skip time, like smilies or so or a percentage counter,
or anything extra then current like some advancement inside kang. would be delightfull.

greets.

From what I know, there will be progress soon.
The statistics arrive so late, because I have completed the last files and at the moment I am sure that it contains all the work that was intended for 115:

dextronomous

full member

Activity: 431

Merit: 105

hi there zielar, was and guess we are all waiting for your exact statistics,

and was wondering could we enable some more stats inside kangaroo like current sampled or checked collisions,
at long waiting times these could help maybe somewhat to skip time, like smilies or so or a percentage counter,
or anything extra then current like some advancement inside kang. would be delightfull.

greets.

zielar

full member

Activity: 281

Merit: 114

Quote from: MrFreeDragon on June 15, 2020, 04:19:55 PM

Quote from: zielar on June 15, 2020, 03:26:59 PM

-snip-
In fact - at the current # 115 level - at all costs everything tries to prevent it from finding the key - from hardware - data loss and tedious restore due to a storm - by placing it ... - nevertheless, together with Jean_Luc_Pons managed to rebuild and improve this arduous process and process continues. This gave a lot of lessons in preparation for # 120.
What I will say more - that the 50% threshold was already exceeded when I mentioned it recently. Over the next hour I will give you the exact statistics from the current situation. It is certain, however, that this time is not as lucky as before and the work is still in progress.

Did you implement the feedback from server to clients? If no - that means that the clients continue to perform "useless work" moving the dead "zombi" kangaroos:

If you have let's say 100 different machines working independent, you reproduce only the dead kangaroos found within one machine only (machine 1 reproduce dead kangaroos only found by itself). After merging all these 100 files on the server, the server finds a lot of dead kangaroos however does not send back signal to clients to reproduce them. Clients continue working with that "zombi" because they do not have feedback from the server. That also means that during the next merging the server will receive again the same kangaroos, the server will kill them again, but the "zombies" will continue their jumps on client side. And so on.

This could cause the very inefficient work for wider ranges like #115 or more.

I don't have any implementations that are not in the latest version of Kangaroo. As a curiosity I will add that so far - I still have NO dead kangaroos!

brainless

member

Activity: 330

Merit: 34

Quote from: MrFreeDragon on June 15, 2020, 04:19:55 PM

Quote from: zielar on June 15, 2020, 03:26:59 PM

-snip-
In fact - at the current # 115 level - at all costs everything tries to prevent it from finding the key - from hardware - data loss and tedious restore due to a storm - by placing it ... - nevertheless, together with Jean_Luc_Pons managed to rebuild and improve this arduous process and process continues. This gave a lot of lessons in preparation for # 120.
What I will say more - that the 50% threshold was already exceeded when I mentioned it recently. Over the next hour I will give you the exact statistics from the current situation. It is certain, however, that this time is not as lucky as before and the work is still in progress.

Did you implement the feedback from server to clients? If no - that means that the clients continue to perform "useless work" moving the dead "zombi" kangaroos:

If you have let's say 100 different machines working independent, you reproduce only the dead kangaroos found within one machine only (machine 1 reproduce dead kangaroos only found by itself). After merging all these 100 files on the server, the server finds a lot of dead kangaroos however does not send back signal to clients to reproduce them. Clients continue working with that "zombi" because they do not have feedback from the server. That also means that during the next merging the server will receive again the same kangaroos, the server will kill them again, but the "zombies" will continue their jumps on client side. And so on.

This could cause the very inefficient work for wider ranges like #115 or more.

if jean luc created multi pubkey ver in time, maybe the job for 115 is only for 1 day with zieler gpus at 85bit
range
anyway they had agreemnet, and cant think beyond thier creation+GPU's

MrFreeDragon

sr. member

Activity: 443

Merit: 350

Quote from: zielar on June 15, 2020, 03:26:59 PM

-snip-
In fact - at the current # 115 level - at all costs everything tries to prevent it from finding the key - from hardware - data loss and tedious restore due to a storm - by placing it ... - nevertheless, together with Jean_Luc_Pons managed to rebuild and improve this arduous process and process continues. This gave a lot of lessons in preparation for # 120.
What I will say more - that the 50% threshold was already exceeded when I mentioned it recently. Over the next hour I will give you the exact statistics from the current situation. It is certain, however, that this time is not as lucky as before and the work is still in progress.

Did you implement the feedback from server to clients? If no - that means that the clients continue to perform "useless work" moving the dead "zombi" kangaroos:

If you have let's say 100 different machines working independent, you reproduce only the dead kangaroos found within one machine only (machine 1 reproduce dead kangaroos only found by itself). After merging all these 100 files on the server, the server finds a lot of dead kangaroos however does not send back signal to clients to reproduce them. Clients continue working with that "zombi" because they do not have feedback from the server. That also means that during the next merging the server will receive again the same kangaroos, the server will kill them again, but the "zombies" will continue their jumps on client side. And so on.

This could cause the very inefficient work for wider ranges like #115 or more.

zielar

full member

Activity: 281

Merit: 114

Quote from: arulbero on June 15, 2020, 03:04:10 PM

Quote from: zielar on June 13, 2020, 08:23:00 AM

Quote from: arulbero on June 13, 2020, 05:44:01 AM

To recap (and to return in topic):

#115 -> 114 bit

steps needed to have 50% chance of a collision: about (114/2)+1 = 58 bit -> 2^58

DP = 25

steps performed: 2**25 * 2**33.14 = 2**58.14, then you are close to the result?

I expect a result at any time. You had to add ~ 5% tolerance limit due to inconsistency in ~ 00.05% files, so in my case from 2 ^ 33.167 gives 52%. I have already crossed 2 ^ 33.18 just so it is exactly as you wrote :-)

Any news?

It may take more time finding #115 than finding #120 ...

In fact - at the current # 115 level - at all costs everything tries to prevent it from finding the key - from hardware - data loss and tedious restore due to a storm - by placing it ... - nevertheless, together with Jean_Luc_Pons managed to rebuild and improve this arduous process and process continues. This gave a lot of lessons in preparation for # 120.
What I will say more - that the 50% threshold was already exceeded when I mentioned it recently. Over the next hour I will give you the exact statistics from the current situation. It is certain, however, that this time is not as lucky as before and the work is still in progress.

arulbero

legendary

Activity: 1932

Merit: 2077

Quote from: zielar on June 13, 2020, 08:23:00 AM

Quote from: arulbero on June 13, 2020, 05:44:01 AM

To recap (and to return in topic):

#115 -> 114 bit

steps needed to have 50% chance of a collision: about (114/2)+1 = 58 bit -> 2^58

DP = 25

steps performed: 2**25 * 2**33.14 = 2**58.14, then you are close to the result?

I expect a result at any time. You had to add ~ 5% tolerance limit due to inconsistency in ~ 00.05% files, so in my case from 2 ^ 33.167 gives 52%. I have already crossed 2 ^ 33.18 just so it is exactly as you wrote :-)

Any news?

It may take more time finding #115 than finding #120 ...

WanderingPhilospher

full member

Activity: 1162

Merit: 237

Shooters Shoot...

Quote from: COBRAS on June 15, 2020, 02:56:04 PM

Quote from: WanderingPhilospher
[/quote

A dead kangaroo means there was a collision inside the same herd, either two wilds or two tames collided. The program automatically replaces the dead kangaroo with another kangaroo. so no worries.

Thank you for your reply. How to use this information - about dead kangaroo ? I have only 1 pubkey from 10 with kabgaroo - dead kangaroo ? And I was stop calclulation pubkey with dead kangaroo because max operation count was max.

What i need to do for pubey with dead kangaroo ? - make more bytes search range or ? ? ?

Thx.

How big of a range are you searching?

1 dead kangaroo is nothing, really.

If pubkey isn't in the range you were searching, then yes, I'd search a different range. If it's a small enough range, use BSGS to make sure the pubkey isn't in the range.

COBRAS

member

Activity: 873

Merit: 22

$$P2P BTC BRUTE.JOIN NOW ! https://uclck.me/SQPJk

Quote from: WanderingPhilospher
[/quote

A dead kangaroo means there was a collision inside the same herd, either two wilds or two tames collided. The program automatically replaces the dead kangaroo with another kangaroo. so no worries.

Thank you for your reply. How to use this information - about dead kangaroo ? I have only 1 pubkey from 10 with kabgaroo - dead kangaroo ? And I was stop calclulation pubkey with dead kangaroo because max operation count was max.

What i need to do for pubey with dead kangaroo ? - make more bytes search range or ? ? ?

Thx.

brainless

member

Activity: 330

Merit: 34

Quote from: Konstanting2 on June 15, 2020, 02:47:53 PM

Thanks for the help. I was able to compile a file for your clients. The program helped fix the extension as needed bat and txt. I started it after 3 minutes at 1050 and got an answer in 65save.txt, but I could not read everything there in hieroglyphs. Help explain how further please.

download and install emeditor
right click file and open with emeditor, there is all option and format for open file

Konstanting2

newbie

Activity: 27

Merit: 0

Thanks for the help. I was able to compile a file for your clients. The program helped fix the extension as needed bat and txt. I started it after 3 minutes at 1050 and got an answer in 65save.txt, but I could not read everything there in hieroglyphs. Help explain how further please.

zielar

full member

Activity: 281

Merit: 114

Quote from: Konstanting2 on June 15, 2020, 02:29:49 PM

Hello everybody! I have a question? On Windows7, the 65save.txt file opens and there are hieroglyphs. Is this a file with save.work right? On Windows7, everyone has a file that opens with hieroglyphs. I tried to open the file with different programs with transcoding, the result is incomprehensible. If you have Windows 10 there are no such problems? And does the Kangaroo.exe program work differently? If there are Russian-speaking users, dismount [email protected]. I sorted it out in mining on my 1050Ti, but here it’s kind of complicated on Windows7 so far.

These are files that are written and recognized by the program that created them. You can see the same hieroglyphs by opening e.g. a picture or music in a notepad.

Konstanting2

newbie

Activity: 27

Merit: 0

Hello everybody! I have a question? On Windows7, the 65save.txt file opens and there are hieroglyphs. Is this a file with save.work right? On Windows7, everyone has a file that opens with hieroglyphs. I tried to open the file with different programs with transcoding, the result is incomprehensible. If you have Windows 10 there are no such problems? And does the Kangaroo.exe program work differently? If there are Russian-speaking users, dismount [email protected]. I sorted it out in mining on my 1050Ti, but here it’s kind of complicated on Windows7 so far.

WanderingPhilospher

full member

Activity: 1162

Merit: 237

Shooters Shoot...

Quote from: COBRAS on June 15, 2020, 12:03:27 PM

Help someone. Kangaroo not found dead kangaroo and privkeys. Were is a problem ? What can help to fined privkey ? In 10 pubkeys I have one with dead kangaroo ? Pubkey with dead kandagoo moree good then pubkey without kangaroo ? What to do Huh

?

Thx

A dead kangaroo means there was a collision inside the same herd, either two wilds or two tames collided. The program automatically replaces the dead kangaroo with another kangaroo. so no worries.

COBRAS

member

Activity: 873

Merit: 22

$$P2P BTC BRUTE.JOIN NOW ! https://uclck.me/SQPJk

Help someone. Kangaroo not found dead kangaroo and privkeys. Were is a problem ? What can help to fined privkey ? In 10 pubkeys I have one with dead kangaroo ? Pubkey with dead kandagoo moree good then pubkey without kangaroo ? What to do Huh

?

Thx

COBRAS

member

Activity: 873

Merit: 22

$$P2P BTC BRUTE.JOIN NOW ! https://uclck.me/SQPJk

Quote from: aplistir on June 15, 2020, 06:33:10 AM

Quote from: Etar on June 14, 2020, 12:01:51 PM

Quote from: brainless on June 14, 2020, 12:00:04 PM

-snip-
mean 789.789 is value can u div pubkey by above value ?

Can`t and nobody can`t. devider must be integer not float. all pubkeys Q=k*G, where k - integer.

Sorry for continuing an off topic discussion, but:

Of course you can divide by 789.789 if you want.

because 789.789=789789/1000 , which doesn't have decimals in it AND you can divide and multiply by scalar numbers.

Don't know why would anyone want to divide by 789.789, but it s possible

Sorry. Move talk about calculator to enother thread !!!

aplistir

full member

Activity: 378

Merit: 197

Quote from: Etar on June 14, 2020, 12:01:51 PM

Quote from: brainless on June 14, 2020, 12:00:04 PM

-snip-
mean 789.789 is value can u div pubkey by above value ?

Can`t and nobody can`t. devider must be integer not float. all pubkeys Q=k*G, where k - integer.

Sorry for continuing an off topic discussion, but:

Of course you can divide by 789.789 if you want.

because 789.789=789789/1000 , which doesn't have decimals in it AND you can divide and multiply by scalar numbers.

Don't know why would anyone want to divide by 789.789, but it s possible

Topic: Pollard's kangaroo ECDLP solver - page 100. (Read 58630 times)