Quote from: fxsniper on Today at 12:49:15 PM

Quote from: NotATether on Today at 10:38:39 AM

To my understanding I believe it contains records with each entry (they're in binary if I remember correctly) having the positions of the tame and wild kangaroos, and possibly the number of kangaroos present. I'm not entirely sure, I have to check again.

your correct may be is binary

I try to print P Value after check pk and found

Point P = secp->ComputePublicKey(&pk);

if(P.equals(keyToSearch)) {
if(P.equals(keyToSearchNeg)) {

P is point of collision point right

image I try to print P value out but fould like this may be is binary file need to be convert to hex or decimal

@fx, again, what are you trying to see or accomplish? You have seen the tame and wild files from the kangaroo python script you have ran. There is nothing different with the kangaroo.exe files. They contain point and distances. I do not understand your obsession with wanting to see the collision points and distances. Seeing them will not help you figure out a DP or help you in any way.

JP and a lot of other smart people have thought of pretty much everything to make kangaroo.exe the best kangaroo program out there. the DP is auto calculated based on bit size you are searching and the number of kangaroos you have (based on your GPUs/CPUs) to limit the amount of DP overhead.

The work/save files contain headers and then the tame and wild points and distances.

I've told you to use the -wsplit option if you want to see collision points. After key is solved, extract points and distances via the python script I showed you. THEN you can see the collision points.