Topic: Pollard's kangaroo ECDLP solver - page 108. (Read 59389 times)

Thank you for reporting the DOC link, sorry for your attention.

Negative ghost rider...I know what/where the range is. When I run that exact range, here are the export files:

You see how there are only 8 characters in the distance? c4e97861 -- no matter which version of Kangaroo I run, or the range, I only get 8 characters. In the example you showed me a few days ago:
the distances have 16 characters. How did you manage to get 16 characters or were you using a different program? If not, what version of Kangaroo were you extracting from because none of the files I generate/export have 16 characters, only 8.

It's from 65 Bits key, Tame goes from 0 to 2**64 (0xffffffffffffffff)

You can upload or send by mail [email protected] /I want to join the project too, thanks.

Good afternoon. Tell me how to start Kangaroo.exe. How to run the program, there is a description, somewhere information. Tell me please. By launching the command line, the program opens and closes immediately. Maybe you need additional programs or Windows 7 is another environment?

Patatas...How/where did you get this export text?


I notice your tames and wild have 16 characters in distance (f862dc916dfc4479, 502a2b5c6849dc12) Did you export these from this program? If so, what version? I went back and recompiled back to version 1.6 (1.9, 1.8, 1.7, and 1.6) and can not duplicate.
They are all the same when I export:


a max of only 8 characters in distance (c4e97861).

In JeanLuc implementation of Kangaroo, there are an offset in tame/wild calculation. The offset is determined by "START" value un config file.

Are the x coordinates and distances generated and saved in files by this specific program "shortened" to save RAM/storage space?
Using the "export" feature by PatatasFritas, when I look at the tame and wild files. Here is example of distance for a 57 bit :
this is what is shown.
I tried building a comparer for the text files generated but something is off.
All the other Kangaroo programs out there, the distance for a 57 bit look like this:
64 characters versus 32 characters but that is not significant. The significance is in the last digits of the distance. This program has 8 end characters and the other programs generate 15 end characters. So, does this program or the export feature "shorten" the digits for distance in order to save space or is there different ways to store kangaroo distances?
When I run the comaprer for the other programs using the text files, all solve correctly.
When I use the comparer for this program, it solves, but it's the wrong bit.

Example, when I solve using other programs with comparer I get:
which is correct private key.

But when I use the comparer on this program I get:

Notice how the one is shorter, but it does calculate the last 8 characters correctly. Is it because distances are shorter in this program?
Many thanks to anyone who can help me learn/understand better.

Hi,

1.9 is ready:

    Added -wmdir option (thanks to PatatasFritas)
    Support of kangaroo backup for client

wmdir is for merging

kangaroo -wmdir dir_name work_file_name: It merge all work files present in dir_name to work_file_name

I'm working on the README

for me your example it is a garbage of commands. for what you set -i and -ws  if there -wsplit ?
the same as i know using cpu and gpu togheter slower then gpu  once.

Maybe someone with DP31 115 sharing is caring?

jean luc how to use the -wmdir, got error 3 180 some others
is this for the server client way or also solo on one system.
Kangaroo19latest -t 1 -gpu -gpuId 0 -o *.txt -ws -d 31 -w .work -i .work -wsplit -wmdir ? -wi 180 *.txt
thanks

Anyone else with DP 30 for #115, I have file to share.

Did you download the compiled version and it didn't work?

Link:
https://github.com/JeanLucPons/Kangaroo/releases/tag/1.8

Intel(R) Xeon (R) CPU [email protected]/Manufacturer ASUTeK P5Q-PRO/RAM 7.00GB/GTX1050Ti

he downloaded program from the site does not work.Could not compile correctly.Someone compile under Windows 7 64bit.You can upload or send by mail [email protected] /I want to join the project too, thanks.

I let my system run on dp 26 with 2^22 kangaroos

Thanks for the explanation. I appreciate you taking the time to draw that up.

Running a test at DP 25 for puzzle #115 with 2^27 kangaroos; 16 hours, running strong. RAM at constant 49%. RAM = 8GB

Only exports DP, headers can be "extracted" with -winfo

In SaveFile/HashTable, DPs are grouped by 18bits (from 0x00000 to 0x3ffff). And inside every group are stored distance and x-coord.

Distance: (1bit sign + 1bit type tame/wild + 126bits distance)
X-Coord: 128 bits

With 18bits of group + 128bits of x-coord, we have 146bits; and we "lost" 110bits (left N bits are zeroed as DP, -d option)

Example:

Does your export strip any information out of original DP files or are you extracting everything, minus the headers?