Which project do you actually need to be compiled? I could compile all variations, but would like to just compile the specific one you want...
Yup, the latest code here if you could compile would be great.
https://github.com/ZenulAbidin/Kangaroo-256
Topic: Pollard's kangaroo ECDLP solver - page 56. (Read 59389 times)
Yup, the latest code here if you could compile would be great.
https://github.com/ZenulAbidin/Kangaroo-256
Sad to see there's no compiled .exe for the Kangaroo-256 fork. Compiling from the source throws a ton of errors, same with Jean_Luc's original version. But at least there is a working .exe for that one. I hope the dev finds time to compile the -256 fork on a Win machine 
I could successfully build the fork. But would you trust me if I publish the file?
I don't need to trust you. I just need to make sure your .exe doesn't have any network access. And since I'd run it inside an offline VM no need to worry about malware either. Thanks.
Which project do you actually need to be compiled? I could compile all variations, but would like to just compile the specific one you want...
Sad to see there's no compiled .exe for the Kangaroo-256 fork. Compiling from the source throws a ton of errors, same with Jean_Luc's original version. But at least there is a working .exe for that one. I hope the dev finds time to compile the -256 fork on a Win machine
I could successfully build the fork. But would you trust me if I publish the file?
Upload the exe somewhere like on zippyshare and then PM me the link so I can make a Github release out of it.
Thank you very much for your help, I appreciate it
Sad to see there's no compiled .exe for the Kangaroo-256 fork. Compiling from the source throws a ton of errors, same with Jean_Luc's original version. But at least there is a working .exe for that one. I hope the dev finds time to compile the -256 fork on a Win machine
I could successfully build the fork. But would you trust me if I publish the file?
So what exactly does your fork do? Make it able to search in a 256 bit range? Anything else?
Yea that's it, just make it able to search in a 256 bit range. That's all he was working on.
So what exactly does your fork do? Make it able to search in a 256 bit range? Anything else?
What is the url of the fork?
Sad to see there's no compiled .exe for the Kangaroo-256 fork. Compiling from the source throws a ton of errors, same with Jean_Luc's original version. But at least there is a working .exe for that one. I hope the dev finds time to compile the -256 fork on a Win machine
2.1, 2.2 and your 2.3. I am going to try the precompiled 2.2, 2.1 later. But my guess it is not the program and definitely not the in.txt file but possibly the intel drivers/opencl which I am going to update also later. One computer works well with the in.txt file and if the move the complied program to the other computers or compile them on their own I still get the error. if it was the program it should not work on any.
OK, to be clear, which fork of Kangaroo are you getting this error on? There's the original one by Jean_Luc and there's also my Kangaroo-256 fork.
it is an illusion of the font the webpage uses
10000000000000000000000000000000 = 21267647932558653966460912964485513216
1FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF = 42535295865117307932921825928971026431 double the top line. All my cpu's are I-3 quad core except one which is 12 core Xeon L5638
10000000000000000000000000000000 = 21267647932558653966460912964485513216
1FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF = 42535295865117307932921825928971026431 double the top line. All my cpu's are I-3 quad core except one which is 12 core Xeon L5638
No I did not use puzzle32.txt LOL. Here is what my in.txt files look just like this 125
10000000000000000000000000000000
1FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF
0233709EB11E0D4439A729F21C2C443DEDB727528229713F0065721BA8FA46F00E
It is nothing to do with the in.txt file. Maybe I need to update the intel opencl for the cpu's. it can't be the same hardware issue for 4 different computers. if it was just 1 computer then maybe
10000000000000000000000000000000
1FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF
0233709EB11E0D4439A729F21C2C443DEDB727528229713F0065721BA8FA46F00E
It is nothing to do with the in.txt file. Maybe I need to update the intel opencl for the cpu's. it can't be the same hardware issue for 4 different computers. if it was just 1 computer then maybe
If you are trying to search from the "1FF..." number to "10000...", because you appear to have the bigger number on top, the "1FF" should be on the first line followed by "10000...".
Also what model is your CPU, you need to have SSSE3 on it to work so at least Core 2.
I have compiled them with VS2019. I have 1.5, 2.2 and 2.3. On one computer they do not have an issue. 4 other computers have the same issue. i have to make the work file on the one and copy it to the others. I think I will try to update the intel cpu software/drivers in the morning for those.
Download the precompiled 2.1 version and test it.
I have compiled them with VS2019. I have 1.5, 2.2 and 2.3. On one computer they do not have an issue. 4 other computers have the same issue. i have to make the work file on the one and copy it to the others. I think I will try to update the intel cpu software/drivers in the morning for those.
No I did not use puzzle32.txt LOL. Here is what my in.txt files look just like this 125
10000000000000000000000000000000
1FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF
0233709EB11E0D4439A729F21C2C443DEDB727528229713F0065721BA8FA46F00E
It is nothing to do with the in.txt file. Maybe I need to update the intel opencl for the cpu's. it can't be the same hardware issue for 4 different computers. if it was just 1 computer then maybe
Which compiled release version are you using? Or did you compile/build on linux? 10000000000000000000000000000000
1FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF
0233709EB11E0D4439A729F21C2C443DEDB727528229713F0065721BA8FA46F00E
It is nothing to do with the in.txt file. Maybe I need to update the intel opencl for the cpu's. it can't be the same hardware issue for 4 different computers. if it was just 1 computer then maybe
No I did not use puzzle32.txt LOL. Here is what my in.txt files look just like this 125
10000000000000000000000000000000
1FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF
0233709EB11E0D4439A729F21C2C443DEDB727528229713F0065721BA8FA46F00E
It is nothing to do with the in.txt file. Maybe I need to update the intel opencl for the cpu's. it can't be the same hardware issue for 4 different computers. if it was just 1 computer then maybe
10000000000000000000000000000000
1FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF
0233709EB11E0D4439A729F21C2C443DEDB727528229713F0065721BA8FA46F00E
It is nothing to do with the in.txt file. Maybe I need to update the intel opencl for the cpu's. it can't be the same hardware issue for 4 different computers. if it was just 1 computer then maybe
That is the public key for puzzle 120, same number on the blockchain and published in your source code too (puzzle32.txt). Also no matter what public key I put in i get the same error. The error can't be in the in.txt file. I have made new ones for each computer and copied the one from the computer that does not get the error. Required text encoding for the in.txt file? All my computers save text in UTF-8
in.txt just use notpad on windows
I think you put puzzle32.txt all in use, that is wrong
you need to split each set of puzzle to new one in.txt it can you any name
in120.txt
in121.txt
in122.txt
puzzle120.txt
(somting like that)
Don't put new line on the end bottom line too
structure simple just 3 line
1 start keyspace search
2 end keyspace search
first public key search
That is the public key for puzzle 120, same number on the blockchain and published in your source code too (puzzle32.txt). Also no matter what public key I put in i get the same error. The error can't be in the in.txt file. I have made new ones for each computer and copied the one from the computer that does not get the error. Required text encoding for the in.txt file? All my computers save text in UTF-8
You can try run kangaroo -check to make sure that basic calculations performing without errors.If you see any errors, than something wrong with your hardware.
Jump to: