Channel forcibly closed and funds not returned #17
Comments
gustavocoding
changed the title
|
This is the stuck channel. |
|
Out of curiosity, how would I troubleshoot the issue? Any logfile in the android wallet? |
|
Have a similar issue, have a channel whose creation txid does not exist on the network (can't be found by explorers). Now when trying to close the channel it has been sitting in the closing state for a while. The problem now is not being able to re-open a channel to the same node due to an error message saying that duplicate channels are not allowed (understandable) |
|
@gustavonalle this looks related to ACINQ/eclair#546 @CaveRock that's a different issue, but I see you have opened a separate ticket |
|
Have a similar issue, too. The fund might be locked for 144 blocks, I'm waiting for the result. |
|
I think I have a similar issue. I believe my repo steps were something like this:
This is the funding tx I've put some relevant screen shots below. It's the April 5 @ 14:59:16 transaction from the history: Which does not show any refund of 4eea8... . If I drill down on the opening transaction, it looks like this: Here's what it looks like in the channels list: And drilling down looks like this:
PS> Great App! I love the UI and ability to scan in QR codes to link channels, which works great with 1ml.com. |
|
@pm47 Can I see the logs in the android wallet to see why the channel is stuck on closing? Anything I can do to forcibly close a forcibly closing channel? 😀 |
|
I was able find public info about the channel: https://www.robtex.com/lightning/channel/568071478635462656 The closing tx has 160+ confirmations and one output to a bech32 address. Does that mean the funds went to the other party? This would be really weird as I opened the channel, the other party went OFFLINE and I manually closed the channel. |
@gustavonalle using android studio you will see the logs |
|
Does Android studio connect to my phone to extract the logs? Do I need a rooted phone? |
|
I also just experienced this issue. I'll post as much information as I can. Channel Identifier: 10c3ad51ddc447d4a82ededf6b474e457519c2cd86936ee3618952981d7a9f9d This channel was opened between my phone wallet (eclair) and my desktop lightning node (desktop eclair). I'm fairly certain the app was running in the background on my phone when this happened. I have no reason to believe that my desktop node was offline, so there was no reason for a force close. As of writing this the closing transaction is still unconfirmed. The channel has disappeared completely from my desktop node (no force closing message) and also from 1ml.com. |
#546 looks like the closing tx was not done due to wrong fees, whilst in my case it is in the blockchain but the wallet cannot recover from the closing state |
|
Closing involves not only the commitment tx, but also all the txes that may
send funds back to your wallet. Those txes might have the fee issue.
Le ven. 6 avr. 2018 à 16:37, Gustavo Fernandes <[email protected]> a
écrit :
… @gustavonalle <https://github.com/gustavonalle> this looks related to
ACINQ/eclair#546 <ACINQ/eclair#546>
#546 looks like the closing tx was not done due tonwrong fees, whilst in
my case it is in the blockchain but the wallet cannot recover from the
closing state
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#17 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AB7yvvYyz7B-qSBR8bhRIumG8AFEh_enks5tl32ggaJpZM4TJS16>
.
|
|
@gustavonalle you don't need to root the phone (and you should not root a phone if you have a bitcoin wallet on mainnet) but you need to enable debugging (see https://developer.android.com/studio/debug/dev-options.html). then when you connect you phone to your PC for the first time it will ask you it you want to authorize USB debugging and wil show you the PC's fingerprint. Then you will be able to see the logs in the |
|
@sstone Thanks. Will get the logs as soon as leave this beach and have access to a computer 😁 |
|
@JukeboxRhino I'm not sure I understand your problem: the closing tx that you post is confirmed and has been spent ? |
|
@sstone I think it's because of the issue with eclair desktop linked above (ACINQ/eclair#546). If my desktop node was the one to force close the channel, then my phone wallet would have been able to spend the coins, which it was. |
|
@remyers your closing tx needs to be confirmed 144 times before it can be spent, it was not when you posted but now the phone should be able to spend the closing tx and return the funds to your bitcoin wallet (you should see a new incoming transaction). What happens when you start eclair ? |
|
@JukeboxRhino sorry I still don't understand. the funding tx is spend by a closing tx with 2 outputs, one that can be spent immediately (I guess it was your desktop output, it was spent and the channel closed), the other that cannot be spent before it has been confirmed 144 times and that's not the case yet |
|
@sstone @pm47 I attached the phone to Android Studio but the logs are just android level debug statements regarding UI and events which are pretty useless. Furthermore, it does not allow to show logs from when I closed the channel to see why it didn't close properly. When I asked about logging, I was asking about wallet logs, to try to understand why the channel is permanently on CLOSING state. Does the wallet store logs somewhere? Only by looking at 2 or 3 days ago logs it'd be possible to understand why the wallet failed to refund the channel |
|
I reproduced the issue with the emulator, opening a 1mBTC channel (mainnet) with 02ad6fb8d693dc1e4569bcedefadf5f72a931ae027dc0f0c544b34c1c6f3b9a02b@167.99.50.31:9735 There is a suspect logging at the start though, when initialising the actor system's loggers: I understand that the eclair Scala core is responsible for all 'heavylifting' of the wallet, maybe the ERROR above is causing the logs to be missed? |
The refund transaction can't be published before the commitment tx reaches 144 blocks, which isn't the case yet for your tx I think. This is what makes the bug difficult to diagnose
Interesting, we'll have a look at that |
Yeah, I though about that, I will let the emulator running for a while then. |
|
Btw, is the commitment tx visible in the logs or in the wallet? I can see recurring events printed: But those 2 tx are for the initial on-chain tx in my wallet and for a cooperative close I've done |
|
Those are for transactions related to the on-chain wallet, which is separated from the lightning part. If the refund transaction was sent, it would appear in these messages |
|
Seem to have a similar issue. Happy to help if needed. |
|
Can confirm Method #2 of this tutorial works |
When publishing delayed txes, we need to first watch the parent transaction in order to know how many confirmations it has. Electrum relies on hashes of `pubkeyScript`s in order to track transactions. In order to do this without having the parent transaction at hand, we recompute the `pubkeyScript` from the child transaction witness data and give it to Electrum. But if the script was a `pay2wsh`, we were using the `redeemScript` instead of computing the `pubkeyScript`. This is the root cause of ACINQ/eclair-mobile#17.
|
Worked for me as well. |
|
Method worked like a charm! Just curious, does the "CLOSING (uncooperative) channel entry ever go away? |
|
Can confirm Method #1 of this tutorial works :) |
|
Doesn't work for me. I have two channels stuck in CLOSING. I can see "Eclair Wallet recovery DNS Configuration OK" in the browser, but nothing happens in the wallet. I have tried many times, restarted, rebooted, etc. |
|
Worked for me as well. Thank you |
|
Oh, now suddenly it worked. Not sure if I did anything myself or if it was something else. |
|
Same problem now with the new version (0.3.1). |
|
@nadam can you paste the funding txid of the channel? |
|
b275bd5bb77305a05b9420797e790295e06ee15850e945f0c5007a03f6ae87fc |
|
@nadam I'm guessing this is a 500000 channel? If so, closing tx only has 13 confirmations, the delay for refunds when doing unilateral close is typically 144 blocks |
|
Right, it got closed now. Users are going to be confused about situations like this unless there are clear messages describing what's going on. |
|
Great, in addition to that, it would be good to have a user friendly explanation of why the channel was forcibly closed. Or even better, leave that decision to the user. The app shouldn't close the channel unless the user (or the server) wants to close it. |
|
@pm47 Excuse me, I should have checked better. Anyway, got stuck in this problem last couple of days. Switched DNS and got the "Eclair Wallet recovery DNS Configuration OK" confirmation. But I guess the Electrum server itself is not available, because I get "Electrum Disconnected" in Android UI. Here are the details: Eclair Android 0.3 mainnet funding tx 4bb546485cdc28885efc323107a3addab4d8435baa500e9c844eebcd161f7511 The closing tx has enough confirmations. |
|
Worked for me but I still had to wait hours due to my phone. I kept the dns change on, rebooted a few times, etc but it was later at night on a different network that it finally updated |
|
I'm not able to do it now neither with 1st nor with 2nd option. Is it still working also with current version? |
What do you mean ? The recovery method described in https://github.com/ACINQ/eclair-wallet/wiki/Recover-funds-stuck-in-CLOSING-state-from-Eclair-Wallet-0.3.0 is specific to eclair -mobile 0.3.0 and is not needed for other versions. |
|
I just figure out I'm still on eclair wallet 0.3.0 and non of the solution
is not working now
…On Sun, 6 Oct 2019 at 22:02, Fabrice Drouin ***@***.***> wrote:
Is it still working also with current version?
What do you mean ? The recovery method described in
https://github.com/ACINQ/eclair-wallet/wiki/Recover-funds-stuck-in-CLOSING-state-from-Eclair-Wallet-0.3.0
is specific to eclair -mobile 0.3.0 and is not needed for other versions.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#17?email_source=notifications&email_token=ABEP6GBWVUV76GXDRB64H7DQNI747A5CNFSM4EZFFV5KYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEAOSWMQ#issuecomment-538782514>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/ABEP6GBW6TL6SFMZHVMRIWTQNI747ANCNFSM4EZFFV5A>
.
|
|
@saintego there was an issue on our electrum recovery server that is being fixed, it should be available again in a few hours (I'll update this ticket) |
|
@saintego our Electrum recovery server is online again, please let me know if you still have problems with the recovery process |
|
Thanks a lot, it works
…On Mon, Oct 7, 2019, 22:13 Fabrice Drouin ***@***.***> wrote:
@saintego <https://github.com/saintego> our Electrum recovery server is
online again, please let me know if you still have problems with the
recovery process
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#17?email_source=notifications&email_token=ABEP6GGUGSN7VFVWIRVRGNDQNOJ6DA5CNFSM4EZFFV5KYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEARUYIQ#issuecomment-539184162>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/ABEP6GDYZFLS5AVJ7Z7N6WLQNOJ6DANCNFSM4EZFFV5A>
.
|
|
Hi, is the electrum recovery server still online? I'm having trouble using the DNS recovery protocol. |
|
@SneezyDwarf111 Yes it is online and still works. I'll reply to your message on https://gitter.im/ACINQ/eclair |
|
@sstone Hi, thank you for your work! |
and others
Funding tx was 731c6e69338f4cc58b595227cf5f2b8bf631e645a197445bcc7bf4f57f5098fb, I forcibly closed the channel id fb98507ff5f47bcc5b4497a145e631f68b2b5fcf2752598bc54c8f33696e1c73 and the state in the wallet is still CLOSING.
More than 144 blocks have passed since the funding transaction, shouldn't the funds have been returned?
The text was updated successfully, but these errors were encountered: