Backup - Revision history

MiltonPusser: /* Channel information */

2019-04-18T07:14:29Z

Channel information

← Older revision		Revision as of 07:14, 18 April 2019
Line 19:		Line 19:
	See [https://github.com/lightningnetwork/lnd/blob/master/docs/recovery.md recovery] docs by lnd.		See [https://github.com/lightningnetwork/lnd/blob/master/docs/recovery.md recovery] docs by lnd.

	=== Backup channelbackup using inotify (watch changes)		=== Backup channelbackup using inotify (watch changes) ===
	[https://gist.github.com/alexbosworth/2c5e185aedbdac45a03655b709e255a3 Post by Alex Bosworth]		[https://gist.github.com/alexbosworth/2c5e185aedbdac45a03655b709e255a3 Post by Alex Bosworth]

MiltonPusser: /* Channel information */

2019-04-18T07:14:19Z

Channel information

← Older revision		Revision as of 07:14, 18 April 2019
Line 18:		Line 18:

	See [https://github.com/lightningnetwork/lnd/blob/master/docs/recovery.md recovery] docs by lnd.		See [https://github.com/lightningnetwork/lnd/blob/master/docs/recovery.md recovery] docs by lnd.

			=== Backup channelbackup using inotify (watch changes)
			[https://gist.github.com/alexbosworth/2c5e185aedbdac45a03655b709e255a3 Post by Alex Bosworth]

	=== Example Static channel backup commands ===		=== Example Static channel backup commands ===

MiltonPusser: /* Channel information */

2019-04-12T13:05:25Z

Channel information

← Older revision		Revision as of 13:05, 12 April 2019
Line 13:		Line 13:
	{{NOTE\|Static Channel backups are suported since [[Lnd]] version 6}}		{{NOTE\|Static Channel backups are suported since [[Lnd]] version 6}}

	Once you start a channel, take a [https://github.com/lightningnetwork/lnd/pull/2313 static channel backup]. This has to be done only once.		Once you start a channel, take a [https://github.com/lightningnetwork/lnd/pull/2313 static channel backup]. This has to be done only once. Or take a backup of the channels.backup file in the same location that we store all the other files. Users will at any time be able to safely copy and backup this file

	After that, if your node dies, you can recover using the seed + the static-channel-backup and retrieve both your onchain and channel balance!		After that, if your node dies, you can recover using the seed + the static-channel-backup and retrieve both your onchain and channel balance!

MiltonPusser at 13:01, 12 April 2019

2019-04-12T13:01:20Z

← Older revision		Revision as of 13:01, 12 April 2019
Line 1:		Line 1:
	~~{{ALERT\|Reliable~~ backups ~~are being worked on at~~ the ~~moment}}~~		Recent Lightning implementations have made backups easier. It is important to understand the difference between wallet and channel funds.

	~~Making backups~~ is ~~not easy~~. ~~You can backup~~ your [[~~Keys\|key~~]]~~, but to recover a disk failure (for example), you still need the channel state~~.		You can easily get your wallet balance back by recovering your seed. Getting your channel funds back is harder. If you would have an old version of your channel, you broadcast an old state, the counterparty (peer) detects [[Fraud]] and takes your funds.

	~~The problem~~ is ~~that if~~ you ~~announce an old~~ channel state ~~(after you recovered a backup), this is detected as [[Fraud]] and you might lose your funds~~.		That is why you need to backup your channel state too.

	= ~~Poor mans solution~~=		= Backup wallet funds =
	~~Probably just take your~~ wallet~~-file... See [https://github~~.~~com/lightningnetwork/lnd/issues/732 github for more info]~~.		Use the wallet seed. You get this at installation. It can not be recovered ([[Lnd]]).

	~~= Hardware =~~
	~~If you’re putting a lot of money on your Lightning routing node, please use a reliable hard drives~~ (~~with mirroring).~~

	~~= Data Loss Protection =~~
	[[~~Data loss protection~~]]

	= Channel information =		= Channel information =
			The second important thing to backup is channel states.
	== LND ==		== LND ==
	{{NOTE\|~~On 2019-04-02~~ Static Channel ~~Backup was merged into LND Master}}~~		{{NOTE\|Static Channel backups are suported since [[Lnd]] version 6}}
	~~{{NOTE\|See~~ [~~https://github.com/lightningnetwork/lnd/blob/master/docs/recovery.md recovery~~] ~~docs by lnd~~}}
	Once you start a channel, take a [https://github.com/lightningnetwork/lnd/pull/2313 static channel backup]. This has to be done only once.		Once you start a channel, take a [https://github.com/lightningnetwork/lnd/pull/2313 static channel backup]. This has to be done only once.

	After that, if your node dies, you can recover using the seed + the static-channel-backup and retrieve both your onchain and channel balance!		After that, if your node dies, you can recover using the seed + the static-channel-backup and retrieve both your onchain and channel balance!

			See [https://github.com/lightningnetwork/lnd/blob/master/docs/recovery.md recovery] docs by lnd.

	=== Example Static channel backup commands ===		=== Example Static channel backup commands ===
Line 129:		Line 126:
	= Commitment revocation private key =		= Commitment revocation private key =
	Every commitment transaction has a unique commitment revocation private-key value that allows the other peer to spend all outputs immediately: revealing this key is how old commitment transactions are revoked. To support revocation, each output of the commitment transaction refers to the commitment revocation public key.		Every commitment transaction has a unique commitment revocation private-key value that allows the other peer to spend all outputs immediately: revealing this key is how old commitment transactions are revoked. To support revocation, each output of the commitment transaction refers to the commitment revocation public key.

			= Hardware =
			If you’re putting a lot of money on your Lightning routing node, please use a reliable hard drives (with mirroring).

			= Data Loss Protection =
			[[Data loss protection]]

MiltonPusser: /* Channel information */

2019-04-12T06:22:23Z

Channel information

← Older revision		Revision as of 06:22, 12 April 2019
Line 17:		Line 17:
	== LND ==		== LND ==
	{{NOTE\|On 2019-04-02 Static Channel Backup was merged into LND Master}}		{{NOTE\|On 2019-04-02 Static Channel Backup was merged into LND Master}}
			{{NOTE\|See [https://github.com/lightningnetwork/lnd/blob/master/docs/recovery.md recovery] docs by lnd}}
	Once you start a channel, take a [https://github.com/lightningnetwork/lnd/pull/2313 static channel backup]. This has to be done only once.		Once you start a channel, take a [https://github.com/lightningnetwork/lnd/pull/2313 static channel backup]. This has to be done only once.

MiltonPusser: /* Channel information */

2019-04-02T08:01:20Z

Channel information

← Older revision		Revision as of 08:01, 2 April 2019
Line 18:		Line 18:
	{{NOTE\|On 2019-04-02 Static Channel Backup was merged into LND Master}}		{{NOTE\|On 2019-04-02 Static Channel Backup was merged into LND Master}}
	Once you start a channel, take a [https://github.com/lightningnetwork/lnd/pull/2313 static channel backup]. This has to be done only once.		Once you start a channel, take a [https://github.com/lightningnetwork/lnd/pull/2313 static channel backup]. This has to be done only once.

			After that, if your node dies, you can recover using the seed + the static-channel-backup and retrieve both your onchain and channel balance!

	=== Example Static channel backup commands ===		=== Example Static channel backup commands ===

MiltonPusser: /* Channel information */

2019-04-02T05:49:25Z

Channel information

← Older revision		Revision as of 05:49, 2 April 2019
Line 16:		Line 16:
	= Channel information =		= Channel information =
	== LND ==		== LND ==
	~~For now, just backup the whole ~/.lnd directory.~~		{{NOTE\|On 2019-04-02 Static Channel Backup was merged into LND Master}}
	{{NOTE\|~~There is work underway to make backup better in 6.0:~~ https://github.com/lightningnetwork/lnd/pull/~~1364 }}~~		Once you start a channel, take a [https://github.com/lightningnetwork/lnd/pull/2313 static channel backup]. This has to be done only once.

	=== Example Static channel backup commands ===		=== Example Static channel backup commands ===
	<pre>		<pre>

MiltonPusser at 06:34, 1 April 2019

2019-04-01T06:34:18Z

← Older revision		Revision as of 06:34, 1 April 2019
Line 18:		Line 18:
	For now, just backup the whole ~/.lnd directory.		For now, just backup the whole ~/.lnd directory.
	{{NOTE\|There is work underway to make backup better in 6.0: https://github.com/lightningnetwork/lnd/pull/1364 }}		{{NOTE\|There is work underway to make backup better in 6.0: https://github.com/lightningnetwork/lnd/pull/1364 }}
	=== Example Static channel backup commands ==		=== Example Static channel backup commands ===
	<pre>		<pre>
	>tlncli exportchanbackup --all		>tlncli exportchanbackup --all

MiltonPusser at 06:34, 1 April 2019

2019-04-01T06:34:08Z

@@ Line 17: / Line 17: @@
 == LND ==
 For now, just backup the whole ~/.lnd directory.
-{{NOTE|There is work underway to make backup better in 6.0: https://github.com/lightningnetwork/lnd/pull/1364 }}
+>tlncli restorechanbackup --multi_backup 0f955a78d0df14db44769c946a537a9c81174a097e3***6ecf7f4ab1afaa0e06
 = Commitment revocation private key =
 Every commitment transaction has a unique commitment revocation private-key value that allows the other peer to spend all outputs immediately: revealing this key is how old commitment transactions are revoked. To support revocation, each output of the commitment transaction refers to the commitment revocation public key.

MiltonPusser: Removed redirect to Keys and backups

2019-02-27T16:17:45Z

Removed redirect to Keys and backups

← Older revision		Revision as of 16:17, 27 February 2019
Line 1:		Line 1:
	~~#REDIRECT~~ [[Keys and ~~backups~~]]		{{ALERT\|Reliable backups are being worked on at the moment}}

			Making backups is not easy. You can backup your [[Keys\|key]], but to recover a disk failure (for example), you still need the channel state.

			The problem is that if you announce an old channel state (after you recovered a backup), this is detected as [[Fraud]] and you might lose your funds.

			= Poor mans solution=
			Probably just take your wallet-file... See [https://github.com/lightningnetwork/lnd/issues/732 github for more info].

			= Hardware =
			If you’re putting a lot of money on your Lightning routing node, please use a reliable hard drives (with mirroring).

			= Data Loss Protection =
			[[Data loss protection]]

			= Channel information =
			== LND ==
			For now, just backup the whole ~/.lnd directory.

			{{NOTE\|There is work underway to make backup better in 6.0: https://github.com/lightningnetwork/lnd/pull/1364 }}

			= Commitment revocation private key =
			Every commitment transaction has a unique commitment revocation private-key value that allows the other peer to spend all outputs immediately: revealing this key is how old commitment transactions are revoked. To support revocation, each output of the commitment transaction refers to the commitment revocation public key.