Quote from: Pmalek on Today at 09:23:39 AM

Another problem is that you don't know when you are going to die. Let's assume you want to leave your coins to your children.

o_e_l_e_o already answered for me - the point is that you can replace the nLocktime transactions regularly.

Just wanted to add that there is another variant I linked in my earlier post in this thread, invented by forum user Andriian and implemented in an experimental version of a mobile wallet, which in some situations can be even even better:

You give your heirs an already signed transaction with two IF_ELSE options: a CSV timelock (after the expiration they can access the coins freely) and a condition that you can move the coins with your own key when you want. They can broadcast it at any time, but when they broadcast it, they need to wait for the timelock to expire to move the coins, for example for a year.

So they can broadcast it as sool you've died. If they maliciously broadcast the transaction while you're still alive, you can move the coins yourself (and speak some serious word with your heir, which may not be a heir anymore in this case

).

This variant has a little bit more trust involved, because in theory you could imagine rare situations where you won't be able to move your coins in time (while still alive, e.g. on a long extreme tourism trip) and your heir could abuse that, but is easier to implement because you don't need to replace transactions as long as you don't move your coins - so it's excellent for a longterm HODL wallet. Even if someone steals the transaction (which could be a paper with a QR code) from your heir and broadcasts it, you will have enough time to react.