I know that you can already set a lock time which allows you to set the future block for which a transaction has to wait until to be confirmed, but would there be a way to specify locking any transaction after that by a set amount of blocks?
Like I send 2 bitcoins to address 1XYZ which is locked for 1 month (a certain amount of blocks). Then once 1XYZ has access to the funds they send to two different addresses, 1ZYX and 1WXY but they both have the same delay of 1 month. And those transactions also have a delay and so on and so on...
I ask this as I am trying to figure out a programatic way of conforming to some certain SEC regulations for something. We are still flushing some things out but I just want to know if this path is possible.
So you are asking if you can encumber all or some number of future transactions that follow the initial one with a delay? (It doesn't seem like the previous answers were talking about more than locking the 1st transaction).
e.g.
1. 2 bitcoins to address 1XYZ which is locked for 1 month
2. then after that month, whomever controls 1XYZ sends to two different addresses, 1ZYX and 1WXY which should also be locked for another month no matter who has the private keys to 1ZYX and 1WXY?
3. Then 1ZYX and 1WXY send elsewhere and those transactions are locked for a month worth of blocks?
4. Does this continue infinitely or does it stop after some number of transactions?
etc
I don't believe that you could encumber future transactions that all originate from a single root as bitcoin is now under the scenario above. Perhaps you could do so with some type of payment channel, but if you can give an example of what you are trying to accomplish, perhaps that would help determine a method to do so.