Contract-level Relative Timelocks (or, let's talk about ancestry proofs and singletons)

That’s right. For simplicity the last update follows the same format as the previous ones right now, but I think you could even “inline” the settlement transaction into the last update. For N=2 this looks a lot like Daric actually (probably not coincidentally).

I think this strategy gives you a (N - 1) * shared_delay at best, since every party still needs a chance to update in the worst case.

2 Likes