New 64 Bit Random Search Pool Project

[NeuroticFish]

And this is your choice, if you do not join because I don't have enough numbers by my merit, that is fine. But I will leave you with this, just because you sit in a garage, doesn't mean you're a car.

Clearly. I hope that I didn't offend you, but I've learned to be very careful with what I install/run.
It's not only about merit, it's also about the fact he's older here, more active, I interacted more with him than you... and higher ranked by the forum.
Usually the lower the rank, the higher the chance it does something fishy. It doesn't mean that you did or you will do that, clearly. It's just chances and numbers.

As I said, a higher rank can give more credibility to everything and attract more people to the project. Whether you do that or not, it's entirely your choice.

In fact I'm the one who modified and compiled the Kangaroo #120 server (more details in the discord server linked in the OP)

That's good to know. I'm still a bit wary about the client though.

[WanderingPhilospher]

Just a quick response for now, will discuss more later:
Here is the problem, it has to remain closed source or people running the program could change a few lines of code and steal the bitcoin that everyone in the pool is working hard for. That is the only reason why it is closed source.

Wait, so the client controls the 'payout' or how could one's modification of the client on their side change how other contributors are paid out? 

I think it should be possible to code it in a way that the client, which people run, is open source, so e.g. it can be compiled by users themselves and malware for example can be ruled out etc., but the server side software remains closed (similar to when mining with a pool where the pool software is closed and the client software like cgminer is open).

Or are you worried of someone modifying the client and distributing that version so that benefits go to them?
In that case, it should be the same way as when downloading Bitcoin core: you have a GitHub page where people are always pointed to, always recommended not to get it from anywhere else and on the GitHub they can either read and compile the source themselves or download and verify signed binaries that have been compiled for them by you.

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.

[pooya87]

Why would I trust you or NotATether with the source code? Because maybe if you compile it people will be more receptive because you have x number of merit? Nah. Who's to say you wouldn't show it or give it to someone? Or who says you won't take the code and tweak it for your own benefit?

I never said such a thing and that is not what open source means.

Being open source means anyone can see the code and compile it for themselves if they choose to. Otherwise trusting X over Y with an already complied binary is the same problem all over again no matter who X and Y are or how much merit they have!
For example do you think I run Electrum because I trust Thomas. V.? Absolutely not. I use it because I can see every single line of code and can compile it myself for my own use.

Bottom line is that there was a big elephant in the room that needed to be addressed and I would have probably never said anything if the .exe was uploaded anywhere else like mediafire instead of github.

[WanderingPhilospher]

Why would I trust you or NotATether with the source code? Because maybe if you compile it people will be more receptive because you have x number of merit? Nah. Who's to say you wouldn't show it or give it to someone? Or who says you won't take the code and tweak it for your own benefit?

I never said such a thing and that is not what open source means.

Being open source means anyone can see the code and compile it for themselves if they choose to. Otherwise trusting X over Y with an already complied binary is the same problem all over again no matter who X and Y are or how much merit they have!
For example do you think I run Electrum because I trust Thomas. V.? Absolutely not. I use it because I can see every single line of code and can compile it myself for my own use.

Bottom line is that there was a big elephant in the room that needed to be addressed and I would have probably never said anything if the .exe was uploaded anywhere else like mediafire instead of github.

I was addressing you and NF, in the same post; he mentioned "giving more credibility" if x y and z compiled it.

I have no issues hanging it anywhere as there is no malicious code in it. I do not know about mediafire, can you elaborate on the differences vs github?

[pooya87]

I do not know about mediafire, can you elaborate on the differences vs github?

Mediafire is an example, sites like that are for sharing any type of files including .exe files such as yours while github is first and foremost a "code" sharing platform even though it has no restrictions on file types being uploaded.

[NotATether]

Bottom line is that there was a big elephant in the room that needed to be addressed and I would have probably never said anything if the .exe was uploaded anywhere else like mediafire instead of github.

I actually trust Mediafire and co. less than other platforms because there's an abundance of malware on there as a result of it being used to host piracy warez.

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

Can confirm.


Basically, it's in our interest to open-source the 64-bit random pool code so that Linux users can run it (you won't believe how many Linux users got nvidia cards attached despite the poor graphics support). I think the sensitive parts are limited to a few lines of code and variables, I'll see if we can just feed that information through a makefile and #define constants to hide those parts.

[ABCbits]

I do not know about mediafire, can you elaborate on the differences vs github?

Mediafire is an example, sites like that are for sharing any type of files including .exe files such as yours while github is first and foremost a "code" sharing platform even though it has no restrictions on file types being uploaded.

You could just say uploading .exe to GitHub repository (instead of Mediafire or similar website) could give few people false sense of security (since few people treat GitHub as safe place to download software directly from the developer).

Basically, it's in our interest to open-source the 64-bit random pool code so that Linux users can run it (you won't believe how many Linux users got nvidia cards attached despite the poor graphics support). I think the sensitive parts are limited to a few lines of code and variables, I'll see if we can just feed that information through a makefile and #define constants to hide those parts.

Alternatively you could provide AppImage file which should work for most linux distro.

P.S. Nvidia GPU popular among Linux users becuase it offer better price/performance and exclusive feature (such as CUDA which frequently used on heavy computer science software).