mirror of
https://github.com/ElementsProject/lightning.git
synced 2025-02-20 13:54:36 +01:00
doc: Updated old links and deleted old file
This commit is contained in:
parent
a55915be9e
commit
669fe35359
3 changed files with 1 additions and 26 deletions
|
@ -65,4 +65,4 @@ Once you've started for the first time, there's a script called `contrib/bootstr
|
|||
|
||||
There are also numerous plugins available for Core Lightning which add capabilities: see the [Plugins](doc:plugins) guide, and check out the plugin collection at: <https://github.com/lightningd/plugins>, including [helpme](https://github.com/lightningd/plugins/tree/master/helpme) which guides you through setting up your first channels and customising your node.
|
||||
|
||||
For a less reckless experience, you can encrypt the HD wallet seed: see [HD wallet encryption](doc:securing-keys).
|
||||
For a less reckless experience, you can encrypt the HD wallet seed: see [HD wallet encryption](doc:backup-and-recovery###hsm-secret-backup).
|
||||
|
|
|
@ -1,10 +0,0 @@
|
|||
---
|
||||
title: "Securing keys"
|
||||
slug: "securing-keys"
|
||||
hidden: false
|
||||
createdAt: "2022-11-18T16:28:08.529Z"
|
||||
updatedAt: "2023-01-31T13:52:27.300Z"
|
||||
---
|
||||
You can encrypt the `hsm_secret` content (which is used to derive the HD wallet's master key) by passing the `--encrypted-hsm` startup argument, or by using the `hsmtool` (which you can find in the `tool/` directory at the root of [Core Lightning repository](https://github.com/ElementsProject/lightning)) with the `encrypt` method. You can unencrypt an encrypted `hsm_secret` using the `hsmtool` with the `decrypt` method.
|
||||
|
||||
If you encrypt your `hsm_secret`, you will have to pass the `--encrypted-hsm` startup option to `lightningd`. Once your `hsm_secret` is encrypted, you **will not** be able to access your funds without your password, so please beware with your password management. Also, beware of not feeling too safe with an encrypted `hsm_secret`: unlike for `bitcoind` where the wallet encryption can restrict the usage of some RPC command, `lightningd` always needs to access keys from the wallet which is thus **not locked** (yet), even with an encrypted BIP32 master seed.
|
|
@ -89,21 +89,6 @@ the default `bitcoind` max.
|
|||
|
||||
Effort has been made to get `lightningd` running on Android, [see issue #3484](https://github.com/ElementsProject/lightning/issues/3484). Currently unusable.
|
||||
|
||||
### How to "backup my wallet" ?
|
||||
|
||||
See [Backup and recovery](doc:backup-and-recovery) for a more comprehensive discussion of your options.
|
||||
|
||||
In summary: as a Bitcoin user, one may be familiar with a file or a seed (or some mnemonics) from which it can recover all its funds.
|
||||
|
||||
Core Lightning has an internal bitcoin wallet, which you can use to make "on-chain" transactions, (see [withdraw](ref:lightning-withdraw)). These on-chain funds are backed up via the HD wallet seed, stored in byte-form in `hsm_secret`.
|
||||
|
||||
`lightningd` also stores information for funds locked in Lightning Network channels, which are stored in a database. This database is required for on-going channel updates as well as channel closure. There is no single-seed backup for funds locked in channels.
|
||||
|
||||
While crucial for node operation, snapshot-style backups of the `lightningd` database is **discouraged**, as _any_ loss of state may result in permanent loss of funds. See the [penalty mechanism](https://github.com/lightning/bolts/blob/master/05-onchain.md#revoked-transaction-close-handling) for more information on why any amount of state-loss results in fund loss.
|
||||
|
||||
Real-time database replication is the recommended approach to backing up node data.
|
||||
Tools for replication are currently in active development, using the [`db write` plugin hook](doc:hooks#db_write).
|
||||
|
||||
# Channel Management
|
||||
|
||||
### How to forget about a channel?
|
||||
|
|
Loading…
Add table
Reference in a new issue