This approach is particularly beneficial for scenarios where it's necessary to ascertain that a transaction occurred after a certain block height, such as in the case of air-gapped embedded hardware devices. These devices could enforce rules requiring transactions to exist above a specified height, using the cumulative difficulty of surrounding headers as proof. The proposition suggests that this rule be enforced immediately upon the activation of a soft fork, without delay until a specific future block height, like 1,983,702, to avoid potential complications.

There is an acknowledgment of potential challenges miners might face with the introduction of this new rule, especially considering the diverse custom software solutions utilized in processing coinbase transactions. It's uncertain how these systems will adapt to the change, suggesting a need for thorough testing before full implementation. A GitHub branch has been created by Sjors, featuring a pull request that implements the -coinbaselocktime parameter, aiming to facilitate mining code adjustments to accommodate this new rule (GitHub PR). The proposal encourages miners to test this solution well in advance of any formal activation parameters being established. This proactive approach aims to identify and address any unforeseen issues, ensuring a smooth transition for all parties involved.