Implement recent spec changes regarding collab channel close outputs#7542
Implement recent spec changes regarding collab channel close outputs#7542SomberNight merged 3 commits intospesmilo:masterfrom
Conversation
I guess
Yes, let's keep that for now. We know from experience that others accept it during channel open, and I think ~500 sat outputs are hardly ever worth sweeping anyway (so not much point in lowering it IMO).
Hmm. Well I guess it's not critical, as the user can force-close manually if needed. electrum/electrum/lnchannel.py Line 1452 in 1ff9f99 it's ~harmless though. |
lightning/bolts#672 We check the received shutdown script against higher segwit versions and accept closing to that script if option_shutdown_anysegwit has been negotiated.
c9b3185 to
538b2eb
Compare
|
Agree with your other points, thanks.
I think so, yes, very confusing 😕. |
538b2eb to
8a002b0
Compare
* on channel opening we verify that the peer's dust limit is above 354 sat, the limit for unknown segwit versions * we constrain the allowed scriptpubkey types for channel closing * we check that the remote's output is above the relay dust limit for the collaborative close case
8a002b0 to
e97f350
Compare
Fixes #7541
option_shutdown_anysegwit, which lets peers close their channels to taproot scripts.Fulfills spec changes:
option_shutdown_anysegwit(Feature 26/27) lightning/bolts#672Related:
Todo: