This doesn't work.

Even a relatively small number of V30 nodes 'on the network' at default settings... and it's possible 'objectionable content' will make it into blocks.

Once one 'objectionable picture' gets in a block it is stored on all core and knots full nodes forever, because a 100kb file is consensus valid. Even having datacarriersize=0 doesn't change that... it stays on the computer forever as long as the computer doesn't prune/remains archival and consensus remains the same.

I don't buy the argument that mechanic has made that governments only care (provided they do care) about mempool policy. "Governments don't care about blocks on a hard drive" etc etc... I think that's ridiculous.

"Ladies and gentlemen of the jury the accused had pictures on a harddrive that's OK... but they had them in their mempool that's NOT OK!!!"

Right... that's not how government works they will never make that distinction should they target people for simply running a bitcoin node.

So if knots runners follow through on this logic "more copies" of knots isn't the answer in fact it's more copies of the data they find objectionable.

It's a consensus change they need... to protect the peer-to-peer nature of Bitcoin while being able to "legally" run a full node and that is incompatible with core v30.

So a chain split will happen it's not if it's when.

2 separate tokens 2 separate networks it's all over except for signing the documents