-
Notifications
You must be signed in to change notification settings - Fork 44
[Support] Will unilaterall close (force-close) of the Eclair-created channel from the remote (LND) side make funds appear on regular on-chain address of the Eclair-generated seed? #258
Comments
Restoring the seed in a different lightning wallet will not work for off-chain funds. To recover the off-chain funds, you need to restore the seed in eclair-mobile, that will tell your peer to close the channel and you'll get the funds back on-chain. |
If you do the force-close from your lnd node, the result will be the same. |
Note that if there's really no backup recovery possible at all, you may need to use https://github.com/ACINQ/eclair-recovery-tool to recover the main output. |
OK so that's what I wanted to know - you need to perform one more tx to claim. That obviously needs LN info..
That link does not work and searching manually does not help. |
Woops you're right, that's a branch in eclair at the moment: ACINQ/eclair#1197 Can you double-check the google drive backup? That would be the easy solution to recover the funds, otherwise we'll look into the recovery tool option. |
Yes, he said he is completely positive that there's no Eclair backup. He will try building Eclair after exams. |
Relative of mine had Eclair wallet with some funds on-chain and some on LN channel.
That phone is now dead.
He has recovery phrase, recovered into another (BlueWallet, iOS) wallet, but sees on-chain funds only (obviously).
LN Google Drive backup is not found in Eclair installed on Android VM - probably forgot to enable Google Drive backup...
Now, useful fact is that his LN funds are locked in the channel with my LND node.
Question: if I perform force-close (getting my part after 2016 blocks) from LND side, will his balance will be sent to his "regular" on-chain address that will be visible on that other on-chain wallet? Or that force-close address is some sort specific, "LN-related", from different derivation path (or whatever)?
Thanks!
The text was updated successfully, but these errors were encountered: