Yes, but which? Effective ossification or superstitious ossification? Filtering spam at the mempool level is a problem because policy changes don't require consensus.
Limiting OP_RETURN at the chain policy level is the only "conservative" choice. Flattening the fee rate for segwit, rather than offering a discount, would be a conservative choice. However performing active spam filtering at the chain policy level is going too far.
Rather than people focusing on the drama of the core team being infiltrated and compromised, and the pearl-clutching of the core-dev lapdogs, and the mutual tribal condemnation of core v.s. knots; why aren't we discussing solutions and/or the technical details of bip110?
