Open Mitoshi-Jackamoto opened 5 years ago
In all honesty I haven't looked to understand who the daemon works wrt to connecting to other deamons, but what if, instead of somehow 'trusting' a limited number of incoming connections, you used the interconnection between the nodes as a guard against exposure.
I'm thinking, somehow that the stratum connection would be redirected to another node, and that you would required that the node itself be on a different network(Class B) . It would mean that in order to get to 51% you would have to have nodes in many different networks.
Then you limit the connections, meaning that it isn't my own daemon that is limiting connections, but yours.
What you could further do, is decentralize the stratum, so that, each daemon is not limited in the number of connections it allows, but interchanges with it's own peers to prevent(in some way) a specific IP network from having >25%(?) of miners??
Just some random thoughts for yah.
We’re looking at all the different pros and cons to trying to get this worked. Thanks for this, it is been noted.
Here, we'll be talking about an idea and maybe doing some commits we'd like to reference to this post
What's this then? Could be the answer to solo-mining? Could be a mess waiting to happen, but lets find out anyway.
Elaboration In theory, if we implement a stratum protocol into our daemon then we could use each daemon as a pool but with limited incoming connections to prevent a sneaky 51% attack. The problem with pools as it stands is that there is not enough pools for networks to be decentralized so by having the pool within a daemon means you would need to load more daemons to further decentralize the network. As everybody should be running a daemon anyway when on the network, their should not be a problem with people taking up most of the network.
There will be a bounty here: https://discord.gg/k2jYvBT for this to be completed