2019-12-29 16:12:06 +03:00
|
|
|
; Example configuration for lnd.
|
|
|
|
;
|
2020-10-08 10:10:57 +03:00
|
|
|
; The default location for this file is in ~/.lnd/lnd.conf on POSIX OSes,
|
|
|
|
; $LOCALAPPDATA/Lnd/lnd.conf on Windows,
|
|
|
|
; ~/Library/Application Support/Lnd/lnd.conf on Mac OS and $home/lnd/lnd.conf on
|
|
|
|
; Plan9.
|
|
|
|
; The default location of this file can be overwritten by specifying the
|
|
|
|
; --configfile= flag when starting lnd.
|
|
|
|
;
|
2019-12-29 16:12:06 +03:00
|
|
|
; Boolean values can be specified as true/false or 1/0.
|
|
|
|
|
2017-11-12 05:58:06 +03:00
|
|
|
[Application Options]
|
|
|
|
|
2017-12-09 00:16:12 +03:00
|
|
|
; The directory that lnd stores all wallet, chain, and channel related data
|
|
|
|
; within The default is ~/.lnd/data on POSIX OSes, $LOCALAPPDATA/Lnd/data on
|
|
|
|
; Windows, ~/Library/Application Support/Lnd/data on Mac OS, and $home/lnd/data
|
|
|
|
; on Plan9. Environment variables are expanded so they may be used. NOTE:
|
|
|
|
; Windows environment variables are typically %VARIABLE%, but they must be
|
|
|
|
; accessed with $VARIABLE here. Also, ~ is expanded to $LOCALAPPDATA on Windows.
|
|
|
|
; datadir=~/.lnd/data
|
2017-11-12 05:58:06 +03:00
|
|
|
|
2017-12-09 00:16:12 +03:00
|
|
|
; The directory that logs are stored in. The logs are auto-rotated by default.
|
|
|
|
; Rotated logs are compressed in place.
|
|
|
|
; logdir=~/.lnd/logs
|
2017-11-12 05:58:06 +03:00
|
|
|
|
2018-04-07 01:11:42 +03:00
|
|
|
; Number of logfiles that the log rotation should keep. Setting it to 0 disables deletion of old log files.
|
|
|
|
; maxlogfiles=3
|
2018-05-23 16:41:59 +03:00
|
|
|
;
|
2018-04-07 01:11:42 +03:00
|
|
|
; Max log file size in MB before it is rotated.
|
|
|
|
; maxlogfilesize=10
|
|
|
|
|
2020-03-17 22:43:14 +03:00
|
|
|
; Time after which an RPCAcceptor will time out and return false if
|
|
|
|
; it hasn't yet received a response.
|
|
|
|
; acceptortimeout=15s
|
|
|
|
|
2017-12-09 00:16:12 +03:00
|
|
|
; Path to TLS certificate for lnd's RPC and REST services.
|
|
|
|
; tlscertpath=~/.lnd/tls.cert
|
2017-11-12 05:58:06 +03:00
|
|
|
|
2017-12-09 00:16:12 +03:00
|
|
|
; Path to TLS private key for lnd's RPC and REST services.
|
|
|
|
; tlskeypath=~/.lnd/tls.key
|
|
|
|
|
2019-11-22 12:22:28 +03:00
|
|
|
; Adds an extra ip to the generated certificate. Setting multiple tlsextraip= entries is allowed.
|
2018-08-14 08:10:54 +03:00
|
|
|
; (old tls files must be deleted if changed)
|
|
|
|
; tlsextraip=
|
|
|
|
|
2019-11-22 12:22:28 +03:00
|
|
|
; Adds an extra domain to the generate certificate. Setting multiple tlsextradomain= entries is allowed.
|
2018-08-14 08:10:54 +03:00
|
|
|
; (old tls files must be deleted if changed)
|
|
|
|
; tlsextradomain=
|
|
|
|
|
2020-08-21 04:00:15 +03:00
|
|
|
; If set, then all certs will automatically be refreshed if they're close to
|
|
|
|
; expiring, or if any parameters related to extra IPs or domains in the cert
|
|
|
|
; change.
|
|
|
|
; tlsautorefresh=true
|
|
|
|
|
2021-04-06 06:23:33 +03:00
|
|
|
; The duration from generating the self signed certificate to the certificate
|
|
|
|
; expiry date. Valid time units are {s, m, h}.
|
|
|
|
; The below value is about 14 months (14 * 30 * 24 = 10080)
|
|
|
|
; tlscertduration=10080h
|
|
|
|
|
2020-10-08 10:10:57 +03:00
|
|
|
; Do not include the interface IPs or the system hostname in TLS certificate,
|
|
|
|
; use first --tlsextradomain as Common Name instead, if set.
|
|
|
|
; tlsdisableautofill=true
|
|
|
|
|
2020-08-21 04:00:15 +03:00
|
|
|
; A list of domains for lnd to periodically resolve, and advertise the resolved
|
|
|
|
; IPs for the backing node. This is useful for users that only have a dynamic IP,
|
|
|
|
; or want to expose the node at a domain.
|
|
|
|
; externalhosts=my-node-domain.com
|
|
|
|
|
2019-01-07 20:48:02 +03:00
|
|
|
; Sets the directory to store Let's Encrypt certificates within
|
|
|
|
; letsencryptdir=~/.lnd/letsencrypt
|
|
|
|
|
2020-09-17 13:31:01 +03:00
|
|
|
; The IP:port on which lnd will listen for Let's Encrypt challenges. Let's
|
2019-01-07 20:48:02 +03:00
|
|
|
; Encrypt will always try to contact on port 80. Often non-root processes are
|
|
|
|
; not allowed to bind to ports lower than 1024. This configuration option allows
|
|
|
|
; a different port to be used, but must be used in combination with port
|
2020-09-17 13:31:01 +03:00
|
|
|
; forwarding from port 80. This configuration can also be used to specify
|
|
|
|
; another IP address to listen on, for example an IPv6 address.
|
|
|
|
; letsencryptlisten=localhost:8080
|
2019-01-07 20:48:02 +03:00
|
|
|
|
|
|
|
; Request a Let's Encrypt certificate for this domain. Note that the certicate
|
|
|
|
; is only requested and stored when the first rpc connection comes in.
|
|
|
|
; letsencryptdomain=example.com
|
|
|
|
|
2017-12-09 00:16:12 +03:00
|
|
|
; Disable macaroon authentication. Macaroons are used are bearer credentials to
|
|
|
|
; authenticate all RPC access. If one wishes to opt out of macaroons, uncomment
|
|
|
|
; the line below.
|
|
|
|
; no-macaroons=true
|
2017-11-12 05:58:06 +03:00
|
|
|
|
2020-09-20 00:20:48 +03:00
|
|
|
; Enable free list syncing for the default bbolt database. This will decrease
|
2020-08-21 04:00:15 +03:00
|
|
|
; start up time, but can result in performance degradation for very large
|
|
|
|
; databases, and also result in higher memory usage. If "free list corruption"
|
|
|
|
; is detected, then this flag may resolve things.
|
|
|
|
; sync-freelist=true
|
|
|
|
|
2018-05-23 16:41:59 +03:00
|
|
|
; Path to write the admin macaroon for lnd's RPC and REST services if it
|
2017-12-09 00:16:12 +03:00
|
|
|
; doesn't exist. This can be set if one wishes to store the admin macaroon in a
|
2018-08-22 23:11:20 +03:00
|
|
|
; distinct location. By default, it is stored within lnd's network directory.
|
|
|
|
; Applications that are able to read this file, gain admin macaroon access.
|
|
|
|
; adminmacaroonpath=~/.lnd/data/chain/bitcoin/simnet/admin.macaroon
|
2017-11-12 05:58:06 +03:00
|
|
|
|
|
|
|
; Path to write the read-only macaroon for lnd's RPC and REST services if it
|
2017-12-09 00:16:12 +03:00
|
|
|
; doesn't exist. This can be set if one wishes to store the read-only macaroon
|
|
|
|
; in a distinct location. The read only macaroon allows users which can read
|
2018-08-22 23:11:20 +03:00
|
|
|
; the file to access RPCs which don't modify the state of the daemon. By
|
|
|
|
; default, it is stored within lnd's network directory.
|
|
|
|
; readonlymacaroonpath=~/.lnd/data/chain/bitcoin/simnet/readonly.macaroon
|
|
|
|
|
|
|
|
; Path to write the invoice macaroon for lnd's RPC and REST services if it
|
|
|
|
; doesn't exist. This can be set if one wishes to store the invoice macaroon in
|
|
|
|
; a distinct location. By default, it is stored within lnd's network directory.
|
|
|
|
; The invoice macaroon allows users which can read the file to gain read and
|
|
|
|
; write access to all invoice related RPCs.
|
|
|
|
; invoicemacaroonpath=~/.lnd/data/chain/bitcoin/simnet/invoice.macaroon
|
2017-11-12 05:58:06 +03:00
|
|
|
|
2020-08-21 04:00:15 +03:00
|
|
|
; A period to wait before for closing channels with outgoing htlcs that have
|
|
|
|
; timed out and are a result of this nodes instead payment. In addition to our
|
|
|
|
; current block based deadline, is specified this grace period will also be taken
|
2020-10-08 10:10:58 +03:00
|
|
|
; into account.
|
2020-08-21 04:00:15 +03:00
|
|
|
; payments-expiration-grace-period=30
|
|
|
|
|
2018-05-23 16:41:59 +03:00
|
|
|
|
|
|
|
; Specify the interfaces to listen on for p2p connections. One listen
|
2017-12-17 20:28:38 +03:00
|
|
|
; address per line.
|
|
|
|
; All ipv4 on port 9735:
|
|
|
|
; listen=0.0.0.0:9735
|
|
|
|
; On all ipv4 interfaces on port 9735 and ipv6 localhost port 9736:
|
|
|
|
; listen=0.0.0.0:9735
|
|
|
|
; listen=[::1]:9736
|
|
|
|
|
2018-05-23 16:41:59 +03:00
|
|
|
; Disable listening for incoming p2p connections. This will override all
|
2017-12-17 20:28:38 +03:00
|
|
|
; listeners.
|
2019-12-29 16:12:06 +03:00
|
|
|
; nolisten=true
|
2017-12-17 20:28:38 +03:00
|
|
|
|
2018-05-23 16:41:59 +03:00
|
|
|
; Specify the interfaces to listen on for gRPC connections. One listen
|
2017-12-17 20:28:38 +03:00
|
|
|
; address per line.
|
|
|
|
; Only ipv4 localhost on port 10009:
|
|
|
|
; rpclisten=localhost:10009
|
|
|
|
; On ipv4 localhost port 10009 and ipv6 port 10010:
|
|
|
|
; rpclisten=localhost:10009
|
|
|
|
; rpclisten=[::1]:10010
|
2018-05-23 16:41:59 +03:00
|
|
|
; On an Unix socket:
|
|
|
|
; rpclisten=unix:///var/run/lnd/lnd-rpclistener.sock
|
2017-12-17 20:28:38 +03:00
|
|
|
|
2018-05-23 16:41:59 +03:00
|
|
|
; Specify the interfaces to listen on for REST connections. One listen
|
2017-12-17 20:28:38 +03:00
|
|
|
; address per line.
|
|
|
|
; All ipv4 interfaces on port 8080:
|
|
|
|
; restlisten=0.0.0.0:8080
|
|
|
|
; On ipv4 localhost port 80 and 443:
|
|
|
|
; restlisten=localhost:80
|
|
|
|
; restlisten=localhost:443
|
2018-05-23 16:41:59 +03:00
|
|
|
; On an Unix socket:
|
|
|
|
; restlisten=unix:///var/run/lnd-restlistener.sock
|
2017-12-09 00:16:12 +03:00
|
|
|
|
2020-08-21 04:00:15 +03:00
|
|
|
; A series of domains to allow cross origin access from. This controls the CORs
|
|
|
|
; policy of the REST RPC proxy.
|
|
|
|
; restcors=https://my-special-site.com
|
|
|
|
|
2017-11-12 05:58:06 +03:00
|
|
|
|
2017-12-09 00:16:12 +03:00
|
|
|
; Adding an external IP will advertise your node to the network. This signals
|
|
|
|
; that your node is available to accept incoming channels. If you don't wish to
|
2018-03-07 00:03:26 +03:00
|
|
|
; advertise your node, this value doesn't need to be set. Unless specified
|
|
|
|
; (with host:port notation), the default port (9735) will be added to the
|
|
|
|
; address.
|
|
|
|
; externalip=
|
2018-06-13 04:31:37 +03:00
|
|
|
;
|
|
|
|
; Instead of explicitly stating your external IP address, you can also enable
|
|
|
|
; UPnP or NAT-PMP support on the daemon. Both techniques will be tried and
|
|
|
|
; require proper hardware support. In order to detect this hardware support,
|
|
|
|
; `lnd` uses a dependency that retrieves the router's gateway address by using
|
|
|
|
; different built-in binaries in each platform. Therefore, it is possible that
|
|
|
|
; we are unable to detect the hardware and `lnd` will exit with an error
|
|
|
|
; indicating this. This option will automatically retrieve your external IP
|
|
|
|
; address, even after it has changed in the case of dynamic IPs, and advertise
|
|
|
|
; it to the network using the ports the daemon is listening on. This does not
|
|
|
|
; support devices behind multiple NATs.
|
|
|
|
; nat=true
|
2017-11-12 05:58:06 +03:00
|
|
|
|
2020-10-08 10:10:57 +03:00
|
|
|
; Disable listening for incoming peer connections.
|
|
|
|
; nolisten=true
|
|
|
|
|
|
|
|
; Disable REST API.
|
|
|
|
; norest=true
|
|
|
|
|
2020-11-11 11:41:23 +03:00
|
|
|
; Disable TLS for the REST API.
|
|
|
|
; no-rest-tls=true
|
|
|
|
|
2020-10-08 10:10:57 +03:00
|
|
|
; Shortest backoff when reconnecting to persistent peers. Valid time units are
|
|
|
|
; {s, m, h}.
|
|
|
|
; minbackoff=1s
|
|
|
|
|
|
|
|
; Longest backoff when reconnecting to persistent peers. Valid time units are
|
|
|
|
; {s, m, h}.
|
|
|
|
; maxbackoff=1h
|
|
|
|
|
2020-08-25 07:54:31 +03:00
|
|
|
; The timeout value for network connections in seconds, default to 120 seconds.
|
|
|
|
; Valid uints are {ms, s, m, h}.
|
|
|
|
; connectiontimeout=120s
|
2017-11-12 05:58:06 +03:00
|
|
|
|
2017-12-09 00:16:12 +03:00
|
|
|
; Debug logging level.
|
|
|
|
; Valid levels are {trace, debug, info, warn, error, critical}
|
2020-11-16 13:23:26 +03:00
|
|
|
; You may also specify <global-level>,<subsystem>=<level>,<subsystem2>=<level>,...
|
|
|
|
; to set log level for individual subsystems. Use lncli debuglevel --show to
|
|
|
|
; list available subsystems.
|
|
|
|
; debuglevel=debug,PEER=info
|
2017-11-12 05:58:06 +03:00
|
|
|
|
2017-12-09 00:16:12 +03:00
|
|
|
; Write CPU profile to the specified file.
|
2018-01-30 02:22:22 +03:00
|
|
|
; cpuprofile=
|
2017-11-12 05:58:06 +03:00
|
|
|
|
2017-12-09 00:16:12 +03:00
|
|
|
; Enable HTTP profiling on given port -- NOTE port must be between 1024 and
|
|
|
|
; 65536. The profile can be access at: http://localhost:<PORT>/debug/pprof/.
|
2018-01-30 02:22:22 +03:00
|
|
|
; profile=
|
2017-11-12 05:58:06 +03:00
|
|
|
|
2020-10-08 10:10:57 +03:00
|
|
|
; DEPRECATED: Allows the rpcserver to intentionally disconnect from peers with
|
|
|
|
; open channels. THIS FLAG WILL BE REMOVED IN 0.10.0.
|
|
|
|
; unsafe-disconnect=false
|
|
|
|
|
|
|
|
; Causes a link to replay the adds on its commitment txn after starting up, this
|
|
|
|
; enables testing of the sphinx replay logic.
|
|
|
|
; unsafe-replay=true
|
|
|
|
|
2017-11-12 05:58:06 +03:00
|
|
|
; The maximum number of incoming pending channels permitted per peer.
|
2017-12-09 00:16:12 +03:00
|
|
|
; maxpendingchannels=1
|
2017-11-12 05:58:06 +03:00
|
|
|
|
2020-10-08 10:10:57 +03:00
|
|
|
; The target location of the channel backup file.
|
|
|
|
; backupfilepath=~/.lnd/data/chain/bitcoin/simnet/channel.backup
|
|
|
|
|
2021-03-18 14:40:53 +03:00
|
|
|
; The maximum capacity of the block cache in bytes. Increasing this will result
|
|
|
|
; in more blocks being kept in memory but will increase performance when the
|
|
|
|
; same block is required multiple times.
|
|
|
|
; The example value below is 40 MB (1024 * 1024 * 40)
|
|
|
|
; blockcachesize=41943040
|
|
|
|
|
2021-01-11 11:22:38 +03:00
|
|
|
; Optional URL for external fee estimation. If no URL is specified, the method
|
|
|
|
; for fee estimation will depend on the chosen backend and network. Must be set
|
|
|
|
; for neutrino on mainnet.
|
|
|
|
; feeurl=https://nodes.lightning.computer/fees/v1/btc-fee-estimates.json
|
|
|
|
|
2017-12-09 00:16:12 +03:00
|
|
|
; If true, then automatic network bootstrapping will not be attempted. This
|
|
|
|
; means that your node won't attempt to automatically seek out peers on the
|
|
|
|
; network.
|
2019-12-29 16:12:06 +03:00
|
|
|
; nobootstrap=true
|
2017-11-12 05:58:06 +03:00
|
|
|
|
2020-10-08 10:10:57 +03:00
|
|
|
; If true, NO SEED WILL BE EXPOSED -- EVER, AND THE WALLET WILL BE ENCRYPTED
|
|
|
|
; USING THE DEFAULT PASSPHRASE. THIS FLAG IS ONLY FOR TESTING AND SHOULD NEVER
|
|
|
|
; BE USED ON MAINNET.
|
|
|
|
; noseedbackup=true
|
|
|
|
|
2020-10-24 17:34:52 +03:00
|
|
|
; Removes all transaction history from the on-chain wallet on startup, forcing a
|
|
|
|
; full chain rescan starting at the wallet's birthday. Implements the same
|
|
|
|
; functionality as btcwallet's dropwtxmgr command. Should be set to false after
|
|
|
|
; successful execution to avoid rescanning on every restart of lnd.
|
|
|
|
; reset-wallet-transactions=true
|
|
|
|
|
2019-05-18 18:31:32 +03:00
|
|
|
; The smallest channel size (in satoshis) that we should accept. Incoming
|
|
|
|
; channels smaller than this will be rejected, default value 20000.
|
|
|
|
; minchansize=
|
|
|
|
|
2020-09-15 05:16:32 +03:00
|
|
|
; The largest channel size (in satoshis) that we should accept. Incoming
|
|
|
|
; channels larger than this will be rejected. For non-Wumbo channels this
|
|
|
|
; limit remains 16777215 satoshis by default as specified in BOLT-0002.
|
|
|
|
; For wumbo channels this limit is 1,000,000,000 satoshis (10 BTC).
|
|
|
|
; Set this config option explicitly to restrict your maximum channel size
|
|
|
|
; to better align with your risk tolerance
|
|
|
|
; maxchansize=
|
|
|
|
|
2021-03-02 15:11:10 +03:00
|
|
|
; The target number of blocks in which a cooperative close initiated by a remote
|
|
|
|
; peer should be confirmed. This target is used to estimate the starting fee
|
2021-03-03 11:44:42 +03:00
|
|
|
; rate that will be used during fee negotiation with the peer. This target is
|
|
|
|
; is also used for cooperative closes initiated locally if the --conf_target
|
|
|
|
; for the channel closure is not set.
|
2021-03-02 15:11:10 +03:00
|
|
|
; coop-close-target-confs=10
|
|
|
|
|
2021-04-08 15:29:03 +03:00
|
|
|
; The maximum time that is allowed to pass between receiving a channel state
|
|
|
|
; update and signing the next commitment. Setting this to a longer duration
|
|
|
|
; allows for more efficient channel operations at the cost of latency.
|
|
|
|
; channel-commit-interval=50ms
|
|
|
|
|
2021-04-09 16:10:27 +03:00
|
|
|
; The maximum number of channel state updates that is accumulated before signing
|
|
|
|
; a new commitment.
|
|
|
|
; channel-commit-batch-size=10
|
|
|
|
|
2020-10-08 10:10:57 +03:00
|
|
|
; The default max_htlc applied when opening or accepting channels. This value
|
|
|
|
; limits the number of concurrent HTLCs that the remote party can add to the
|
|
|
|
; commitment. The maximum possible value is 483.
|
|
|
|
; default-remote-max-htlcs=483
|
|
|
|
|
2020-08-21 04:00:15 +03:00
|
|
|
; The duration that a peer connection must be stable before attempting to send a
|
|
|
|
; channel update to reenable or cancel a pending disables of the peer's channels
|
|
|
|
; on the network. (default: 19m0s)
|
|
|
|
; chan-enable-timeout=22m
|
|
|
|
|
|
|
|
; The duration that must elapse after first detecting that an already active
|
|
|
|
; channel is actually inactive and sending channel update disabling it to the
|
|
|
|
; network. The pending disable can be canceled if the peer reconnects and becomes
|
|
|
|
; stable for chan-enable-timeout before the disable update is sent.
|
|
|
|
; (default: 20m0s)
|
|
|
|
; chan-disable-timeout=22m
|
2020-10-08 10:10:58 +03:00
|
|
|
|
2020-08-21 04:00:15 +03:00
|
|
|
; The polling interval between attempts to detect if an active channel has become
|
|
|
|
; inactive due to its peer going offline. (default: 1m0s)
|
|
|
|
; chan-status-sample-interval=2m
|
|
|
|
|
|
|
|
; Disable queries from the height-hint cache to try to recover channels stuck in
|
|
|
|
; the pending close state. Disabling height hint queries may cause longer chain
|
|
|
|
; rescans, resulting in a performance hit. Unset this after channels are unstuck
|
|
|
|
; so you can get better performance again.
|
|
|
|
; height-hint-cache-query-disable=true
|
|
|
|
|
|
|
|
; The polling interval between historical graph sync attempts. Each historical
|
|
|
|
; graph sync attempt ensures we reconcile with the remote peer's graph from the
|
|
|
|
; genesis block. (default: 1h0m0s)
|
|
|
|
; historicalsyncinterval=2h
|
|
|
|
|
|
|
|
; If true, will not reply with historical data that matches the range specified
|
|
|
|
; by a remote peer's gossip_timestamp_filter. Doing so will result in lower
|
|
|
|
; memory and bandwidth requirements.
|
|
|
|
; ignore-historical-gossip-filters=true
|
|
|
|
|
|
|
|
; If true, lnd will not accept channel opening requests with non-zero push
|
|
|
|
; amounts. This should prevent accidental pushes to merchant nodes.
|
|
|
|
; rejectpush=true
|
|
|
|
|
|
|
|
; If true, lnd will not forward any HTLCs that are meant as onward payments. This
|
|
|
|
; option will still allow lnd to send HTLCs and receive HTLCs but lnd won't be
|
|
|
|
; used as a hop.
|
|
|
|
; rejecthtlc=true
|
|
|
|
|
|
|
|
; If true, will apply a randomized staggering between 0s and 30s when
|
|
|
|
; reconnecting to persistent peers on startup. The first 10 reconnections will be
|
|
|
|
; attempted instantly, regardless of the flag's value
|
|
|
|
; stagger-initial-reconnect=true
|
|
|
|
|
|
|
|
; The maximum number of blocks funds could be locked up for when forwarding
|
|
|
|
; payments. (default: 2016)
|
|
|
|
; max-cltv-expiry=2016
|
|
|
|
|
|
|
|
; The maximum percentage of total funds that can be allocated to a channel's
|
|
|
|
; commitment fee. This only applies for the initiator of the channel. Valid
|
|
|
|
; values are within [0.1, 1]. (default: 0.5)
|
|
|
|
; max-channel-fee-allocation=0.9
|
|
|
|
|
2020-12-14 23:07:12 +03:00
|
|
|
; The maximum fee rate in sat/vbyte that will be used for commitments of
|
|
|
|
; channels of the anchors type. Must be large enough to ensure transaction
|
|
|
|
; propagation (default: 10)
|
|
|
|
; max-commit-fee-rate-anchors=5
|
|
|
|
|
2020-08-21 04:00:15 +03:00
|
|
|
; If true, lnd will abort committing a migration if it would otherwise have been
|
|
|
|
; successful. This leaves the database unmodified, and still compatible with the
|
|
|
|
; previously active version of lnd.
|
|
|
|
; dry-run-migration=true
|
|
|
|
|
|
|
|
; If true, option upfront shutdown script will be enabled. If peers that we open
|
|
|
|
; channels with support this feature, we will automatically set the script to
|
|
|
|
; which cooperative closes should be paid out to on channel open. This offers the
|
|
|
|
; partial protection of a channel peer disconnecting from us if cooperative
|
|
|
|
; close is attempted with a different script.
|
|
|
|
; enable-upfront-shutdown=true
|
2020-10-08 10:10:58 +03:00
|
|
|
|
2021-04-10 11:41:18 +03:00
|
|
|
; If true, spontaneous payments through keysend will be accepted.
|
|
|
|
; This is a temporary solution until AMP is implemented which is expected to be soon.
|
|
|
|
; This option will then become deprecated in favor of AMP.
|
2020-08-21 04:00:15 +03:00
|
|
|
; accept-keysend=true
|
|
|
|
|
|
|
|
; If non-zero, keysend payments are accepted but not immediately settled. If the
|
|
|
|
; payment isn't settled manually after the specified time, it is canceled
|
|
|
|
; automatically. [experimental]
|
|
|
|
; keysend-hold-time=true
|
|
|
|
|
2021-01-14 23:21:20 +03:00
|
|
|
; If set, lnd will use anchor channels by default if the remote channel party
|
|
|
|
; supports them. Note that lnd will require 1 UTXO to be reserved for this
|
|
|
|
; channel type if it is enabled.
|
|
|
|
; protocol.anchors=true
|
|
|
|
|
2020-10-08 10:10:57 +03:00
|
|
|
; If true, we'll attempt to garbage collect canceled invoices upon start.
|
|
|
|
; gc-canceled-invoices-on-startup=true
|
|
|
|
|
|
|
|
; If true, we'll delete newly canceled invoices on the fly.
|
|
|
|
; gc-canceled-invoices-on-the-fly=true
|
|
|
|
|
2020-08-21 04:00:15 +03:00
|
|
|
; If true, our node will allow htlc forwards that arrive and depart on the same
|
|
|
|
; channel.
|
|
|
|
; allow-circular-route=true
|
|
|
|
|
|
|
|
; Time in milliseconds between each release of announcements to the network
|
|
|
|
; trickledelay=180000
|
|
|
|
|
|
|
|
; The number of peers that we should receive new graph updates from. This option
|
|
|
|
; can be tuned to save bandwidth for light clients or routing nodes. (default: 3)
|
|
|
|
; numgraphsyncpeers=9
|
|
|
|
|
2018-01-30 02:04:53 +03:00
|
|
|
; The alias your node will use, which can be up to 32 UTF-8 characters in
|
|
|
|
; length.
|
|
|
|
; alias=My Lightning ☇
|
|
|
|
|
|
|
|
; The color of the node in hex format, used to customize node appearance in
|
|
|
|
; intelligence services.
|
|
|
|
; color=#3399FF
|
|
|
|
|
2017-11-12 05:58:06 +03:00
|
|
|
|
|
|
|
[Bitcoin]
|
|
|
|
|
2017-12-09 00:16:12 +03:00
|
|
|
; If the Bitcoin chain should be active. Atm, only a single chain can be
|
|
|
|
; active.
|
2019-12-29 16:12:06 +03:00
|
|
|
bitcoin.active=true
|
2017-11-12 05:58:06 +03:00
|
|
|
|
2020-10-08 10:10:57 +03:00
|
|
|
; The directory to store the chain's data within.
|
|
|
|
; bitcoin.chaindir=~/.lnd/data/chain/bitcoin
|
|
|
|
|
|
|
|
; Use Bitcoin's main network.
|
|
|
|
; bitcoin.mainnet=true
|
|
|
|
|
2017-12-09 00:16:12 +03:00
|
|
|
; Use Bitcoin's test network.
|
2019-12-29 16:12:06 +03:00
|
|
|
; bitcoin.testnet=true
|
2018-05-23 16:41:59 +03:00
|
|
|
;
|
2017-12-09 00:16:12 +03:00
|
|
|
; Use Bitcoin's simulation test network
|
2019-12-29 16:12:06 +03:00
|
|
|
bitcoin.simnet=true
|
2017-11-12 05:58:06 +03:00
|
|
|
|
2017-12-09 00:16:12 +03:00
|
|
|
; Use Bitcoin's regression test network
|
|
|
|
; bitcoin.regtest=false
|
2017-11-12 05:58:06 +03:00
|
|
|
|
2018-01-13 08:34:46 +03:00
|
|
|
; Use the btcd back-end
|
|
|
|
bitcoin.node=btcd
|
2017-11-12 05:58:06 +03:00
|
|
|
|
2018-01-13 08:34:46 +03:00
|
|
|
; Use the bitcoind back-end
|
2018-05-23 16:41:59 +03:00
|
|
|
; bitcoin.node=bitcoind
|
2018-01-13 08:34:46 +03:00
|
|
|
|
|
|
|
; Use the neutrino (light client) back-end
|
|
|
|
; bitcoin.node=neutrino
|
2017-11-12 05:58:06 +03:00
|
|
|
|
2018-03-19 02:09:22 +03:00
|
|
|
; The default number of confirmations a channel must have before it's considered
|
|
|
|
; open. We'll require any incoming channel requests to wait this many
|
|
|
|
; confirmations before we consider the channel active.
|
|
|
|
; bitcoin.defaultchanconfs=3
|
|
|
|
|
2020-10-08 10:10:57 +03:00
|
|
|
; The default number of blocks we will require our channel counterparty to wait
|
|
|
|
; before accessing its funds in case of unilateral close. If this is not set, we
|
|
|
|
; will scale the value according to the channel size.
|
|
|
|
; bitcoin.defaultremotedelay=144
|
|
|
|
|
2020-10-29 12:29:53 +03:00
|
|
|
; The maximum number of blocks we will limit the wait that our own funds are
|
|
|
|
; encumbered by in the case when our node unilaterally closes. If a remote peer
|
|
|
|
; proposes a channel with a delay above this amount, lnd will reject the
|
|
|
|
; channel.
|
|
|
|
; bitcoin.maxlocaldelay=2016
|
|
|
|
|
2020-10-08 10:10:57 +03:00
|
|
|
; The smallest HTLC we are willing to accept on our channels, in millisatoshi.
|
|
|
|
; bitcoin.minhtlc=1
|
|
|
|
|
|
|
|
; The smallest HTLC we are willing to send out on our channels, in millisatoshi.
|
|
|
|
; bitcoin.minhtlcout=1000
|
|
|
|
|
|
|
|
; The base fee in millisatoshi we will charge for forwarding payments on our
|
|
|
|
; channels.
|
|
|
|
; bitcoin.basefee=1000
|
|
|
|
|
|
|
|
; The fee rate used when forwarding payments on our channels. The total fee
|
|
|
|
; charged is basefee + (amount * feerate / 1000000), where amount is the
|
|
|
|
; forwarded amount.
|
|
|
|
; bitcoin.feerate=1
|
|
|
|
|
|
|
|
; The CLTV delta we will subtract from a forwarded HTLC's timelock value.
|
|
|
|
; bitcoin.timelockdelta=40
|
|
|
|
|
2020-11-03 23:19:15 +03:00
|
|
|
; The seed DNS server(s) to use for initial peer discovery. Must be specified as
|
|
|
|
; a '<primary_dns>[,<soa_primary_dns>]' tuple where the SOA address is needed
|
|
|
|
; for DNS resolution through Tor but is optional for clearnet users. Multiple
|
|
|
|
; tuples can be specified, will overwrite the default seed servers.
|
|
|
|
; The default seed servers are:
|
|
|
|
; mainnet:
|
|
|
|
; bitcoin.dnsseed=nodes.lightning.directory,soa.nodes.lightning.directory
|
|
|
|
; bitcoin.dnsseed=lseed.bitcoinstats.com
|
|
|
|
; testnet:
|
|
|
|
; bitcoin.dnsseed=test.nodes.lightning.directory,soa.nodes.lightning.directory
|
|
|
|
;
|
|
|
|
; Example for custom DNS servers:
|
|
|
|
; bitcoin.dnsseed=seed1.test.lightning
|
|
|
|
; bitcoin.dnsseed=seed2.test.lightning,soa.seed2.test.lightning
|
|
|
|
|
2020-10-08 10:10:57 +03:00
|
|
|
; Used to help identify ourselves to other bitcoin peers (default: neutrino).
|
|
|
|
; neutrino.useragentname=neutrino
|
|
|
|
|
|
|
|
; Used to help identify ourselves to other bitcoin peers (default: 0.11.0-beta).
|
|
|
|
; neutrino.useragentversion=0.11.0-beta
|
2017-11-12 05:58:06 +03:00
|
|
|
|
2021-03-29 11:01:09 +03:00
|
|
|
; Validate every channel in the graph during sync by downloading the containing
|
|
|
|
; block. This is the inverse of routing.assumechanvalid, meaning that for
|
|
|
|
; Neutrino the validation is turned off by default for massively increased graph
|
|
|
|
; sync performance. This speedup comes at the risk of using an unvalidated view
|
|
|
|
; of the network for routing. Overwrites the value of routing.assumechanvalid if
|
|
|
|
; Neutrino is used. (default: false)
|
|
|
|
; neutrino.validatechannels=false
|
|
|
|
|
2021-03-30 16:18:51 +03:00
|
|
|
; DEPRECATED: This is now turned on by default for Neutrino (use
|
|
|
|
; neutrino.validatechannels=true to turn off) and shouldn't be used for any
|
|
|
|
; other backend!
|
2020-10-21 12:22:33 +03:00
|
|
|
; --routing.assumechanvalid=true
|
|
|
|
|
2021-04-03 01:02:08 +03:00
|
|
|
; If set to true, then we'll prune a channel if only a single edge is seen as
|
|
|
|
; being stale. This results in a more compact channel graph, and also is helpful
|
|
|
|
; for neutrino nodes as it means they'll only maintain edges where both nodes are
|
|
|
|
; seen as being live from it's PoV.
|
|
|
|
; --routing.strictgraphpruning=true
|
|
|
|
|
2018-01-13 08:34:46 +03:00
|
|
|
[Btcd]
|
|
|
|
|
2020-10-08 10:10:57 +03:00
|
|
|
; The base directory that contains the node's data, logs, configuration file,
|
|
|
|
; etc.
|
|
|
|
; btcd.dir=~/.btcd
|
|
|
|
|
2018-01-13 08:34:46 +03:00
|
|
|
; The host that your local btcd daemon is listening on. By default, this
|
|
|
|
; setting is assumed to be localhost with the default port for the current
|
|
|
|
; network.
|
|
|
|
; btcd.rpchost=localhost
|
2018-05-23 16:41:59 +03:00
|
|
|
|
2018-01-13 08:34:46 +03:00
|
|
|
; Username for RPC connections to btcd. By default, lnd will attempt to
|
|
|
|
; automatically obtain the credentials, so this likely won't need to be set
|
|
|
|
; (other than for simnet mode).
|
|
|
|
; btcd.rpcuser=kek
|
2017-11-12 05:58:06 +03:00
|
|
|
|
2018-01-13 08:34:46 +03:00
|
|
|
; Password for RPC connections to btcd. By default, lnd will attempt to
|
|
|
|
; automatically obtain the credentials, so this likely won't need to be set
|
|
|
|
; (other than for simnet mode).
|
|
|
|
; btcd.rpcpass=kek
|
2017-11-12 05:58:06 +03:00
|
|
|
|
2017-12-09 00:16:12 +03:00
|
|
|
; File containing the daemon's certificate file. This only needs to be set if
|
|
|
|
; the node isn't on the same host as lnd.
|
2018-01-13 08:34:46 +03:00
|
|
|
; btcd.rpccert=~/.btcd/rpc.cert
|
2017-11-12 05:58:06 +03:00
|
|
|
|
|
|
|
; The raw bytes of the daemon's PEM-encoded certificate chain which will be used
|
2018-01-13 08:34:46 +03:00
|
|
|
; to authenticate the RPC connection. This only needs to be set if the btcd
|
2017-12-09 00:16:12 +03:00
|
|
|
; node is on a remote host.
|
2018-05-23 16:41:59 +03:00
|
|
|
; btcd.rawrpccert=
|
2018-01-13 08:34:46 +03:00
|
|
|
|
|
|
|
|
|
|
|
[Bitcoind]
|
|
|
|
|
2020-10-08 10:10:57 +03:00
|
|
|
; The base directory that contains the node's data, logs, configuration file,
|
|
|
|
; etc.
|
|
|
|
; bitcoind.dir=~/.bitcoin
|
|
|
|
|
2018-01-13 08:34:46 +03:00
|
|
|
; The host that your local bitcoind daemon is listening on. By default, this
|
|
|
|
; setting is assumed to be localhost with the default port for the current
|
|
|
|
; network.
|
|
|
|
; bitcoind.rpchost=localhost
|
2018-05-23 16:41:59 +03:00
|
|
|
|
2018-01-13 08:34:46 +03:00
|
|
|
; Username for RPC connections to bitcoind. By default, lnd will attempt to
|
|
|
|
; automatically obtain the credentials, so this likely won't need to be set
|
|
|
|
; (other than for a remote bitcoind instance).
|
|
|
|
; bitcoind.rpcuser=kek
|
|
|
|
|
|
|
|
; Password for RPC connections to bitcoind. By default, lnd will attempt to
|
|
|
|
; automatically obtain the credentials, so this likely won't need to be set
|
|
|
|
; (other than for a remote bitcoind instance).
|
|
|
|
; bitcoind.rpcpass=kek
|
|
|
|
|
2018-07-17 03:23:21 +03:00
|
|
|
; ZMQ socket which sends rawblock and rawtx notifications from bitcoind. By
|
|
|
|
; default, lnd will attempt to automatically obtain this information, so this
|
|
|
|
; likely won't need to be set (other than for a remote bitcoind instance).
|
2018-08-10 09:50:36 +03:00
|
|
|
; bitcoind.zmqpubrawblock=tcp://127.0.0.1:28332
|
|
|
|
; bitcoind.zmqpubrawtx=tcp://127.0.0.1:28333
|
2018-01-13 08:34:46 +03:00
|
|
|
|
2020-03-13 11:41:08 +03:00
|
|
|
; Fee estimate mode for bitcoind. It must be either "ECONOMICAL" or "CONSERVATIVE".
|
|
|
|
; If unset, the default value is "CONSERVATIVE".
|
|
|
|
; bitcoind.estimatemode=CONSERVATIVE
|
2018-01-13 08:34:46 +03:00
|
|
|
|
2021-03-27 01:49:24 +03:00
|
|
|
; The maximum number of peers lnd will choose from the backend node to retrieve
|
|
|
|
; pruned blocks from. This only applies to pruned nodes.
|
|
|
|
; bitcoind.pruned-node-max-peers=4
|
|
|
|
|
2018-01-13 08:34:46 +03:00
|
|
|
[neutrino]
|
|
|
|
|
|
|
|
; Connect only to the specified peers at startup. This creates a persistent
|
|
|
|
; connection to a target peer. This is recommended as there aren't many
|
|
|
|
; neutrino compliant full nodes on the test network yet.
|
2018-01-30 02:22:22 +03:00
|
|
|
; neutrino.connect=
|
2018-01-13 08:34:46 +03:00
|
|
|
|
2020-10-08 10:10:57 +03:00
|
|
|
; Max number of inbound and outbound peers.
|
|
|
|
;
|
|
|
|
; NOTE: This value is currently unused.
|
|
|
|
; neutrino.maxpeers=
|
|
|
|
|
2018-01-13 08:34:46 +03:00
|
|
|
; Add a peer to connect with at startup.
|
2018-01-30 02:22:22 +03:00
|
|
|
; neutrino.addpeer=
|
2018-01-13 08:34:46 +03:00
|
|
|
|
2020-10-08 10:10:57 +03:00
|
|
|
; How long to ban misbehaving peers. Valid time units are {s, m, h}. Minimum 1
|
|
|
|
; second.
|
|
|
|
;
|
|
|
|
; NOTE: This value is currently unused.
|
|
|
|
; neutrino.banduration=
|
|
|
|
|
|
|
|
; Maximum allowed ban score before disconnecting and banning misbehaving peers.
|
|
|
|
;
|
|
|
|
; NOTE: This value is currently unused.
|
|
|
|
; neutrino.banthreshold=
|
|
|
|
|
2021-01-11 11:22:38 +03:00
|
|
|
; DEPRECATED: Use top level 'feeurl' option. Optional URL for fee estimation. If
|
|
|
|
; a URL is not specified, static fees will be used for estimation.
|
2018-09-10 03:34:10 +03:00
|
|
|
; neutrino.feeurl=
|
|
|
|
|
2020-10-08 10:10:57 +03:00
|
|
|
; Optional filter header in height:hash format to assert the state of neutrino's
|
|
|
|
; filter header chain on startup. If the assertion does not hold, then the
|
|
|
|
; filter header chain will be re-synced from the genesis block.
|
|
|
|
; neutrino.assertfilterheader=
|
2018-01-13 08:34:46 +03:00
|
|
|
|
|
|
|
[Litecoin]
|
|
|
|
|
|
|
|
; If the Litecoin chain should be active. Atm, only a single chain can be
|
|
|
|
; active.
|
2019-12-29 16:12:06 +03:00
|
|
|
; litecoin.active=true
|
2017-11-12 05:58:06 +03:00
|
|
|
|
2020-10-08 10:10:57 +03:00
|
|
|
; The directory to store the chain's data within.
|
|
|
|
; litecoin.chaindir=~/.lnd/data/chain/litecoin
|
|
|
|
|
|
|
|
; Use Litecoin's main network.
|
|
|
|
; litecoin.mainnet=true
|
|
|
|
|
2018-03-21 22:12:46 +03:00
|
|
|
; Use Litecoin's test network.
|
2019-12-29 16:12:06 +03:00
|
|
|
; litecoin.testnet=true
|
2020-10-08 10:10:57 +03:00
|
|
|
;
|
|
|
|
; Use Litecoin's simulation test network
|
|
|
|
; litecoin.simnet=true
|
|
|
|
|
|
|
|
; Use Litecoin's regression test network
|
|
|
|
; litecoin.regtest=false
|
2017-11-12 05:58:06 +03:00
|
|
|
|
2020-10-08 10:10:57 +03:00
|
|
|
; Use the ltcd back-end.
|
2018-03-21 22:12:46 +03:00
|
|
|
litecoin.node=ltcd
|
2017-11-12 05:58:06 +03:00
|
|
|
|
2020-10-08 10:10:57 +03:00
|
|
|
; Use the litecoind back-end.
|
2018-05-23 16:41:59 +03:00
|
|
|
; litecoin.node=litecoind
|
2017-11-12 05:58:06 +03:00
|
|
|
|
2020-10-08 10:10:57 +03:00
|
|
|
; The default number of confirmations a channel must have before it's considered
|
|
|
|
; open. We'll require any incoming channel requests to wait this many
|
|
|
|
; confirmations before we consider the channel active.
|
|
|
|
; litecoin.defaultchanconfs=3
|
|
|
|
|
|
|
|
; The default number of blocks we will require our channel counterparty to wait
|
|
|
|
; before accessing its funds in case of unilateral close. If this is not set, we
|
|
|
|
; will scale the value according to the channel size.
|
|
|
|
; litecoin.defaultremotedelay=144
|
|
|
|
|
2020-10-29 12:29:53 +03:00
|
|
|
; The maximum number of blocks we will limit the wait that our own funds are
|
|
|
|
; encumbered by in the case when our node unilaterally closes. If a remote peer
|
|
|
|
; proposes a channel with a delay above this amount, lnd will reject the
|
|
|
|
; channel.
|
|
|
|
; litecoin.maxlocaldelay=2016
|
|
|
|
|
2020-10-08 10:10:57 +03:00
|
|
|
; The smallest HTLC we are willing to accept on our channels, in millisatoshi.
|
|
|
|
; litecoin.minhtlc=1
|
|
|
|
|
|
|
|
; The smallest HTLC we are willing to send out on our channels, in millisatoshi.
|
|
|
|
; litecoin.minhtlcout=1000
|
|
|
|
|
|
|
|
; The base fee in millisatoshi we will charge for forwarding payments on our
|
|
|
|
; channels.
|
|
|
|
; litecoin.basefee=1000
|
|
|
|
|
|
|
|
; The fee rate used when forwarding payments on our channels. The total fee
|
|
|
|
; charged is basefee + (amount * feerate / 1000000), where amount is the
|
|
|
|
; forwarded amount.
|
|
|
|
; litecoin.feerate=1
|
|
|
|
|
|
|
|
; The CLTV delta we will subtract from a forwarded HTLC's timelock value.
|
|
|
|
; litecoin.timelockdelta=576
|
2017-11-12 05:58:06 +03:00
|
|
|
|
2020-11-03 23:19:15 +03:00
|
|
|
; The seed DNS server(s) to use for initial peer discovery. Must be specified as
|
|
|
|
; a '<primary_dns>[,<soa_primary_dns>]' tuple where the SOA address is needed
|
|
|
|
; for DNS resolution through Tor but is optional for clearnet users. Multiple
|
|
|
|
; tuples can be specified, will overwrite the default seed servers.
|
|
|
|
; The default seed servers are:
|
|
|
|
; mainnet:
|
|
|
|
; litecoin.dnsseed=ltc.nodes.lightning.directory,soa.nodes.lightning.directory
|
|
|
|
;
|
|
|
|
; Example for custom DNS servers:
|
|
|
|
; litecoin.dnsseed=seed1.test-ltc.lightning
|
|
|
|
; litecoin.dnsseed=seed2.test-ltc.lightning,soa.seed2.test-ltc.lightning
|
|
|
|
|
2018-01-13 08:34:46 +03:00
|
|
|
[Ltcd]
|
2017-11-12 05:58:06 +03:00
|
|
|
|
2020-10-08 10:10:57 +03:00
|
|
|
; The base directory that contains the node's data, logs, configuration file,
|
|
|
|
; etc.
|
|
|
|
; ltcd.dir=~/.ltcd
|
|
|
|
|
2018-01-13 08:34:46 +03:00
|
|
|
; The host that your local ltcd daemon is listening on. By default, this
|
|
|
|
; setting is assumed to be localhost with the default port for the current
|
|
|
|
; network.
|
|
|
|
; ltcd.rpchost=localhost
|
2018-05-23 16:41:59 +03:00
|
|
|
|
2018-01-13 08:34:46 +03:00
|
|
|
; Username for RPC connections to ltcd. By default, lnd will attempt to
|
|
|
|
; automatically obtain the credentials, so this likely won't need to be set
|
|
|
|
; (other than for simnet mode).
|
|
|
|
; ltcd.rpcuser=kek
|
|
|
|
|
|
|
|
; Password for RPC connections to ltcd. By default, lnd will attempt to
|
|
|
|
; automatically obtain the credentials, so this likely won't need to be set
|
|
|
|
; (other than for simnet mode).
|
|
|
|
; ltcd.rpcpass=kek
|
|
|
|
|
|
|
|
; File containing the daemon's certificate file. This only needs to be set if
|
|
|
|
; the node isn't on the same host as lnd.
|
|
|
|
; ltcd.rpccert=~/.ltcd/rpc.cert
|
|
|
|
|
|
|
|
; The raw bytes of the daemon's PEM-encoded certificate chain which will be used
|
|
|
|
; to authenticate the RPC connection. This only needs to be set if the ltcd
|
|
|
|
; node is on a remote host.
|
2018-05-23 16:41:59 +03:00
|
|
|
; ltcd.rawrpccert=
|
2017-11-12 05:58:06 +03:00
|
|
|
|
|
|
|
|
2018-03-21 22:12:46 +03:00
|
|
|
[Litecoind]
|
|
|
|
|
2020-10-08 10:10:57 +03:00
|
|
|
; The base directory that contains the node's data, logs, configuration file,
|
|
|
|
; etc.
|
|
|
|
; litecoind.dir=~/.litecoin
|
|
|
|
|
2018-03-21 22:12:46 +03:00
|
|
|
; The host that your local litecoind daemon is listening on. By default, this
|
|
|
|
; setting is assumed to be localhost with the default port for the current
|
|
|
|
; network.
|
|
|
|
; litecoind.rpchost=localhost
|
2018-05-23 16:41:59 +03:00
|
|
|
|
2018-03-21 22:12:46 +03:00
|
|
|
; Username for RPC connections to litecoind. By default, lnd will attempt to
|
|
|
|
; automatically obtain the credentials, so this likely won't need to be set
|
|
|
|
; (other than for a remote litecoind instance).
|
|
|
|
; litecoind.rpcuser=kek
|
|
|
|
|
|
|
|
; Password for RPC connections to litecoind. By default, lnd will attempt to
|
|
|
|
; automatically obtain the credentials, so this likely won't need to be set
|
|
|
|
; (other than for a remote litecoind instance).
|
|
|
|
; litecoind.rpcpass=kek
|
|
|
|
|
2018-07-17 03:23:21 +03:00
|
|
|
; ZMQ socket which sends rawblock and rawtx notifications from litecoind. By
|
|
|
|
; default, lnd will attempt to automatically obtain this information, so this
|
|
|
|
; likely won't need to be set (other than for a remote litecoind instance).
|
2018-08-10 09:50:36 +03:00
|
|
|
; litecoind.zmqpubrawblock=tcp://127.0.0.1:28332
|
|
|
|
; litecoind.zmqpubrawtx=tcp://127.0.0.1:28333
|
2018-03-21 22:12:46 +03:00
|
|
|
|
2020-03-13 11:41:08 +03:00
|
|
|
; Fee estimate mode for litecoind. It must be either "ECONOMICAL" or "CONSERVATIVE".
|
|
|
|
; If unset, the default value is "CONSERVATIVE".
|
|
|
|
; litecoind.estimatemode=CONSERVATIVE
|
2018-03-21 22:12:46 +03:00
|
|
|
|
2021-03-27 01:49:24 +03:00
|
|
|
; The maximum number of peers lnd will choose from the backend node to retrieve
|
|
|
|
; pruned blocks from. This only applies to pruned nodes.
|
|
|
|
; litecoind.pruned-node-max-peers=4
|
|
|
|
|
2017-11-12 05:58:06 +03:00
|
|
|
[autopilot]
|
|
|
|
|
2017-12-09 00:16:12 +03:00
|
|
|
; If the autopilot agent should be active or not. The autopilot agent will
|
|
|
|
; attempt to automatically open up channels to put your node in an advantageous
|
|
|
|
; position within the network graph.
|
2019-12-29 16:12:06 +03:00
|
|
|
; autopilot.active=true
|
2017-11-12 05:58:06 +03:00
|
|
|
|
2017-12-09 00:16:12 +03:00
|
|
|
; The maximum number of channels that should be created.
|
|
|
|
; autopilot.maxchannels=5
|
2017-11-12 05:58:06 +03:00
|
|
|
|
2018-01-29 02:05:33 +03:00
|
|
|
; The fraction of total funds that should be committed to automatic channel
|
|
|
|
; establishment. For example 0.6 means that 60% of the total funds available
|
|
|
|
; within the wallet should be used to automatically establish channels. The total
|
|
|
|
; amount of attempted channels will still respect the maxchannels param.
|
2017-12-09 00:16:12 +03:00
|
|
|
; autopilot.allocation=0.6
|
2018-02-06 05:34:09 +03:00
|
|
|
|
2020-08-21 04:00:15 +03:00
|
|
|
; Heuristic to activate, and the weight to give it during scoring. (default:
|
2020-10-03 06:13:54 +03:00
|
|
|
; top_centrality:1)
|
|
|
|
; autopilot.heuristic=preferential:1
|
2020-08-21 04:00:15 +03:00
|
|
|
|
|
|
|
; The smallest channel that the autopilot agent should create (default: 20000)
|
|
|
|
; autopilot.minchansize=20000
|
|
|
|
|
|
|
|
; The largest channel that the autopilot agent should create (default: 16777215)
|
|
|
|
; autopilot.maxchansize=20000
|
|
|
|
|
|
|
|
; Whether the channels created by the autopilot agent should be private or not.
|
|
|
|
; Private channels won't be announced to the network.
|
|
|
|
; autopilot.private=true
|
|
|
|
|
|
|
|
; The minimum number of confirmations each of your inputs in funding transactions
|
|
|
|
; created by the autopilot agent must have. (default: 1)
|
|
|
|
; autopilot.minconfs=2
|
|
|
|
|
|
|
|
; The confirmation target (in blocks) for channels opened by autopilot. (default:
|
|
|
|
; 3)
|
|
|
|
; autopilot.conftarget=2
|
|
|
|
|
2018-02-06 05:34:09 +03:00
|
|
|
[tor]
|
2020-08-21 04:00:15 +03:00
|
|
|
; Allow outbound and inbound connections to be routed through Tor
|
2020-10-08 10:10:58 +03:00
|
|
|
; tor.active=true
|
2020-08-21 04:00:15 +03:00
|
|
|
|
2018-02-06 05:34:09 +03:00
|
|
|
; The port that Tor's exposed SOCKS5 proxy is listening on. Using Tor allows
|
|
|
|
; outbound-only connections (listening will be disabled) -- NOTE port must be
|
2018-05-23 16:41:59 +03:00
|
|
|
; between 1024 and 65535
|
2018-02-06 05:34:09 +03:00
|
|
|
; tor.socks=9050
|
|
|
|
|
|
|
|
; The DNS server as IP:PORT that Tor will use for SRV queries - NOTE must have
|
2018-04-18 08:22:55 +03:00
|
|
|
; TCP resolution enabled. The current active DNS server for Testnet listening is
|
2018-02-06 05:34:09 +03:00
|
|
|
; nodes.lightning.directory
|
|
|
|
; tor.dns=nodes.lightning.directory
|
|
|
|
|
|
|
|
; Enable Tor stream isolation by randomizing user credentials for each
|
|
|
|
; connection. With this mode active, each connection will use a new circuit.
|
|
|
|
; This means that multiple applications (other than lnd) using Tor won't be mixed
|
|
|
|
; in with lnd's traffic.
|
2019-12-29 16:12:06 +03:00
|
|
|
; tor.streamisolation=true
|
2019-06-29 02:10:56 +03:00
|
|
|
|
2020-08-21 04:00:15 +03:00
|
|
|
; The host:port that Tor is listening on for Tor control connections (default:
|
|
|
|
; localhost:9051)
|
2020-10-08 10:10:58 +03:00
|
|
|
; tor.control=localhost:9091
|
2020-08-21 04:00:15 +03:00
|
|
|
|
|
|
|
; IP address that Tor should use as the target of the hidden service
|
2020-10-08 10:10:58 +03:00
|
|
|
; tor.targetipaddress=
|
|
|
|
|
2020-08-21 04:00:15 +03:00
|
|
|
; The password used to arrive at the HashedControlPassword for the control port.
|
|
|
|
; If provided, the HASHEDPASSWORD authentication method will be used instead of
|
|
|
|
; the SAFECOOKIE one.
|
2020-10-08 10:10:58 +03:00
|
|
|
; tor.password=plsdonthackme
|
|
|
|
|
2020-08-21 04:00:15 +03:00
|
|
|
; Automatically set up a v2 onion service to listen for inbound connections
|
|
|
|
; tor.v2=true
|
2020-10-08 10:10:58 +03:00
|
|
|
|
2020-08-21 04:00:15 +03:00
|
|
|
; Automatically set up a v3 onion service to listen for inbound connections
|
|
|
|
; tor.v3=true
|
2020-10-08 10:10:58 +03:00
|
|
|
|
2020-08-21 04:00:15 +03:00
|
|
|
; The path to the private key of the onion service being created
|
2020-10-08 10:10:58 +03:00
|
|
|
; tor.privatekeypath=/path/to/torkey
|
|
|
|
|
2020-08-21 04:00:15 +03:00
|
|
|
;The path to the private key of the watchtower onion service being created
|
2020-10-08 10:10:58 +03:00
|
|
|
; tor.watchtowerkeypath=/other/path/
|
2020-08-21 04:00:15 +03:00
|
|
|
|
2019-06-29 02:10:56 +03:00
|
|
|
[watchtower]
|
|
|
|
; Enable integrated watchtower listening on :9911 by default.
|
2019-12-29 16:12:06 +03:00
|
|
|
; watchtower.active=true
|
2019-06-29 02:10:56 +03:00
|
|
|
|
|
|
|
; Specify the interfaces to listen on for watchtower client connections. One
|
|
|
|
; listen address per line. If no port is specified the default port of 9911 will
|
|
|
|
; be added implicitly.
|
|
|
|
; All ipv4 on port 9911:
|
|
|
|
; watchtower.listen=0.0.0.0:9911
|
|
|
|
; On all ipv4 interfaces on port 9911 and ipv6 localhost port 9912:
|
|
|
|
; watchtower.listen=0.0.0.0:9911
|
|
|
|
; watchtower.listen=[::1]:9912
|
|
|
|
|
|
|
|
; Configure the external IP address of your watchtower. Setting this field does
|
|
|
|
; not have any behavioral changes to the tower or enable any sort of discovery,
|
|
|
|
; however it will make the full URI (pubkey@host:port) available via
|
|
|
|
; WatchtowerRPC.GetInfo and `lncli tower info`.
|
|
|
|
; watchtower.externalip=1.2.3.4
|
|
|
|
|
|
|
|
; Configure the default watchtower data directory. The default directory is
|
|
|
|
; data/watchtower relative to the chosen lnddir. This can be useful if one needs
|
|
|
|
; to move the database to a separate volume with more storage. In the example
|
|
|
|
; below, the database will be stored at:
|
|
|
|
; /path/to/towerdir/bitcoin/<network>/watchtower.db.
|
|
|
|
; watchtower.towerdir=/path/to/towerdir
|
|
|
|
|
|
|
|
; Duration the watchtower server will wait for messages to be received before
|
|
|
|
; hanging up on client connections.
|
|
|
|
; watchtower.readtimeout=15s
|
|
|
|
|
|
|
|
; Duration the watchtower server will wait for messages to be written before
|
|
|
|
; hanging up on client connections
|
|
|
|
; watchtower.writetimeout=15s
|
|
|
|
|
|
|
|
[wtclient]
|
2020-03-05 22:22:02 +03:00
|
|
|
; Activate Watchtower Client. To get more information or configure watchtowers
|
2020-03-06 00:08:38 +03:00
|
|
|
; run `lncli wtclient -h`.
|
2020-03-05 22:22:02 +03:00
|
|
|
; wtclient.active=true
|
2019-06-29 02:10:56 +03:00
|
|
|
|
|
|
|
; Specify the fee rate with which justice transactions will be signed. This fee
|
|
|
|
; rate should be chosen as a maximum fee rate one is willing to pay in order to
|
|
|
|
; sweep funds if a breach occurs while being offline. The fee rate should be
|
|
|
|
; specified in sat/byte, the default is 10 sat/byte.
|
|
|
|
; wtclient.sweep-fee-rate=10
|
2020-08-24 09:54:38 +03:00
|
|
|
|
2020-10-08 10:10:57 +03:00
|
|
|
; (Deprecated) Specifies the URIs of private watchtowers to use in backing up
|
|
|
|
; revoked states. URIs must be of the form <pubkey>@<addr>. Only 1 URI is
|
|
|
|
; supported at this time, if none are provided the tower will not be enabled.
|
|
|
|
; wtclient.private-tower-uris=
|
|
|
|
|
2020-08-24 09:54:38 +03:00
|
|
|
[healthcheck]
|
|
|
|
; The number of times we should attempt to query our chain backend before
|
|
|
|
; gracefully shutting down. Set this value to 0 to disable this health check.
|
|
|
|
; healthcheck.chainbackend.attempts=3
|
|
|
|
|
|
|
|
; The amount of time we allow a call to our chain backend to take before we fail
|
|
|
|
; the attempt. This value must be >= 1s.
|
|
|
|
; healthcheck.chainbackend.timeout=10s
|
|
|
|
|
|
|
|
; The amount of time we should backoff between failed attempts to query chain
|
|
|
|
; backend. This value must be >= 1s.
|
|
|
|
; healthcheck.chainbackend.backoff=30s
|
|
|
|
|
|
|
|
; The amount of time we should wait between chain backend health checks. This
|
|
|
|
; value must be >= 1m.
|
|
|
|
; healthcheck.chainbackend.interval=1m
|
|
|
|
|
2020-08-24 09:54:39 +03:00
|
|
|
; The minimum ratio of free disk space to total capacity that we require.
|
|
|
|
; healthcheck.diskspace.diskrequired=0.1
|
|
|
|
|
|
|
|
; The number of times we should attempt to query our available disk space before
|
|
|
|
; gracefully shutting down. Set this value to 0 to disable this health check.
|
|
|
|
; healthcheck.diskspace.attempts=2
|
|
|
|
|
|
|
|
; The amount of time we allow a query for our available disk space to take
|
|
|
|
; before we fail the attempt. This value must be >= 1s.
|
|
|
|
; healthcheck.diskspace.timeout=5s
|
|
|
|
|
|
|
|
; The amount of time we should backoff between failed attempts to query
|
|
|
|
; available disk space. This value must be >= 1s.
|
|
|
|
; healthcheck.diskspace.backoff=1m
|
|
|
|
|
|
|
|
; The amount of time we should wait between disk space health checks. This
|
|
|
|
; value must be >= 1m.
|
|
|
|
; healthcheck.diskspace.interval=6h
|
2020-08-21 04:00:15 +03:00
|
|
|
|
2020-12-02 05:34:19 +03:00
|
|
|
; The number of times we should attempt to check for certificate expiration before
|
|
|
|
; gracefully shutting down. Set this value to 0 to disable this health check.
|
|
|
|
; healthcheck.tls.attempts=2
|
|
|
|
|
|
|
|
; The amount of time we allow a query for certificate expiration to take
|
|
|
|
; before we fail the attempt. This value must be >= 1s.
|
|
|
|
; healthcheck.tls.timeout=5s
|
|
|
|
|
|
|
|
; The amount of time we should backoff between failed attempts to query
|
|
|
|
; certificate expiration. This value must be >= 1s.
|
|
|
|
; healthcheck.tls.backoff=1m
|
|
|
|
|
|
|
|
; The amount of time we should wait between certificate expiration health checks.
|
|
|
|
; This value must be >= 1m.
|
|
|
|
; healthcheck.tls.interval=1m
|
|
|
|
|
2020-10-08 10:10:57 +03:00
|
|
|
[signrpc]
|
|
|
|
|
|
|
|
; Path to the signer macaroon.
|
|
|
|
; signrpc.signermacaroonpath=~/.lnd/data/chain/bitcoin/simnet/signer.macaroon
|
|
|
|
|
|
|
|
[walletrpc]
|
|
|
|
|
|
|
|
; Path to the wallet kit macaroon.
|
|
|
|
; walletrpc.walletkitmacaroonpath=~/.lnd/data/chain/bitcoin/simnet/walletkit.macaroon
|
|
|
|
|
|
|
|
[chainrpc]
|
|
|
|
|
|
|
|
; Path to the chain notifier macaroon.
|
|
|
|
; chainrpc.notifiermacaroonpath=~/.lnd/data/chain/bitcoin/simnet/chainnotifier.macaroon
|
|
|
|
|
2020-08-21 04:00:15 +03:00
|
|
|
[routerrpc]
|
|
|
|
; Minimum required route success probability to attempt the payment (default:
|
|
|
|
; 0.01)
|
2020-10-08 10:10:58 +03:00
|
|
|
; routerrpc.minrtprob=1
|
2020-08-21 04:00:15 +03:00
|
|
|
|
|
|
|
; Assumed success probability of a hop in a route when no other information is
|
|
|
|
; available. (default: 0.6)
|
2020-10-08 10:10:58 +03:00
|
|
|
; routerrpc.apriorihopprob=0.2
|
2020-08-21 04:00:15 +03:00
|
|
|
|
|
|
|
; Weight of the a priori probability in success probability estimation. Valid
|
|
|
|
; values are in [0, 1]. (default: 0.5)
|
2020-10-08 10:10:58 +03:00
|
|
|
; routerrpc.aprioriweight=0.3
|
2020-08-21 04:00:15 +03:00
|
|
|
|
|
|
|
; Defines the duration after which a penalized node or channel is back at 50%
|
|
|
|
; probability (default: 1h0m0s)
|
2020-10-08 10:10:58 +03:00
|
|
|
; routerrpc.penaltyhalflife=2h
|
2020-08-21 04:00:15 +03:00
|
|
|
|
2020-09-08 14:02:33 +03:00
|
|
|
; The (virtual) fixed cost in sats of a failed payment attempt (default: 100)
|
2020-10-08 10:10:58 +03:00
|
|
|
; routerrpc.attemptcost=90
|
2020-09-08 14:02:33 +03:00
|
|
|
|
|
|
|
; The (virtual) proportional cost in ppm of the total amount of a failed payment
|
|
|
|
; attempt (default: 1000)
|
|
|
|
; routerrpc.attemptcostppm=900
|
2020-08-21 04:00:15 +03:00
|
|
|
|
|
|
|
; The maximum number of payment results that are held on disk by mission control
|
|
|
|
; (default: 1000)
|
2020-10-08 10:10:58 +03:00
|
|
|
; routerrpc.maxmchistory=900
|
2020-08-21 04:00:15 +03:00
|
|
|
|
|
|
|
; Path to the router macaroon
|
2020-10-08 10:10:57 +03:00
|
|
|
; routerrpc.routermacaroonpath=~/.lnd/data/chain/bitcoin/simnet/router.macaroon
|
2020-08-21 04:00:15 +03:00
|
|
|
|
|
|
|
[workers]
|
|
|
|
; Maximum number of concurrent read pool workers. This number should be
|
|
|
|
; proportional to the number of peers. (default: 100)
|
2020-10-08 10:10:58 +03:00
|
|
|
; workers.read=200
|
2020-08-21 04:00:15 +03:00
|
|
|
|
|
|
|
; Maximum number of concurrent write pool workers. This number should be
|
|
|
|
; proportional to the number of CPUs on the host. (default: 8)
|
2020-10-08 10:10:58 +03:00
|
|
|
; workers.write=8
|
2020-08-21 04:00:15 +03:00
|
|
|
|
|
|
|
; Maximum number of concurrent sig pool workers. This number should be
|
|
|
|
; proportional to the number of CPUs on the host. (default: 8)
|
2020-10-08 10:10:58 +03:00
|
|
|
; workers.sig=4
|
2020-08-21 04:00:15 +03:00
|
|
|
|
|
|
|
[caches]
|
|
|
|
|
|
|
|
; Maximum number of entries contained in the reject cache, which is used to speed
|
|
|
|
; up filtering of new channel announcements and channel updates from peers. Each
|
|
|
|
; entry requires 25 bytes. (default: 50000)
|
2020-10-08 10:10:58 +03:00
|
|
|
; caches.reject-cache-size=900000
|
2020-08-21 04:00:15 +03:00
|
|
|
|
|
|
|
; Maximum number of entries contained in the channel cache, which is used to
|
|
|
|
; reduce memory allocations from gossip queries from peers. Each entry requires
|
|
|
|
; roughly 2Kb. (default: 20000)
|
|
|
|
; caches.channel-cache-size=9000000
|
|
|
|
|
|
|
|
[protocol]
|
|
|
|
; If set, then lnd will create and accept requests for channels larger than 0.16
|
|
|
|
; BTC
|
|
|
|
; protocol.wumbo-channels=true
|
|
|
|
|
2020-12-14 23:07:12 +03:00
|
|
|
; Set to disable support for anchor commitments
|
|
|
|
; protocol.no-anchors=true
|
2020-08-21 04:00:15 +03:00
|
|
|
|
|
|
|
[db]
|
|
|
|
; The selected database backend. The current default backend is "bolt". lnd
|
|
|
|
; also has experimental support for etcd, a replicated backend.
|
2020-10-08 10:10:58 +03:00
|
|
|
; db.backend=bolt
|
2020-08-21 04:00:15 +03:00
|
|
|
|
2020-11-25 03:40:54 +03:00
|
|
|
; The maximum interval the graph database will wait between attempting to flush
|
|
|
|
; a batch of modifications to disk. Defaults to 500 milliseconds.
|
|
|
|
; db.batch-commit-interval=500ms
|
|
|
|
|
2020-08-21 04:00:15 +03:00
|
|
|
[etcd]
|
|
|
|
; Etcd database host.
|
|
|
|
; db.etcd.host=localhost:2379
|
|
|
|
|
|
|
|
; Etcd database user.
|
|
|
|
; db.etcd.user=userscopedforlnd
|
2020-10-08 10:10:58 +03:00
|
|
|
|
2020-08-21 04:00:15 +03:00
|
|
|
; Password for the database user.
|
|
|
|
; db.etcd.pass=longandsekrit
|
|
|
|
|
2020-12-16 20:34:41 +03:00
|
|
|
; Etcd namespace to use.
|
|
|
|
; db.etcd.namespace=lnd
|
|
|
|
|
2020-08-21 04:00:15 +03:00
|
|
|
; Path to the TLS certificate for etcd RPC.
|
|
|
|
; db.etcd.cert_file=/key/path
|
2020-10-08 10:10:58 +03:00
|
|
|
|
2020-08-21 04:00:15 +03:00
|
|
|
; Path to the TLS private key for etcd RPC.
|
|
|
|
; db.etcd.key_file=/a/path
|
2020-10-08 10:10:58 +03:00
|
|
|
|
2020-08-21 04:00:15 +03:00
|
|
|
; Whether we intend to skip TLS verification
|
2020-10-08 10:10:58 +03:00
|
|
|
; db.etcd.insecure_skip_verify=true
|
|
|
|
|
2020-08-21 04:00:15 +03:00
|
|
|
; Whether to collect etcd commit stats.
|
2020-10-08 10:10:58 +03:00
|
|
|
; db.etcd.collect_stats=true
|
2020-08-21 04:00:15 +03:00
|
|
|
|
2020-11-18 17:34:38 +03:00
|
|
|
; If set LND will use an embedded etcd instance instead of the external one.
|
|
|
|
; Useful for testing.
|
|
|
|
; db.etcd.embedded=false
|
|
|
|
|
2021-01-06 21:40:30 +03:00
|
|
|
; If non zero, LND will use this as client port for the embedded etcd instance.
|
|
|
|
; db.etcd.embedded_client_port=1234
|
|
|
|
|
|
|
|
; If non zero, LND will use this as peer port for the embedded etcd instance.
|
|
|
|
; db.etcd.embedded_peer_port=1235
|
|
|
|
|
2020-08-21 04:00:15 +03:00
|
|
|
[bolt]
|
|
|
|
; If true, prevents the database from syncing its freelist to disk.
|
|
|
|
; db.bolt.nofreelistsync=1
|
2020-11-09 12:21:23 +03:00
|
|
|
|
|
|
|
; Whether the databases used within lnd should automatically be compacted on
|
|
|
|
; every startup (and if the database has the configured minimum age). This is
|
|
|
|
; disabled by default because it requires additional disk space to be available
|
|
|
|
; during the compaction that is freed afterwards. In general compaction leads to
|
|
|
|
; smaller database files.
|
|
|
|
; db.bolt.auto-compact=true
|
|
|
|
|
|
|
|
; How long ago the last compaction of a database file must be for it to be
|
|
|
|
; considered for auto compaction again. Can be set to 0 to compact on every
|
|
|
|
; startup. (default: 168h)
|
|
|
|
; db.bolt.auto-compact-min-age=0
|
kvdb: add timeout options for bbolt (#4787)
* mod: bump btcwallet version to accept db timeout
* btcwallet: add DBTimeOut in config
* kvdb: add database timeout option for bbolt
This commit adds a DBTimeout option in bbolt config. The relevant
functions walletdb.Open/Create are updated to use this config. In
addition, the bolt compacter also applies the new timeout option.
* channeldb: add DBTimeout in db options
This commit adds the DBTimeout option for channeldb. A new unit
test file is created to test the default options. In addition,
the params used in kvdb.Create inside channeldb_test is updated
with a DefaultDBTimeout value.
* contractcourt+routing: use DBTimeout in kvdb
This commit touches multiple test files in contractcourt and routing.
The call of function kvdb.Create and kvdb.Open are now updated with
the new param DBTimeout, using the default value kvdb.DefaultDBTimeout.
* lncfg: add DBTimeout option in db config
The DBTimeout option is added to db config. A new unit test is
added to check the default DB config is created as expected.
* migration: add DBTimeout param in kvdb.Create/kvdb.Open
* keychain: update tests to use DBTimeout param
* htlcswitch+chainreg: add DBTimeout option
* macaroons: support DBTimeout config in creation
This commit adds the DBTimeout during the creation of macaroons.db.
The usage of kvdb.Create and kvdb.Open in its tests are updated with
a timeout value using kvdb.DefaultDBTimeout.
* walletunlocker: add dbTimeout option in UnlockerService
This commit adds a new param, dbTimeout, during the creation of
UnlockerService. This param is then passed to wallet.NewLoader
inside various service calls, specifying a timeout value to be
used when opening the bbolt. In addition, the macaroonService
is also called with this dbTimeout param.
* watchtower/wtdb: add dbTimeout param during creation
This commit adds the dbTimeout param for the creation of both
watchtower.db and wtclient.db.
* multi: add db timeout param for walletdb.Create
This commit adds the db timeout param for the function call
walletdb.Create. It touches only the test files found in chainntnfs,
lnwallet, and routing.
* lnd: pass DBTimeout config to relevant services
This commit enables lnd to pass the DBTimeout config to the following
services/config/functions,
- chainControlConfig
- walletunlocker
- wallet.NewLoader
- macaroons
- watchtower
In addition, the usage of wallet.Create is updated too.
* sample-config: add dbtimeout option
2020-12-08 02:31:49 +03:00
|
|
|
|
|
|
|
; Specify the timeout to be used when opening the database.
|
|
|
|
; db.bolt.dbtimeout=60s
|
2021-01-29 11:14:21 +03:00
|
|
|
|
|
|
|
[gossip]
|
|
|
|
; Specify a set of pinned gossip syncers, which will always be actively syncing
|
|
|
|
; whenever the corresponding peer is online. A pinned syncer does not count
|
|
|
|
; towards the configured `numgraphsyncpeers` since pinned syncers are not
|
|
|
|
; rotated. Configuring a pinned syncer does not ensure a persistent connection
|
|
|
|
; to the target peer, they will only be pinned if the connection remains active
|
|
|
|
; via some other mechanism, e.g. having an open channel.
|
|
|
|
;
|
|
|
|
; This feature is useful when trying to ensure that a node keeps its
|
|
|
|
; routing table tightly synchronized with a set of remote peers, e.g. multiple
|
|
|
|
; lightning nodes operated by the same service.
|
|
|
|
;
|
|
|
|
; Each value should be a hex-encoded pubkey of the pinned peer. Multiple pinned
|
|
|
|
; peers can be specified by setting multiple flags/fields in the config.
|
|
|
|
; gossip.pinned-syncers=pubkey1
|
|
|
|
; gossip.pinned-syncers=pubkey2
|
2021-03-04 02:12:25 +03:00
|
|
|
|
|
|
|
; The maximum number of updates for a specific channel and direction that lnd
|
|
|
|
; will accept over the channel update interval.
|
|
|
|
; gossip.max-channel-update-burst=10
|
|
|
|
; gossip.channel-update-interval=1m
|