Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

to_self_delay cannot be updated after opening a channel #1144

Closed
AndySchroder opened this issue Mar 2, 2024 · 3 comments
Closed

to_self_delay cannot be updated after opening a channel #1144

AndySchroder opened this issue Mar 2, 2024 · 3 comments

Comments

@AndySchroder
Copy link

As far as I can tell, the to_self_delay cannot be updated after opening a channel. Can it? With dynamic fee markets I think the two parties in a channel should be able to agree to update the to_self_delay with a new commitment transaction at any time. Is there any technical reason why this cannot be possible, or is there just no communication protocol for doing it yet?

@saubyk
Copy link

saubyk commented Mar 2, 2024

Can be addressed with dynamic commitments?
#1117

@t-bast
Copy link
Collaborator

t-bast commented Mar 4, 2024

is there just no communication protocol for doing it yet?

That's exactly why, and also because it's not a very high priority feature (to_self_delay is only used when force-closing, which shouldn't happen anyway). This can be done during a splice, or with any other "dynamic commitments upgrade" protocol.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants