Difference between revisions of "Keys"
Jump to navigation
Jump to search
MiltonPusser (talk | contribs) |
(typo) |
||
| Line 9: | Line 9: | ||
= Channel information = | = Channel information = | ||
== LND == | == LND == | ||
Tip for now, just backup the | Tip for now, just backup the whole ~/.lnd directory. | ||
{{TODO|Write how to backup lnd}} | {{TODO|Write how to backup lnd}} | ||
= 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. | ||
Revision as of 17:37, 30 January 2019
Your Lightning node or wallet will have keys. Look at Backup for instructions.
Bitcoin key (on-chain)
A wallet and lightning node usually hold bitcoins to open channels. If you backup this key you can get your on-chain balance back.
Making backups is not easy. Probably just take your wallet-file... See github for more info. Template:TODO
Channel information
LND
Tip for now, just backup the whole ~/.lnd directory. Template:TODO
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.