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

Force-close if closing transaction doesn't confirm in a timely manner #1046

Closed
TheBlueMatt opened this issue Aug 16, 2021 · 1 comment
Closed

Comments

@TheBlueMatt
Copy link
Collaborator

t-bast points out at lightning/bolts#894 (comment) that in the case of option_anysegwit someone could use a segwit script with unknown semantics which is nonstandard due to dust output values or some other reason causing the closing transaction to not be confirmable. Thus, we'll need to force-close in these cases. We already expose an API for users to do so, but its kinda annoying to require users do this manually, so we should do it automatically.

@TheBlueMatt
Copy link
Collaborator Author

Basically fixed in #1065.

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

1 participant