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

Detect double-spent dual funded channels #371

Open
t-bast opened this issue Sep 21, 2022 · 0 comments
Open

Detect double-spent dual funded channels #371

t-bast opened this issue Sep 21, 2022 · 0 comments

Comments

@t-bast
Copy link
Member

t-bast commented Sep 21, 2022

When using dual funding, we cannot simply forget unconfirmed channels after 2016 blocks if we contributed to the funding amount. There are multiple funding transaction candidates, and any of them may (eventually) confirm. The only case where we can forget such an unconfirmed channel is when we have proof that all funding transaction candidates have been double-spent by a transaction that doesn't belong to the funding candidates set.

However, this is very tedious to implement on top of the electrum protocol: we would likely need to subscribe to every input of every funding transaction candidate, aggregate their status and then run non-trivial logic to verify that funding transactions were all correctly double-spent.

This isn't done right now, which means that a double-spent dual funded channel will not be detected and will stay stuck in the WaitForFundingConfirmed state.

@t-bast t-bast changed the title Detect double-spent dual funding channels Detect double-spent dual funded channels Sep 21, 2022
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