locktime – Invalidates transactions signed after a specified time.

It is impossible to do exactly what you asked, but it is in principle possible to achieve something similar.

Bitcoin does not have a “not valid after block height/block time” structure that prevents transactions from being included if they are not mined quickly.

However, you can configure output to reflect the same conditions.

use OP_CHECKLOCKTIMEVERIFYYou can configure output to be available to the coordinator up to a certain block height or time, and only to you thereafter.

In theory, this could meet the requirement without mining transactions. By providing the Coordinator with a signed transaction to produce the corresponding output, it can broadcast it along with any subtransactions that consume that output.

If there is no need to exercise that bond or if the time limit has passed, there is no benefit to them in broadcasting it.

If the coordinator is not a polite citizen, they may broadcast this even after the timelock has elapsed, resulting in a painful attack, which may result in transaction fees. However, since you can no longer create transactions to use the bond, you can retrieve the value of the bond.