-
Notifications
You must be signed in to change notification settings - Fork 906
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
**BROKEN** Peer internal error AWAITING_UNILATERAL: Bad tx ... Peer permanent failure in AWAITING_UNILATERAL: Internal error #4201
Comments
I have bad news. This looks like someone exploited the https://lists.linuxfoundation.org/pipermail/lightning-dev/2019-September/002174.html on your node before the upgrade, and it is only now coming to light (not that it would have helped to know earlier). In particular, your node believes that it's a 0.1 BTC channel, but it's actually a 0.0006 BTC channel (this was the bug). You seem to have shut down your node now? Is 02bb10aaa77a95a358cebb2d112c4de00e47c08f56e89b1acb44 (microlancer.io) your new node? |
I upgraded this node to 0.8.1 immediately when I saw the CVE come out, but maybe someone figured out the exploit independently or simply did it in the few hours before I upgraded. Yeah, I have new node there but it is running LND. |
Well, nothing I can do about getting exploited. Closing this. |
I have the same status after failure in broadcasting tx. AWAITING_UNILATERAL is hanging for days. This is what I have in my debug log.
The important notification. The channel wasn't created. Never. |
Issue and Steps to Reproduce
I have a channel that doesn't seem to want to close properly. In the logs, I see the message:
2020-11-13T10:21:53.461Z BROKEN .... -chan#38497: Peer internal error AWAITING_UNILATERAL: Bad tx .... 2020-11-13T10:21:53.461Z UNUSUAL ....-chan#38497: Peer permanent failure in AWAITING_UNILATERAL: Internal error
I don't know how much of these other log messages will be helpful, but I have a channel that is refusing to close.
getinfo
outputList peers output
List funds output
Links
The text was updated successfully, but these errors were encountered: