Timeline for Question regarding LN node backups
Current License: CC BY-SA 4.0
7 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| May 2, 2019 at 13:38 | comment | added | Rene Pickhardt | Could be that your node detected problems, failed the channel with force closing newest state. In that case there was a timelock on your funds. Your lightning node keeps track of them and redeems them after the timelock this could be the reason why funds did not appear directly | |
| May 2, 2019 at 11:05 | comment | added | baysx | Interesting fact, but almost all my funds appeared few days later after running dev-rescan-outputs (lasted quite long). Anyway, i think this is lucky case and you should not run 'old backup' version in online mode if you have chances to recover the last one node state. In my case i was doing exactly wrong way and ran 'last_state" then 'prev_state' then again 'last_stait'. On second step i had many messages in logfile about 'Recovering funds!' events, so you should not allow to happen this for best experience. anyway, i am happy that protocol itself is pretty fail-proof. | |
| Apr 29, 2019 at 16:08 | comment | added | baysx | It seems that i got expensive lesson about backups :) channels now are closing, i see that onchain funds appear, but it looks that i loosed already about 15% of funds that was on channels. We'll see what happens next, i have still about 50% offchain on inactive channels. What keywords should be searched in logs to see was there claim for all funds on other side or not? | |
| Apr 29, 2019 at 15:46 | comment | added | baysx | After restore i have now about 20 inactive channels. I can connect to almost every node (some nodes went offline) but this doesnt restore channel state to active even after 15 minutes. i have a bunch of inactive channels but what to do now? i cannot close these channels, i am getting "this channel is inactive". Both sides are online. as i understand there is some timeout which will be reached and then channel will auto-close? am i right? | |
| Apr 29, 2019 at 15:40 | vote | accept | baysx | ||
| Apr 29, 2019 at 13:16 | comment | added | cdecker |
It's worth pointing out that state changes happen automatically, e.g., fee changes and HTLC forwarding, so it should never be considered safe to restore if the node had been running inbetween. Shutting down, migrating, the restarting is ok, put one must be absolutely sure the node hadn't been running in the interim. With option_dataloss_protection, now enabled with all up to date implementations, no node should ever inadvertently cheat, but at that point you're at the mercy of the counterparty (see criticism of LNDs SCB scheme).
|
|
| Apr 29, 2019 at 12:20 | history | answered | Rene Pickhardt | CC BY-SA 4.0 |