Skip to content

bug: Do not forget a zeroconf channel if it doesn't confirm #8147

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

Open
cdecker opened this issue Mar 7, 2025 · 1 comment
Open

bug: Do not forget a zeroconf channel if it doesn't confirm #8147

cdecker opened this issue Mar 7, 2025 · 1 comment

Comments

@cdecker
Copy link
Member

cdecker commented Mar 7, 2025

While debugging an issue on Greenlight, we found that one of the nodes
had forgotten a channel that it was waiting to confirm. This was caused by the "forget non-confirming channel" logic here:

log_unusual(channel->log,

The problem is that this code assumes that a channel that we aren't
funding cannot hold any funds that we own, hence we can forget the
channel without any issues. This used to be true until we introduced
zeroconf support. Now even unconfirmed channels may contain owned
funds, if they are zeroconf channels.

We need to adjust the logic to skip channels that are zeroconf && owned_sats > 0.

@cdecker
Copy link
Member Author

cdecker commented Mar 7, 2025

I'm not quite sure why the check here isn't preserving the channel:

0dde74f

Ah, because it only considers funds we contributed to the funding, not our current owned funds.

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