Stuck on an issue?
Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
A valid channel closed by Eclair Mobile without human intervention
See original GitHub issueIssue Description
Today I got a perfectly valid channel closed. On Android. Eclair Mobile 0.4.8.
New-line feeds added for readability:
local/remote feerates are too different:
remoteFeeratePerKw=2781
localFeeratePerKw=45000
It was like this. I was randomly checking everything is OK before going to a bitcoin caffee, so I turned on Eclair Mobile, waited a while to see the channel is online. Everything was fine. I turned off WiFi (hoping to save some energy with this old phone) and the notification appeared about the channel being closed uncooperatively by my side. What? I did not do anything to close the channel. Maybe there is a bug which would let interpret a half-received message anyway and that would cause this strange behavior.
Time: ~14:38 EU time, today (2019-08-04)
Peer Node Id: 03864ef ... a3f8f (acinq mainnet node)
Funded by the peer
...Let me know what other information I shall provide, but I think all you can find is that my node initiated an unilateral closing of a channel...
I would expect the valid channels to stay up and to not be closed by magic on “my” side.
It closed the channel without asking any question.
In order to reproduce, I think you can try to turn off WiFi the moment Eclair Mobile receives gossip about feerate.
0.4.8 installed from the Play Store
Android 8.1.0 (crDroid) on Samsung S4 mini
A similarly sounding issue: https://github.com/ACINQ/eclair/issues/640 The relevant source from where the channel-closing message is: See https://github.com/ACINQ/eclair/blob/master/eclair-core/src/main/scala/fr/acinq/eclair/channel/ChannelExceptions.scala#L56
I did not have logging turned on when it happened.
No loss of funds. They will be sent to me after refund delay. Let me know how I can help in order that this issue is fixed and does not happen to anyone again.
Issue Analytics
- State:
- Created 4 years ago
- Comments:5 (3 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
Closing this stale issue. There is activity in the spec to leverage CPFP and RBF which will allow us to move fee management to the bitcoin wallet instead of the channel management. That will get rid of those issues.
This may be related: https://github.com/ACINQ/eclair-mobile/issues/118 but in my case I was connecting the latest (0.4.8) version of Eclair Mobile with the official mainnet Acinq node and the channel close happened on the Mobile side.