As far as the BIP that you mentioned is concerned, isn't it the definition of timelocked transactions?
Define me "timelocked". There's the "You cannot mine this until block x" timelocked (AKA, locktime). There's the "You cannot
spend this until block x" timelocked. There's the "You cannot spend this
after block x" timelocked*. All do lock to the future, though, yes.
I mean are you sure that the only move I need to do is to broadcast it now and it will be mined in 2 years?
No, it will be mined in 10 minutes, but the new UTXO cannot be spent until 2025.
In the case you broadcast a transaction before its locktime, nodes will reject it and they won't keep your transaction in their mempool at all.
If the locktime of your transaction has been set to 2 years later, you have to wait for 2 years and then broadcast your transaction.
That's what I also know. But according to BlackHatCoiner and the BIP he mentioned, it may be possible to broadcast now, have it mined and locked until 2 years later
Both of you refer to the
locktime field. I was referring to OP_CHECKLOCKTIMEVERIFY. They are completely different. The former is checked when you attempt to include its transaction to a block. The latter is checked when you attempt to spend an output.
*This one doesn't really exist, but it exists in concept. It was called OP_BLOCKNUMBER, but the founder warned for security implications: https://bitcointalksearch.org/topic/m.22119
