pull down to refresh

This proposal assumes that Alice and Bob each have a clock, and that these clocks do not drift too much relative to each other. The channel may become unusable if clocks differ too much, as discussed below.
Not great Bob. Could be interesting in spite of it though
reply
Wouldn't eltoo reduce the need to do things like this?
In order to resume the activity of a Lightning channel, one needs a backup that contains all the information about the current channel state. The need to perform channel backups has plagued user experience, with many implementations reverting to static backups, which can be used to recover funds, but not to resume channel operations.
Alice would still be in trouble if she lost state and wasn't backing up I guess, but would channel backups still be a "plague"?
reply
Hmm requires OP_Cat too. I'm uneasy about OP_Cat tbh.
reply
Too generic?
reply
Yeah basically. It was originally removed because of a now patched denial of service vector, but you can do eltoo, covenents, and kinds of stuff with just op_cat. Even the block stream article I was reading about op_cat schnorr tricks said it needed deeper review due to what its capable of.
I like the check template verify (CTV) style of BIP better
reply
If it's too generic I can imagine it'd be difficult to preclude DoS attacks aren't possible. I guess we'd have to be suspicious of operations where the computational cost isn't proportional to the operation's size, but I don't know enough about bitcoin script to imagine OP_CAT breaking that.
reply