f - Document explicit legacy entropy selection

Review feedback removed the automatic legacy keys_seed fallback.

Update the config docs and sample template so operators know an

existing raw seed must be selected explicitly.

Document the new CLI and environment names next to the TOML

fields so non-file configuration is discoverable.

Co-Authored-By: HAL 9000

Author: tnull

contrib/ldk-server-config.toml

@@ -11,11 +11,14 @@ alias = "ldk_server"                          # Lightning node alias
 
 # Node entropy settings
 [node.entropy]
-# Path to a BIP39 mnemonic file. If unset and no legacy `keys_seed` file exists, a fresh
-# 24-word mnemonic is generated on first start. Defaults to "<storage_dir>/keys_mnemonic".
+# Path to a BIP39 mnemonic file. If unset, a fresh 24-word mnemonic is generated on
+# first start. Defaults to "<storage_dir>/keys_mnemonic".
+# CLI/env: --node-entropy-mnemonic-file / LDK_SERVER_NODE_ENTROPY_MNEMONIC_FILE
 #mnemonic_file = "/tmp/ldk-server/keys_mnemonic"
 # Legacy: path to a raw 64-byte seed file used by ldk-server installs initialized before
-# BIP39 mnemonic support. Mutually exclusive with `mnemonic_file`.
+# BIP39 mnemonic support. Configure this explicitly to keep using an existing keys_seed file.
+# CLI/env: --node-entropy-seed-file / LDK_SERVER_NODE_ENTROPY_SEED_FILE
+# Mutually exclusive with `mnemonic_file`.
 #seed_file = "/tmp/ldk-server/keys_seed"
 
 # Storage settings

docs/configuration.md

@@ -152,7 +152,7 @@ Two resolution methods are supported via the `mode` field:
 ```
 <storage_dir>/
   keys_mnemonic          # BIP39 mnemonic (default for new installs)
-  keys_seed              # Legacy raw seed (only present on installs initialized before mnemonic support)
+  keys_seed              # Legacy raw seed (only used when explicitly configured)
   tls.crt                # TLS certificate (PEM)
   tls.key                # TLS private key (PEM)
   <network>/                # e.g., bitcoin/, regtest/, signet/
@@ -174,8 +174,11 @@ defaults can be overridden under `[node.entropy]`:
 
 - `mnemonic_file`: path to the BIP39 mnemonic file. Defaults to `<storage_dir>/keys_mnemonic`. If
   the file does not exist on first start, a fresh 24-word mnemonic is generated and written.
+  CLI/env: `--node-entropy-mnemonic-file` / `LDK_SERVER_NODE_ENTROPY_MNEMONIC_FILE`.
 - `seed_file`: path to a raw 64-byte seed file. Provided for backwards compatibility with installs
   initialized before BIP39 mnemonic support. Mutually exclusive with `mnemonic_file`.
+  CLI/env: `--node-entropy-seed-file` / `LDK_SERVER_NODE_ENTROPY_SEED_FILE`.
 
-For backwards compatibility, if neither field is configured and a `keys_seed` file exists at the
-storage root, ldk-server will continue to use it.
+Legacy raw-seed installs are not auto-detected. To keep using an existing
+`<storage_dir>/keys_seed`, set `seed_file` explicitly or use the corresponding CLI argument or
+environment variable.

docs/operations.md

@@ -49,7 +49,7 @@ setup):
 | File                                   | Priority     | Description                                                                |
 | -------------------------------------- | ------------ | -------------------------------------------------------------------------- |
 | `<storage_dir>/keys_mnemonic`          | **Critical** | BIP39 mnemonic. Required to recover on-chain funds. Default for new installs. |
-| `<storage_dir>/keys_seed`              | **Critical** | Legacy raw seed file. Only present on installs initialized before mnemonic support. |
+| `<storage_dir>/keys_seed`              | **Critical** | Legacy raw seed file. Only used when explicitly configured. |
 | `<network_dir>/ldk_node_data.sqlite`   | **Critical** | Channel state and on-chain wallet data. Required to recover channel funds. |
 | `<network_dir>/ldk_server_data.sqlite` | Nice-to-have | Payment and forwarding history                                             |
 
@@ -196,6 +196,6 @@ Data is stored in per-network subdirectories (`bitcoin/`, `testnet/`, `signet/`,
 etc.) under the storage root. This means you can run multiple networks from one storage
 directory without conflicts.
 
-The `keys_mnemonic` file (or, on legacy installs, `keys_seed`) is shared across networks
-(stored at the storage root, not per-network). Keys are split by network at the derivation
-path level, so the same mnemonic/seed will produce different keys.
+The `keys_mnemonic` file, or an explicitly configured legacy `keys_seed`, is shared across
+networks (stored at the storage root, not per-network). Keys are split by network at the
+derivation path level, so the same mnemonic/seed will produce different keys.