Dude, broadcasting blocks direct to the network > getting the pool to do it.
If you don't understand this you're a moron.
Yes OCEAN could be stupid and refuse to broadcast a block if it wanted, but it isn't unique compared to any other node. YOU can refuse to broadcast OCEAN blocks if you want with your node. Is it going to have any effect? No.
Which is faster?
Solution found goes 1 hop to your home node and then fans out, with N varying nodes before reaching a major mining node.
Solution found goes 1 hop to a pool's node and then 1 hop to other major mining nodes.
Less hops is faster.
Love ya buddy 😁
Are we still talking about solo mining? DATUM is the only solution that even provides a second broadcast source as an option. Lotto solo mining ONLY does the home broadcast. So even if we refused to do so, it would still not be any worse than your alternatives.
The point is if you refused to do so then OCEAN wouldn't be doing as Mich for decentralization as you portrayed. I'm glad to hear from you directly that you would not refuse a valid block find if your pool fee was excluded.
Why do you assume a miner's node has to be a dingy Raspberry Pi at home running exclusively over Tor?
If a miner cares about such a thing he can run their node on AWS and add a bunch of addnode= to their configuration, just like Ocean or anyone else can do it.
If they can afford enough ASICs to find blocks with certain regularity they surely can afford to rent a basic bare metal server to host their node.
Latency has nothing to do with compute.
It does in this case. If you care about validating and broadcasting your own blocks as fast as possible you don't want to run the node in a cheapo VPS that is timesharing the physical CPU with a thousand other virtual machines.
But besides this irrelevant non sequitur my point still stands: nothing stops any serious miner from having his own "pool-grade" low latency & well connected node. It's orders of magnitude easier and cheaper than running a big mining farm.
