You don’t need a soft fork to change what your node relays.

While BIP-110 takes the debate to the consensus layer, Bitcoin Core already gives node operators control over their own mempool policy.

datacarriersize=83

This limits the size of OP_RETURN data your node considers standard for mempool acceptance and relay.

It doesn’t change consensus. It doesn’t invalidate blocks. Miners can still include those transactions.

Your node simply chooses not to help propagate them.

BIP-110 is about consensus.
datacarriersize is about node policy.

Different tools, different consequences.

Run your node. Choose your policy.

#BTC