Ocean is the central server that coordinates the coinbase split and sends it to all the miners connected to their server. Without Ocean you are no longer pool mining because ocean is the server that every miner is relying on for the split.

Even if I run my own node

when you remove Ocean who coordinates and administers the split?

Reply to this note

Please Login to reply.

Discussion

I dont understand the dilemma here, if miners are gathering their hashpower to homogenise payouts, it is going to be mandatory to have a central point of coordination. The fact that DATUM allows to only have coordination around the payments and not on the template is an upgrade. arouI suppose that if OCEAN makes all their code open source, the disappearance of OCEAN wont be a problem. Dont think that a central pool that coordinates payments is a risk to the network. The risk IMO is censored transactions.

Pools are very much needed and thanks to them the 51% attack is way more difficult. Mining conpanies may not be aligned with the philosophy but thanks to the network incentives they help to secure everything.

Pools do not decentralize mining period!

I already showed you with GitHub links what happens and what message miner will get - pool can reject your template no matter what

If a miner founds a block an sends it to a node that he is self hosting, no one can stop/cancel that block from spreading.

Don't care about the links they are not about block submittion to the network.

What you describing is not pool mining

but lottery mining

lol 😂 those links tell you what happens behind the seen it’s a code that runs both datum and stratum server.

Nothing is decentralized with stratum 2 or datum unless you hash towards your own node and your own stratum server

Again, you clearly don't know how DATUM works.

With DATUM you create your own block template using your OWN Bitcoin node. This means you decide which transactions are included in the block, not the pool. When your mining hardware finds a valid block, the DATUM Gateway—software running alongside your node—handles the submission process. The block is broadcast directly to the Bitcoin network by your node, ensuring it enters the network without relying on OCEAN to relay it.

The pool’s validation is a temporary coordination step for reward purposes, but it doesn’t gatekeep the block’s entry into the blockchain.