Thread

Replies (41)

Can you tell me more (in neutral terms πŸ™‚) about how Knots is different from Bitcoin Core? Is it more configurable than Core? Does it have different defaults than Core? And is it the case that - at the moment - the size of the accepted OP_RETURN is the most interesting/controversial difference in what the various nodes are accepting in the mempool?
I've been trying to quickly catch up with the details of Knots. Is this true: - it's new, and hasn't been reviewed much - it limits op_return to 42 bytes - today, Core has a limit of 80 bytes - but the next release of Core will have no limit on op-return - both clients transfer data via the normal Bitcoin client relay network and not over any other network; i.e. neither of them use any other network I'm trying to write neutrally, to get the facts straight. I'm very aware of the spam/op-return/unspendable-utxo debate, I just don't know much about Knots specifically
You and I have never interacted before, and you don't know who I am. I just asked for practical details of what the differences are. E.g. do they have different op-return limits? It seems to be common in Bitcoin to announce "Bitcoin core has been co-opted", such as during the BCH arguments. This tells me nothing, other than you dislike Core. I want facts, as I will be forming my own opinion.