You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If the responder of a channel initiates the co-op close process, they seem to not have the proofs for the commitment transaction available in the local proof archive.
This results in the following error:
I think we need to call auxSweeper.importOutputProof when the co-op close process starts. Better yet, with a slightly larger change, we can hook into the chanvalidate module for lnd, and make sure that once the funding transaction is confirmed, all the proofs are imported.
…lose
Otherwise, the transfer insert for the responder may fail as they don't
have the funding output in their database, so shipping the transfer
fails as it can't find the proof.
Fixes#985.
…lose
Otherwise, the transfer insert for the responder may fail as they don't
have the funding output in their database, so shipping the transfer
fails as it can't find the proof.
Fixes#985.
…lose
Otherwise, the transfer insert for the responder may fail as they don't
have the funding output in their database, so shipping the transfer
fails as it can't find the proof.
Fixes#985.
Uh oh!
There was an error while loading. Please reload this page.
Found while adding more assertions to the custom channel integration tests in
litd
: lightninglabs/lightning-terminal#784If the responder of a channel initiates the co-op close process, they seem to not have the proofs for the commitment transaction available in the local proof archive.
This results in the following error:
That's why the transfer then never fully completes and the final balance isn't correct.
The text was updated successfully, but these errors were encountered: