You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+4-6Lines changed: 4 additions & 6 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -67,17 +67,15 @@ file based backup or the recovered file from the crashed node).
67
67
of the `channel.db` from the node.
68
68
<br/><br/>
69
69
Whatever you do, do **never, ever** replace your `channel.db` file with an old
70
-
version (from a file based backup) and start your node that way.[Read this
71
-
explanation why that can lead to loss of funds.](https://github.com/lightningnetwork/lnd/blob/master/docs/safety.md#file-based-backups)
70
+
version (from a file based backup) and start your node that way.
71
+
[Read this explanation why that can lead to loss of funds.](https://github.com/lightningnetwork/lnd/blob/master/docs/safety.md#file-based-backups)
72
72
73
73
2.**Rescue on-chain balance**: To start the recovery process, we are going to
74
74
re-create the node from scratch. To make sure we don't overwrite any old data
75
75
in the process, make sure the old data directory of your node (usually `.lnd`
76
76
in the user's home directory) is safely moved away (or the whole folder
77
-
renamed) before continuing.
78
-
<br/>
79
-
To start the on-chain recovery, [follow the sub step "Starting On-Chain
80
-
Recovery" of this guide](https://github.com/lightningnetwork/lnd/blob/master/docs/recovery.md#starting-on-chain-recovery).
77
+
renamed) before continuing.<br/>
78
+
To start the on-chain recovery, [follow the sub step "Starting On-Chain Recovery" of this guide](https://github.com/lightningnetwork/lnd/blob/master/docs/recovery.md#starting-on-chain-recovery).
81
79
Don't follow the whole guide, only this single chapter!
82
80
<br/><br/>
83
81
This step is completed once the `lncli getinfo` command shows both
0 commit comments