I downloaded them this morning and ran them through the online scanner and they were all clean. Ran the generic on wsl and it worked 1 thread as about 2 mil/second older Xeon it seems to make a file that is either a checkpoint or remembers the addresses tried or both. works well but since I paid for a rtx GPU and made a control program so it runs unattended I am going to use that, but for CPU users it should be ok. Suggestion: put them on github and maybe others will be more comfortable then being on a file share website which makes others a little suspicious. you can open a free account there.
[/quote]
Thanks for your trust and reply!

I don't know if it helps to gain more trust, but i updated the tool, removed the executeable permissions and included a warning about running binaries from unknown sources in the README.txt and added some hints how to run binaries if you do not trust the developer. Actually there are serveral tools on github where binaries are included (like iceland and the pool) and there are no sources available for these tools available, so i don't see a big difference if i would use github. I do not exspect anybody to trust me, but at least to be fair. i just offer a different approach an my tool is quite fast on CPUs and it would be very interesting to see the keyrates on modern CPUs.

This is my last reply regarding useless speed comparisions:

you simply have to compare the speed of my tool with your prefered tool!!!


i just gave you a number for my very slow CPU - this is a mobile CPU, so this does not say anything about speed on your CPU!
if your prefered tool is faster, than be happy with it, on my CPU my tool is faster!

only through tests...
i run competiton tests between my tool and other CPU tools and my tool always found the key faster, so i guess my search logic works somehow better than a simple random search, but you cannot exspect miracles like a 10x speed improvement.

You can benchmark it for yourself:
- run the fastest CPU tool you know and compare the keyrate with my tool!
On my slow CPU i get about 30% more speed, but this may be different on other CPUs. I would be happy if some users would post keyrates of their CPUs.

I never talked about GPUs and said that my tool can compete with them - of course GPUs are faster, but not everybody (like me) has access to a fast GPU, but some people here may have access to fast multicore CPUs and using several cores of a modern CPU could give in total a quite good rate, even if a GPU may still be faster. All i say is that my approach/logic for searching is different and that i took a big effort in improving speed for CPUs - that's it.

Solving #66 requires not only speed, it also requires luck and with luck even a slow CPU could solve #66 - unlikely, but possible - in the end it's more lotto than a puzzle 

So, if you have a fast GPU then you should use it and in this case my tool is of course not helpfull for you at all.

and here again you are posting false accusations

if you quote my README.txt you should also quote this:


It was hard to developed this tool, so i have to make sure i get my share by verifying the key otherwise the user could just use the key and run - you see the problem?

It's all about trust... you don't trust me, but i should  trust the users? we are talking about a big reward!

Of course the user has to trust me that i do not take the money and run - that's right, but think about this:
would this be wise from my point of view? NO we have #67 and more to come, so i am very interested that whoever finds the key gets his share and helps to find the next key and i get again 50% of the reward.
If i would take the money and run i could only do it once... this would be very stupid.

I can only repeat:
internet permission is not required - the key is just saved to a text file.  (the TLS stuff comes from the linked libgmpxx.a which was build by compiling libgmp.a, so i linked it)

As we are talking about trust and false warnings:
why don't you warn people using the pool that is advertised here? it also includes precompiled executeables for windows and linux and unlike my tool the keys and ranges are send to a server... so to all you guys contributing to the pool: you have to trust the guy who runs the server (also a newbie), but unlike i don't say that you cannot trust him an he will run once a key is found, but it's the same problem, so it quite strange that you talk only about my tool and not about the pool.

So i repeat: My tool does what i advertised (the chance to find a is afaik higher than with any other CPU tool i have tested) and i will not run, if a key is found.

If you don't trust me or don't want to share the reward 50:50 then simply don't use my tool, but in this case you should also not use any pools and you should always only use open source tools you compiled yourself!

And again just lies... I never said i found the holy grail or promised to solve #66 within a day.

everything is explained in the README.txt, but he simply does not want to understand it.

For everybody else who wants try my tool:

- use an online virus scanner on the executeables
- use a sandboxed environment or a VM or a linux live-CD to test the executeables
- then you are free to judge me


I hope somebody with a good reputation can help me against these false accusations from this paranoid guy!?
It's ok to warn people, but just not with false accusations...

Thanks!

You can't even read...

YES, there are executables in the file, yes of course these are precompiled versions (README.txt) and if you would have read the REAME.txt you would understand why i cannot publish the sources,
but you simply don't want to understand... and there are also online virus-scanners where you could upload the executeables, but you just want to tell lies...

You are a linux geek and do not even understand what PRECOMPILED means or what a SANDBOXED environment is???

If you are a linux geek you could even you could even boot a linux live-cd, unplug all your harddrives and network connections (if you are paranoid) and simply test my tool and you will see it does no harm at all, still all you can do is telling lies, i just hope here are some people with a brain

sad but true, it seems i am wasting my time here, unless some more intelligent people jump in.

You really made my day... 

@citb0in
I have also reported your post!

Yes i am new here, but my tool is absolutely safe to use!

It seems you are windows user and do not understand anything about linux and permissions.
Please try to understand this before posting false warnings and telling lies:


- my tool does not require any dangerous permissions (like internet access or anything else)
- my tool requires only read and write permissions in the current folder (to save the current position and the key, once it is found)

It's OK not to trust anybody, but linux allows you to run this tool in a sandboxed environment - this way it can not do any harm!


So, please think before you post such a warning and accuse people!
I worked hard to develop this tool and i want to share it with anybody who is interested to solve #66 - that's it!

I hope here are some linux guys who understand what i am talking about.

I have developed a new tool to solve #66:

- ONLY CPU / highly optimized for speed and about 30% faster (on my CPU) than the fastest tool i know
- ONLY LINUX x86_64 / there is no and NEVER will be a WINDOWS/MAC version (DO NOT ASK!!!), but it may run on Windows Subsystem for Linux (WSL) / not tested
- SPECIAL SEARCH ALGORITHM/LOGIC that allows resuming search and has a higher chance to find the key (sucessfully tested on the solved puzzles!) / no stupid random or incremental search
- DUE TO LEGAL REASONS PRECOMPILED/PRECONFIGURED FOR #66 / i will release an update for #67 once #66 is solved

In short:
My tool is afaik the best option if you have access to one or more modern powerfull multicore CPUs and want to solve #66.
It still will not be easy to solve #66, but at least your chance to solve it will be higher!
All i ask you for is to split the reward (50:50) with me, if you use my tool.

If you are interested: the download link is in my profile.

NOTE: For anything regarding this tool leave me a private message! It may take some time, but i will try to answer all messages - thanks!