-
Couldn't load subscription status.
- Fork 2.2k
[WIP] Funding detect double spends #1755
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
[WIP] Funding detect double spends #1755
Conversation
827818b to
9c43df4
Compare
|
Not ready for review. |
| // the remaining part of the opening process, we must wait for | ||
| // this process to finish (either successfully or with some | ||
| // error), before the fundingManager can be shut down. | ||
| // We now launch a goroutine that will wiat for the funding |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
| // We now launch a goroutine that will wiat for the funding | |
| // We now launch a goroutine that will wait for the funding |
| ).(*lnwire.AcceptChannel) | ||
| } | ||
|
|
||
| // TestFundingManagerFundingDoubleSpend tests that we correctly handles the |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
| // TestFundingManagerFundingDoubleSpend tests that we correctly handles the | |
| // TestFundingManagerFundingDoubleSpend tests that we correctly handle the |
|
Gonna close this as it is outdated and unfinished. I still think this is the way to go to solve #386 though. |
This PR makes the
fundingmanageraware of transaction spending inputs to the funding transaction, invalidating the funding tx. In this case we will cancel the funding flow.TODO:
pkScriptfor funding tx inputsFixes #1494
Fixes #1623
Blocked by #1910