Quote from: WanderingPhilospher on Today at 06:37:23 PM

None of the software does an auto pay out. That will all be done manually.

If you know what the pool is about and understand how the client works in its original form and how the actual cracking software works in its original form, you can conclude how easy it would be to manipulate work done, i.e. your percentage of work done to receive more than your fair share or flat out take the private key and claim all the BTC for yourself.

Some people have already tested the programs. I can see how many people use a different cracking software to try and run with the client software. But without the version on github, they can run their program all day but receive zero credit because it is "fake" work/not validated. That is because there are 2 fail safes built into the software that detect bad actors and does not give them credit. One on the client side and one on the cracking side. If either are exposed, then the pool is worthless.

If you have ever ran TDs 64 bit pool and actually watch what is going on when your machine is running the program, which by the way, it is also closed course (hmmmm, I wonder why), you can see the vulnerabilities in it. But you have to pay attention...

I will discuss options with NotATether in private to see if their is a viable solution.

Mmmm okay, alright, just make sure you're safe against decompiling / changing parameters (you mentioned changing percentage reports) and recompiling and stuff like that.
Security by obscurity is possible but hard to achieve imho and every non-obscure security mechanism should always be considered if in any way possible Grin

unixb0y

Posts

Merits