I’m not capable of see how older nodes previous to BIP 68, BIP112 and BIP 65 are capable of stop including Transactions to their mempool when the newer guidelines are intentionally breached. I need to separate two circumstances I do not perceive:
OP_CLTV. Shall we say an UTXO Output is locked by <30Blocks OP_CLTV OP_DROP HASH160 PKH CHECKSIG>. Nodes following the brand new normal will verify the nlocktime area of a transaction in order that it’s sooner than the time within the encumbrance. But when I publish this transaction to older nodes, for them the ScriptPubkey isn’t TimeLocked. So how are older miners prevented to mine on such invalid transactions
OP_CSV. For this OP_Code I might see, that older Nodes is not going to embrace transactions with a model quantity >=2. In any other case we’d have the identical issues, that older nodes would come with these transactions of their mempool with out with the ability to verify whether or not they’re breaching the relative time lock.
With the brand new Script Versioning launched by Segwit, these circumstances bought simpler. However utilizing NOPs backwards compatibility appears very onerous.