UNIXBTC
UNIX / Bitcoin
crypto

I've time-locked some coins of mine, it's not too difficult.
You need to use `OP_CHECKLOCKTIMEVERIFY` in the locking script, and push the height or UNIX timestamp up until when you want the coins to be locked.
For a P2PKH output, this would look something like
`2000000 OP_CHECKLOCKTIMEVERIFY OP_DROP OP_DUP OP_HASH160 <pubkey_hash> OP_EQUALVERIFY OP_CHECKSIG`
to lock your coins up until a block height of 2000000.
Then, to spend the coins, you need to wait up until at least block 2000000, specify `nLockTime >= 2000000` and also `nSequence < 0xffffffff`.
Done!
Take into account that such an output is non-standard, so people usually wrap it in a P2SH or P2WSH script. You *can* do it "raw" like I have above and submit the transaction, but you'd typically have to submit it directly to a mining pool, given its non-standardness.

I've time-locked some coins of mine, it's not too difficult.
You need to use `OP_CHECKLOCKTIMEVERIFY` in the locking script, and push the height or UNIX timestamp up until when you want the coins to be locked.
For a P2PKH output, this would look something like
`2000000 OP_CHECKLOCKTIMEVERIFY OP_DROP OP_DUP OP_HASH160 <pubkey_hash> OP_EQUALVERIFY OP_CHECKSIG`
to lock your coins up until a block height of 2000000.
Then, to spend the coins, you need to wait up until at least block 2000000, specify `nLockTime >= 2000000` and also `nSequence < 0xffffffff`.
Done!
Take into account that such an output is non-standard, so people usually wrap it in a P2SH or P2WSH script. You *can* do it "raw" like I have above and submit the transaction, but you'd typically have to submit it directly to a mining pool, given its non-standardness.