I wish Ocean would not conflate decentralised block construction and Knots.
They are different things
Login to reply
Replies (13)
Trojan horse, maybe.
does it matter which node you use for the block template construction?
I think that is what they are trying to do.
But I think it puts off people who would otherwise be interested in fair payouts and creating their own blocks.
I don't think so. They have multiple templates (including core).
However when I tried to set up DATUM on Umbrel, it said that it was dependent on Knots???
So I'm not sure
Stratum server builds transactions not node. Node propagates it
Do you mean DATUM? It can only construct a block according to the rules of the node (and mempool) that it is connected to.
Datum is a stratum server
I think the issue is without knots you can't really configure much of your mempool policy
Yeah.
But some people are happy to run Core if they can avoid hashing for Bitmain, right?
It's depends on the node you run. The mempool policy you run on your node determine the block template that will be built.
Yes but that doesn't really do much to decentralise block template construction assuming bitmain run the standard core mempool settings.
I guess if you hashed for ocean and used one of their options that at least goes some way towards it, but ideally just run a node and datum so you are a miner once again and ocean are just splitting rewards to reduce variance.
new transactions are stored in a node's memory pool while they're waiting to get mined on to the blockchain.
Bitmain don't run standard Core.
Using Ocean's standard options is a good compromise. You can literally see the block you are hashing against.
OCEAN - Block Template