pull down to refresh
For APO#2 what securities are in place to prevent users from repeatedly pushing channel updates that contradict each other?
reply
I assume you mean pushing (ie broadcasting) on chain. If you push an old state, say one where you have more Bitcoin than you actually do, all your channel partner needs to do is broadcast the correct version. That’s what ANYPREVOUT does - it allows you to commit/sign a transaction that isn’t bound to any particular previous output, it can be any output. In the this case, the any output it’s binding to is the old (bad) state you pushed.
reply
Ah got it - thank you for clarifying
reply
FWICT:
-
almost anything you can do with APO you can do with CTV... but at big losses in efficiency depending on the construction
-
some uses for lightning are cheaper with APO
-
some uses for vaults are cheaper with CTV
-
CTV has more prep work done
-
APO is a smaller, and seemingly less controversial, code change
ANYPREVOUT
CTV