Hi all,
In Adelaide we proposed that CSV delays be symmetric; that the
to-self output would be delayed to avoid weird "no, you close!" games.
Unfortunately, Roasbeef points out that this undermines the
great strength of the option_static_remotekey, which allows a
disaster-recovery scenario to easily discover any unknown unilateral
closes using only a master seed. Turns out, this "I deleted everything
but I kept my seed!" is a real thing.
We could still use the max of the two sides' CSV, but that's
already a choice that sides can make (if accepting, simply offer the
same value, and if opening, error and retry if their accept contains a
larger value).
So I think this proposal should be abandoned.
Thoughts?
Rusty.
_______________________________________________
Lightning-dev mailing list
[email protected]
https://lists.linuxfoundation.org/mailman/listinfo/lightning-dev
