Builder's Guide
Search…
lnd.conf
The LND configuration file can be edited to customize your Lightning Network node.
The LND configuration file is found in your LND directory, typically in ~/.lnd
A sample configuration file can be found here or in your local copy of the LND source code. This file exists purely for illustrative purposes, and do not serve as a template for an "ideal" node.
lnd.conf
1
; Example configuration for lnd.
2
;
3
; The default location for this file is in ~/.lnd/lnd.conf on POSIX OSes,
4
; $LOCALAPPDATA/Lnd/lnd.conf on Windows,
5
; ~/Library/Application Support/Lnd/lnd.conf on Mac OS and $home/lnd/lnd.conf on
6
; Plan9.
7
; The default location of this file can be overwritten by specifying the
8
; --configfile= flag when starting lnd.
9
;
10
; Boolean values can be specified as true/false or 1/0.
11
​
12
[Application Options]
13
​
14
; The directory that lnd stores all wallet, chain, and channel related data
15
; within The default is ~/.lnd/data on POSIX OSes, $LOCALAPPDATA/Lnd/data on
16
; Windows, ~/Library/Application Support/Lnd/data on Mac OS, and $home/lnd/data
17
; on Plan9. Environment variables are expanded so they may be used. NOTE:
18
; Windows environment variables are typically %VARIABLE%, but they must be
19
; accessed with $VARIABLE here. Also, ~ is expanded to $LOCALAPPDATA on Windows.
20
; datadir=~/.lnd/data
21
​
22
; The directory that logs are stored in. The logs are auto-rotated by default.
23
; Rotated logs are compressed in place.
24
; logdir=~/.lnd/logs
25
​
26
; Number of logfiles that the log rotation should keep. Setting it to 0 disables deletion of old log files.
27
; maxlogfiles=3
28
;
29
; Max log file size in MB before it is rotated.
30
; maxlogfilesize=10
31
​
32
; Time after which an RPCAcceptor will time out and return false if
33
; it hasn't yet received a response.
34
; acceptortimeout=15s
35
​
36
; Path to TLS certificate for lnd's RPC and REST services.
37
; tlscertpath=~/.lnd/tls.cert
38
​
39
; Path to TLS private key for lnd's RPC and REST services.
40
; tlskeypath=~/.lnd/tls.key
41
​
42
; Adds an extra ip to the generated certificate. Setting multiple tlsextraip= entries is allowed.
43
; (old tls files must be deleted if changed)
44
; tlsextraip=
45
​
46
; Adds an extra domain to the generate certificate. Setting multiple tlsextradomain= entries is allowed.
47
; (old tls files must be deleted if changed)
48
; tlsextradomain=
49
​
50
; If set, then all certs will automatically be refreshed if they're close to
51
; expiring, or if any parameters related to extra IPs or domains in the cert
52
; change.
53
; tlsautorefresh=true
54
​
55
; The duration from generating the self signed certificate to the certificate
56
; expiry date. Valid time units are {s, m, h}.
57
; The below value is about 14 months (14 * 30 * 24 = 10080)
58
; tlscertduration=10080h
59
​
60
; Do not include the interface IPs or the system hostname in TLS certificate,
61
; use first --tlsextradomain as Common Name instead, if set.
62
; tlsdisableautofill=true
63
​
64
; A list of domains for lnd to periodically resolve, and advertise the resolved
65
; IPs for the backing node. This is useful for users that only have a dynamic IP,
66
; or want to expose the node at a domain.
67
; externalhosts=my-node-domain.com
68
​
69
; Sets the directory to store Let's Encrypt certificates within
70
; letsencryptdir=~/.lnd/letsencrypt
71
​
72
; The IP:port on which lnd will listen for Let's Encrypt challenges. Let's
73
; Encrypt will always try to contact on port 80. Often non-root processes are
74
; not allowed to bind to ports lower than 1024. This configuration option allows
75
; a different port to be used, but must be used in combination with port
76
; forwarding from port 80. This configuration can also be used to specify
77
; another IP address to listen on, for example an IPv6 address.
78
; letsencryptlisten=localhost:8080
79
​
80
; Request a Let's Encrypt certificate for this domain. Note that the certificate
81
; is only requested and stored when the first rpc connection comes in.
82
; letsencryptdomain=example.com
83
​
84
; Disable macaroon authentication. Macaroons are used are bearer credentials to
85
; authenticate all RPC access. If one wishes to opt out of macaroons, uncomment
86
; the line below.
87
; no-macaroons=true
88
​
89
; Enable free list syncing for the default bbolt database. This will decrease
90
; start up time, but can result in performance degradation for very large
91
; databases, and also result in higher memory usage. If "free list corruption"
92
; is detected, then this flag may resolve things.
93
; sync-freelist=true
94
​
95
; Path to write the admin macaroon for lnd's RPC and REST services if it
96
; doesn't exist. This can be set if one wishes to store the admin macaroon in a
97
; distinct location. By default, it is stored within lnd's network directory.
98
; Applications that are able to read this file, gain admin macaroon access.
99
; adminmacaroonpath=~/.lnd/data/chain/bitcoin/simnet/admin.macaroon
100
​
101
; Path to write the read-only macaroon for lnd's RPC and REST services if it
102
; doesn't exist. This can be set if one wishes to store the read-only macaroon
103
; in a distinct location. The read only macaroon allows users which can read
104
; the file to access RPCs which don't modify the state of the daemon. By
105
; default, it is stored within lnd's network directory.
106
; readonlymacaroonpath=~/.lnd/data/chain/bitcoin/simnet/readonly.macaroon
107
​
108
; Path to write the invoice macaroon for lnd's RPC and REST services if it
109
; doesn't exist. This can be set if one wishes to store the invoice macaroon in
110
; a distinct location. By default, it is stored within lnd's network directory.
111
; The invoice macaroon allows users which can read the file to gain read and
112
; write access to all invoice related RPCs.
113
; invoicemacaroonpath=~/.lnd/data/chain/bitcoin/simnet/invoice.macaroon
114
​
115
; The strategy to use for selecting coins for wallet transactions. Options are
116
; 'largest' and 'random'.
117
; coin-selection-strategy=largest
118
​
119
; A period to wait before for closing channels with outgoing htlcs that have
120
; timed out and are a result of this nodes instead payment. In addition to our
121
; current block based deadline, if specified this grace period will also be taken
122
; into account. Valid time units are {s, m, h}.
123
; payments-expiration-grace-period=30s
124
​
125
; Specify the interfaces to listen on for p2p connections. One listen
126
; address per line.
127
; All ipv4 on port 9735:
128
; listen=0.0.0.0:9735
129
; On all ipv4 interfaces on port 9735 and ipv6 localhost port 9736:
130
; listen=0.0.0.0:9735
131
; listen=[::1]:9736
132
​
133
; Disable listening for incoming p2p connections. This will override all
134
; listeners.
135
; nolisten=true
136
​
137
; Specify the interfaces to listen on for gRPC connections. One listen
138
; address per line.
139
; Only ipv4 localhost on port 10009:
140
; rpclisten=localhost:10009
141
; On ipv4 localhost port 10009 and ipv6 port 10010:
142
; rpclisten=localhost:10009
143
; rpclisten=[::1]:10010
144
; On an Unix socket:
145
; rpclisten=unix:///var/run/lnd/lnd-rpclistener.sock
146
​
147
; Specify the interfaces to listen on for REST connections. One listen
148
; address per line.
149
; All ipv4 interfaces on port 8080:
150
; restlisten=0.0.0.0:8080
151
; On ipv4 localhost port 80 and 443:
152
; restlisten=localhost:80
153
; restlisten=localhost:443
154
; On an Unix socket:
155
; restlisten=unix:///var/run/lnd-restlistener.sock
156
​
157
; A series of domains to allow cross origin access from. This controls the CORs
158
; policy of the REST RPC proxy.
159
; restcors=https://my-special-site.com
160
​
161
; Adding an external IP will advertise your node to the network. This signals
162
; that your node is available to accept incoming channels. If you don't wish to
163
; advertise your node, this value doesn't need to be set. Unless specified
164
; (with host:port notation), the default port (9735) will be added to the
165
; address.
166
; externalip=
167
;
168
; Instead of explicitly stating your external IP address, you can also enable
169
; UPnP or NAT-PMP support on the daemon. Both techniques will be tried and
170
; require proper hardware support. In order to detect this hardware support,
171
; `lnd` uses a dependency that retrieves the router's gateway address by using
172
; different built-in binaries in each platform. Therefore, it is possible that
173
; we are unable to detect the hardware and `lnd` will exit with an error
174
; indicating this. This option will automatically retrieve your external IP
175
; address, even after it has changed in the case of dynamic IPs, and advertise
176
; it to the network using the ports the daemon is listening on. This does not
177
; support devices behind multiple NATs.
178
; nat=true
179
​
180
; Disable REST API.
181
; norest=true
182
​
183
; Disable TLS for the REST API.
184
; no-rest-tls=true
185
​
186
; The ping interval for REST based WebSocket connections, set to 0 to disable
187
; sending ping messages from the server side. Valid time units are {s, m, h}.
188
; ws-ping-interval=30s
189
​
190
; The time we wait for a pong response message on REST based WebSocket
191
; connections before the connection is closed as inactive. Valid time units are
192
; {s, m, h}.
193
; ws-pong-wait=5s
194
​
195
; Shortest backoff when reconnecting to persistent peers. Valid time units are
196
; {s, m, h}.
197
; minbackoff=1s
198
​
199
; Longest backoff when reconnecting to persistent peers. Valid time units are
200
; {s, m, h}.
201
; maxbackoff=1h
202
​
203
; The timeout value for network connections in seconds, default to 120 seconds.
204
; Valid uints are {ms, s, m, h}.
205
; connectiontimeout=120s
206
​
207
; Debug logging level.
208
; Valid levels are {trace, debug, info, warn, error, critical}
209
; You may also specify <global-level>,<subsystem>=<level>,<subsystem2>=<level>,...
210
; to set log level for individual subsystems. Use lncli debuglevel --show to
211
; list available subsystems.
212
; debuglevel=debug,PEER=info
213
​
214
; Write CPU profile to the specified file.
215
; cpuprofile=
216
​
217
; Enable HTTP profiling on given port -- NOTE port must be between 1024 and
218
; 65536. The profile can be access at: http://localhost:<PORT>/debug/pprof/.
219
; profile=
220
​
221
; DEPRECATED: Allows the rpcserver to intentionally disconnect from peers with
222
; open channels. THIS FLAG WILL BE REMOVED IN 0.10.0.
223
; unsafe-disconnect=false
224
​
225
; Causes a link to replay the adds on its commitment txn after starting up, this
226
; enables testing of the sphinx replay logic.
227
; unsafe-replay=true
228
​
229
; The maximum number of incoming pending channels permitted per peer.
230
; maxpendingchannels=1
231
​
232
; The target location of the channel backup file.
233
; backupfilepath=~/.lnd/data/chain/bitcoin/simnet/channel.backup
234
​
235
; The maximum capacity of the block cache in bytes. Increasing this will result
236
; in more blocks being kept in memory but will increase performance when the
237
; same block is required multiple times.
238
; The example value below is 40 MB (1024 * 1024 * 40)
239
; blockcachesize=41943040
240
​
241
; Optional URL for external fee estimation. If no URL is specified, the method
242
; for fee estimation will depend on the chosen backend and network. Must be set
243
; for neutrino on mainnet.
244
; feeurl=https://nodes.lightning.computer/fees/v1/btc-fee-estimates.json
245
​
246
; If true, then automatic network bootstrapping will not be attempted. This
247
; means that your node won't attempt to automatically seek out peers on the
248
; network.
249
; nobootstrap=true
250
​
251
; If true, NO SEED WILL BE EXPOSED -- EVER, AND THE WALLET WILL BE ENCRYPTED
252
; USING THE DEFAULT PASSPHRASE. THIS FLAG IS ONLY FOR TESTING AND SHOULD NEVER
253
; BE USED ON MAINNET.
254
; noseedbackup=true
255
​
256
; The full path to a file (or pipe/device) that contains the password for
257
; unlocking the wallet; if set, no unlocking through RPC is possible and lnd
258
; will exit if no wallet exists or the password is incorrect; if
259
; wallet-unlock-allow-create is also set then lnd will ignore this flag if no
260
; wallet exists and allow a wallet to be created through RPC.
261
; wallet-unlock-password-file=/tmp/example.password
262
​
263
; Don't fail with an error if wallet-unlock-password-file is set but no wallet
264
; exists yet. Not recommended for auto-provisioned or high-security systems
265
; because the wallet creation RPC is unauthenticated and an attacker could
266
; inject a seed while lnd is in that state.
267
; wallet-unlock-allow-create=true
268
​
269
; Removes all transaction history from the on-chain wallet on startup, forcing a
270
; full chain rescan starting at the wallet's birthday. Implements the same
271
; functionality as btcwallet's dropwtxmgr command. Should be set to false after
272
; successful execution to avoid rescanning on every restart of lnd.
273
; reset-wallet-transactions=true
274
​
275
; The smallest channel size (in satoshis) that we should accept. Incoming
276
; channels smaller than this will be rejected, default value 20000.
277
; minchansize=
278
​
279
; The largest channel size (in satoshis) that we should accept. Incoming
280
; channels larger than this will be rejected. For non-Wumbo channels this
281
; limit remains 16777215 satoshis by default as specified in BOLT-0002.
282
; For wumbo channels this limit is 1,000,000,000 satoshis (10 BTC).
283
; Set this config option explicitly to restrict your maximum channel size
284
; to better align with your risk tolerance
285
; maxchansize=
286
​
287
; The target number of blocks in which a cooperative close initiated by a remote
288
; peer should be confirmed. This target is used to estimate the starting fee
289
; rate that will be used during fee negotiation with the peer. This target is
290
; is also used for cooperative closes initiated locally if the --conf_target
291
; for the channel closure is not set.
292
; coop-close-target-confs=10
293
​
294
; The maximum time that is allowed to pass between receiving a channel state
295
; update and signing the next commitment. Setting this to a longer duration
296
; allows for more efficient channel operations at the cost of latency.
297
; channel-commit-interval=50ms
298
​
299
; The maximum number of channel state updates that is accumulated before signing
300
; a new commitment.
301
; channel-commit-batch-size=10
302
​
303
; The default max_htlc applied when opening or accepting channels. This value
304
; limits the number of concurrent HTLCs that the remote party can add to the
305
; commitment. The maximum possible value is 483.
306
; default-remote-max-htlcs=483
307
​
308
; The duration that a peer connection must be stable before attempting to send a
309
; channel update to re-enable or cancel a pending disables of the peer's channels
310
; on the network. (default: 19m0s)
311
; chan-enable-timeout=22m
312
​
313
; The duration that must elapse after first detecting that an already active
314
; channel is actually inactive and sending channel update disabling it to the
315
; network. The pending disable can be canceled if the peer reconnects and becomes
316
; stable for chan-enable-timeout before the disable update is sent.
317
; (default: 20m0s)
318
; chan-disable-timeout=22m
319
​
320
; The polling interval between attempts to detect if an active channel has become
321
; inactive due to its peer going offline. (default: 1m0s)
322
; chan-status-sample-interval=2m
323
​
324
; Disable queries from the height-hint cache to try to recover channels stuck in
325
; the pending close state. Disabling height hint queries may cause longer chain
326
; rescans, resulting in a performance hit. Unset this after channels are unstuck
327
; so you can get better performance again.
328
; height-hint-cache-query-disable=true
329
​
330
; The polling interval between historical graph sync attempts. Each historical
331
; graph sync attempt ensures we reconcile with the remote peer's graph from the
332
; genesis block. (default: 1h0m0s)
333
; historicalsyncinterval=2h
334
​
335
; If true, will not reply with historical data that matches the range specified
336
; by a remote peer's gossip_timestamp_filter. Doing so will result in lower
337
; memory and bandwidth requirements.
338
; ignore-historical-gossip-filters=true
339
​
340
; If true, lnd will not accept channel opening requests with non-zero push
341
; amounts. This should prevent accidental pushes to merchant nodes.
342
; rejectpush=true
343
​
344
; If true, lnd will not forward any HTLCs that are meant as onward payments. This
345
; option will still allow lnd to send HTLCs and receive HTLCs but lnd won't be
346
; used as a hop.
347
; rejecthtlc=true
348
​
349
; If true, will apply a randomized staggering between 0s and 30s when
350
; reconnecting to persistent peers on startup. The first 10 reconnections will be
351
; attempted instantly, regardless of the flag's value
352
; stagger-initial-reconnect=true
353
​
354
; The maximum number of blocks funds could be locked up for when forwarding
355
; payments. (default: 2016)
356
; max-cltv-expiry=2016
357
​
358
; The maximum percentage of total funds that can be allocated to a channel's
359
; commitment fee. This only applies for the initiator of the channel. Valid
360
; values are within [0.1, 1]. (default: 0.5)
361
; max-channel-fee-allocation=0.9
362
​
363
; The maximum fee rate in sat/vbyte that will be used for commitments of
364
; channels of the anchors type. Must be large enough to ensure transaction
365
; propagation (default: 10)
366
; max-commit-fee-rate-anchors=5
367
​
368
; A threshold defining the maximum amount of dust a given channel can have
369
; after which forwarding and sending dust HTLC's to and from the channel will
370
; fail. This amount is expressed in satoshis. (default: 500000)
371
; dust-threshold=1000000
372
​
373
; If true, lnd will abort committing a migration if it would otherwise have been
374
; successful. This leaves the database unmodified, and still compatible with the
375
; previously active version of lnd.
376
; dry-run-migration=true
377
​
378
; If true, option upfront shutdown script will be enabled. If peers that we open
379
; channels with support this feature, we will automatically set the script to
380
; which cooperative closes should be paid out to on channel open. This offers the
381
; partial protection of a channel peer disconnecting from us if cooperative
382
; close is attempted with a different script.
383
; enable-upfront-shutdown=true
384
​
385
; If true, spontaneous payments through keysend will be accepted.
386
; This is a temporary solution until AMP is implemented which is expected to be soon.
387
; This option will then become deprecated in favor of AMP.
388
; accept-keysend=true
389
​
390
; If non-zero, keysend payments are accepted but not immediately settled. If the
391
; payment isn't settled manually after the specified time, it is canceled
392
; automatically. [experimental]
393
; keysend-hold-time=true
394
​
395
; If true, spontaneous payments through AMP will be accepted. Payments to AMP
396
; invoices will be accepted regardless of this setting.
397
; accept-amp=true
398
​
399
; If true, we'll attempt to garbage collect canceled invoices upon start.
400
; gc-canceled-invoices-on-startup=true
401
​
402
; If true, we'll delete newly canceled invoices on the fly.
403
; gc-canceled-invoices-on-the-fly=true
404
​
405
; If true, our node will allow htlc forwards that arrive and depart on the same
406
; channel.
407
; allow-circular-route=true
408
​
409
; Time in milliseconds between each release of announcements to the network
410
; trickledelay=180000
411
​
412
; The number of peers that we should receive new graph updates from. This option
413
; can be tuned to save bandwidth for light clients or routing nodes. (default: 3)
414
; numgraphsyncpeers=9
415
​
416
; If true, lnd will start the Prometheus exporter. Prometheus flags are
417
; behind a build/compile flag and are not available by default. lnd must be built
418
; with the monitoring tag; `make && make install tags=monitoring` to activate them.
419
; prometheus.enable=true
420
​
421
; Specify the interface to listen on for Prometheus connections.
422
; prometheus.listen=0.0.0.0:8989
423
​
424
; The alias your node will use, which can be up to 32 UTF-8 characters in
425
; length.
426
; alias=My Lightning β˜‡
427
​
428
; The color of the node in hex format, used to customize node appearance in
429
; intelligence services.
430
; color=#3399FF
431
​
432
​
433
[Bitcoin]
434
​
435
; If the Bitcoin chain should be active. Atm, only a single chain can be
436
; active.
437
bitcoin.active=true
438
​
439
; The directory to store the chain's data within.
440
; bitcoin.chaindir=~/.lnd/data/chain/bitcoin
441
​
442
; Use Bitcoin's main network.
443
; bitcoin.mainnet=true
444
​
445
; Use Bitcoin's test network.
446
; bitcoin.testnet=true
447
;
448
; Use Bitcoin's simulation test network
449
bitcoin.simnet=true
450
​
451
; Use Bitcoin's regression test network
452
; bitcoin.regtest=false
453
​
454
; Use Bitcoin's signet test network
455
; bitcoin.signet=false
456
​
457
; Connect to a custom signet network defined by this challenge instead of using
458
; the global default signet test network -- Can be specified multiple times
459
; bitcoin.signetchallenge=
460
​
461
; Specify a seed node for the signet network instead of using the global default
462
; signet network seed nodes
463
; bitcoin.signetseednode=123.45.67.89
464
​
465
; Use the btcd back-end
466
bitcoin.node=btcd
467
​
468
; Use the bitcoind back-end
469
; bitcoin.node=bitcoind
470
​
471
; Use the neutrino (light client) back-end
472
; bitcoin.node=neutrino
473
​
474
; The default number of confirmations a channel must have before it's considered
475
; open. We'll require any incoming channel requests to wait this many
476
; confirmations before we consider the channel active.
477
; bitcoin.defaultchanconfs=3
478
​
479
; The default number of blocks we will require our channel counterparty to wait
480
; before accessing its funds in case of unilateral close. If this is not set, we
481
; will scale the value according to the channel size.
482
; bitcoin.defaultremotedelay=144
483
​
484
; The maximum number of blocks we will limit the wait that our own funds are
485
; encumbered by in the case when our node unilaterally closes. If a remote peer
486
; proposes a channel with a delay above this amount, lnd will reject the
487
; channel.
488
; bitcoin.maxlocaldelay=2016
489
​
490
; The smallest HTLC we are willing to accept on our channels, in millisatoshi.
491
; bitcoin.minhtlc=1
492
​
493
; The smallest HTLC we are willing to send out on our channels, in millisatoshi.
494
; bitcoin.minhtlcout=1000
495
​
496
; The base fee in millisatoshi we will charge for forwarding payments on our
497
; channels.
498
; bitcoin.basefee=1000
499
​
500
; The fee rate used when forwarding payments on our channels. The total fee
501
; charged is basefee + (amount * feerate / 1000000), where amount is the
502
; forwarded amount.
503
; bitcoin.feerate=1
504
​
505
; The CLTV delta we will subtract from a forwarded HTLC's timelock value.
506
; bitcoin.timelockdelta=40
507
​
508
; The seed DNS server(s) to use for initial peer discovery. Must be specified as
509
; a '<primary_dns>[,<soa_primary_dns>]' tuple where the SOA address is needed
510
; for DNS resolution through Tor but is optional for clearnet users. Multiple
511
; tuples can be specified, will overwrite the default seed servers.
512
; The default seed servers are:
513
; mainnet:
514
; bitcoin.dnsseed=nodes.lightning.directory,soa.nodes.lightning.directory
515
; bitcoin.dnsseed=lseed.bitcoinstats.com
516
; testnet:
517
; bitcoin.dnsseed=test.nodes.lightning.directory,soa.nodes.lightning.directory
518
;
519
; Example for custom DNS servers:
520
; bitcoin.dnsseed=seed1.test.lightning
521
; bitcoin.dnsseed=seed2.test.lightning,soa.seed2.test.lightning
522
​
523
​
524
[Btcd]
525
​
526
; The base directory that contains the node's data, logs, configuration file,
527
; etc.
528
; btcd.dir=~/.btcd
529
​
530
; The host that your local btcd daemon is listening on. By default, this
531
; setting is assumed to be localhost with the default port for the current
532
; network.
533
; btcd.rpchost=localhost
534
​
535
; Username for RPC connections to btcd. By default, lnd will attempt to
536
; automatically obtain the credentials, so this likely won't need to be set
537
; (other than for simnet mode).
538
; btcd.rpcuser=kek
539
​
540
; Password for RPC connections to btcd. By default, lnd will attempt to
541
; automatically obtain the credentials, so this likely won't need to be set
542
; (other than for simnet mode).
543
; btcd.rpcpass=kek
544
​
545
; File containing the daemon's certificate file. This only needs to be set if
546
; the node isn't on the same host as lnd.
547
; btcd.rpccert=~/.btcd/rpc.cert
548
​
549
; The raw bytes of the daemon's PEM-encoded certificate chain which will be used
550
; to authenticate the RPC connection. This only needs to be set if the btcd
551
; node is on a remote host.
552
; btcd.rawrpccert=
553
​
554
​
555
[Bitcoind]
556
​
557
; The base directory that contains the node's data, logs, configuration file,
558
; etc.
559
; bitcoind.dir=~/.bitcoin
560
​
561
; The host that your local bitcoind daemon is listening on. By default, this
562
; setting is assumed to be localhost with the default port for the current
563
; network.
564
; bitcoind.rpchost=localhost
565
​
566
; Username for RPC connections to bitcoind. By default, lnd will attempt to
567
; automatically obtain the credentials, so this likely won't need to be set
568
; (other than for a remote bitcoind instance).
569
; bitcoind.rpcuser=kek
570
​
571
; Password for RPC connections to bitcoind. By default, lnd will attempt to
572
; automatically obtain the credentials, so this likely won't need to be set
573
; (other than for a remote bitcoind instance).
574
; bitcoind.rpcpass=kek
575
​
576
; ZMQ socket which sends rawblock and rawtx notifications from bitcoind. By
577
; default, lnd will attempt to automatically obtain this information, so this
578
; likely won't need to be set (other than for a remote bitcoind instance).
579
; bitcoind.zmqpubrawblock=tcp://127.0.0.1:28332
580
; bitcoind.zmqpubrawtx=tcp://127.0.0.1:28333
581
​
582
; Fee estimate mode for bitcoind. It must be either "ECONOMICAL" or "CONSERVATIVE".
583
; If unset, the default value is "CONSERVATIVE".
584
; bitcoind.estimatemode=CONSERVATIVE
585
​
586
; The maximum number of peers lnd will choose from the backend node to retrieve
587
; pruned blocks from. This only applies to pruned nodes.
588
; bitcoind.pruned-node-max-peers=4
589
​
590
​
591
[neutrino]
592
​
593
; Connect only to the specified peers at startup. This creates a persistent
594
; connection to a target peer. This is recommended as there aren't many
595
; neutrino compliant full nodes on the test network yet.
596
; neutrino.connect=
597
​
598
; Max number of inbound and outbound peers.
599
;
600
; NOTE: This value is currently unused.
601
; neutrino.maxpeers=
602
​
603
; Add a peer to connect with at startup.
604
; neutrino.addpeer=
605
​
606
; How long to ban misbehaving peers. Valid time units are {s, m, h}. Minimum 1
607
; second.
608
;
609
; NOTE: This value is currently unused.
610
; neutrino.banduration=
611
​
612
; Maximum allowed ban score before disconnecting and banning misbehaving peers.
613
;
614
; NOTE: This value is currently unused.
615
; neutrino.banthreshold=
616
​
617
; DEPRECATED: Use top level 'feeurl' option. Optional URL for fee estimation. If
618
; a URL is not specified, static fees will be used for estimation.
619
; neutrino.feeurl=
620
​
621
; Optional filter header in height:hash format to assert the state of neutrino's
622
; filter header chain on startup. If the assertion does not hold, then the
623
; filter header chain will be re-synced from the genesis block.
624
; neutrino.assertfilterheader=
625
​
626
; Used to help identify ourselves to other bitcoin peers (default: neutrino).
627
; neutrino.useragentname=neutrino
628
​
629
; Used to help identify ourselves to other bitcoin peers (default: 0.11.0-beta).
630
; neutrino.useragentversion=0.11.0-beta
631
​
632
; The amount of time to wait before giving up on a transaction broadcast attempt.
633
; neutrino.broadcasttimeout=5s
634
​
635
; Whether compact filters fetched from the P2P network should be persisted to disk.
636
; neutrino.persistfilters=true
637
​
638
; Validate every channel in the graph during sync by downloading the containing
639
; block. This is the inverse of routing.assumechanvalid, meaning that for
640
; Neutrino the validation is turned off by default for massively increased graph
641
; sync performance. This speedup comes at the risk of using an unvalidated view
642
; of the network for routing. Overwrites the value of routing.assumechanvalid if
643
; Neutrino is used. (default: false)
644
; neutrino.validatechannels=false
645
​
646
​
647
[Litecoin]
648
​
649
; If the Litecoin chain should be active. Atm, only a single chain can be
650
; active.
651
; litecoin.active=true
652
​
653
; The directory to store the chain's data within.
654
; litecoin.chaindir=~/.lnd/data/chain/litecoin
655
​
656
; Use Litecoin's main network.
657
; litecoin.mainnet=true
658
​
659
; Use Litecoin's test network.
660
; litecoin.testnet=true
661
;
662
; Use Litecoin's simulation test network
663
; litecoin.simnet=true
664
​
665
; Use Litecoin's regression test network
666
; litecoin.regtest=false
667
​
668
; Litecoin does not support the signet test network. The options
669
; litecoin.signet, litecoin.signetchallenge and litecoin.signetseednode are
670
; only defined because the data structure is shared with bitcoind.
671
​
672
; Use the ltcd back-end.
673
litecoin.node=ltcd
674
​
675
; Use the litecoind back-end.
676
; litecoin.node=litecoind
677
​
678
; The default number of confirmations a channel must have before it's considered
679
; open. We'll require any incoming channel requests to wait this many
680
; confirmations before we consider the channel active.
681
; litecoin.defaultchanconfs=3
682
​
683
; The default number of blocks we will require our channel counterparty to wait
684
; before accessing its funds in case of unilateral close. If this is not set, we
685
; will scale the value according to the channel size.
686
; litecoin.defaultremotedelay=144
687
​
688
; The maximum number of blocks we will limit the wait that our own funds are
689
; encumbered by in the case when our node unilaterally closes. If a remote peer
690
; proposes a channel with a delay above this amount, lnd will reject the
691
; channel.
692
; litecoin.maxlocaldelay=2016
693
​
694
; The smallest HTLC we are willing to accept on our channels, in millisatoshi.
695
; litecoin.minhtlc=1
696
​
697
; The smallest HTLC we are willing to send out on our channels, in millisatoshi.
698
; litecoin.minhtlcout=1000
699
​
700
; The base fee in millisatoshi we will charge for forwarding payments on our
701
; channels.
702
; litecoin.basefee=1000
703
​
704
; The fee rate used when forwarding payments on our channels. The total fee
705
; charged is basefee + (amount * feerate / 1000000), where amount is the
706
; forwarded amount.
707
; litecoin.feerate=1
708
​
709
; The CLTV delta we will subtract from a forwarded HTLC's timelock value.
710
; litecoin.timelockdelta=576
711
​
712
; The seed DNS server(s) to use for initial peer discovery. Must be specified as
713
; a '<primary_dns>[,<soa_primary_dns>]' tuple where the SOA address is needed
714
; for DNS resolution through Tor but is optional for clearnet users. Multiple
715
; tuples can be specified, will overwrite the default seed servers.
716
; The default seed servers are:
717
; mainnet:
718
; litecoin.dnsseed=ltc.nodes.lightning.directory,soa.nodes.lightning.directory
719
;
720
; Example for custom DNS servers:
721
; litecoin.dnsseed=seed1.test-ltc.lightning
722
; litecoin.dnsseed=seed2.test-ltc.lightning,soa.seed2.test-ltc.lightning
723
​
724
​
725
[Ltcd]
726
​
727
; The base directory that contains the node's data, logs, configuration file,
728
; etc.
729
; ltcd.dir=~/.ltcd
730
​
731
; The host that your local ltcd daemon is listening on. By default, this
732
; setting is assumed to be localhost with the default port for the current
733
; network.
734
; ltcd.rpchost=localhost
735
​
736
; Username for RPC connections to ltcd. By default, lnd will attempt to
737
; automatically obtain the credentials, so this likely won't need to be set
738
; (other than for simnet mode).
739
; ltcd.rpcuser=kek
740
​
741
; Password for RPC connections to ltcd. By default, lnd will attempt to
742
; automatically obtain the credentials, so this likely won't need to be set
743
; (other than for simnet mode).
744
; ltcd.rpcpass=kek
745
​
746
; File containing the daemon's certificate file. This only needs to be set if
747
; the node isn't on the same host as lnd.
748
; ltcd.rpccert=~/.ltcd/rpc.cert
749
​
750
; The raw bytes of the daemon's PEM-encoded certificate chain which will be used
751
; to authenticate the RPC connection. This only needs to be set if the ltcd
752
; node is on a remote host.
753
; ltcd.rawrpccert=
754
​
755
​
756
[Litecoind]
757
​
758
; The base directory that contains the node's data, logs, configuration file,
759
; etc.
760
; litecoind.dir=~/.litecoin
761
​
762
; The host that your local litecoind daemon is listening on. By default, this
763
; setting is assumed to be localhost with the default port for the current
764
; network.
765
; litecoind.rpchost=localhost
766
​
767
; Username for RPC connections to litecoind. By default, lnd will attempt to
768
; automatically obtain the credentials, so this likely won't need to be set
769
; (other than for a remote litecoind instance).
770
; litecoind.rpcuser=kek
771
​
772
; Password for RPC connections to litecoind. By default, lnd will attempt to
773
; automatically obtain the credentials, so this likely won't need to be set
774
; (other than for a remote litecoind instance).
775
; litecoind.rpcpass=kek
776
​
777
; ZMQ socket which sends rawblock and rawtx notifications from litecoind. By
778
; default, lnd will attempt to automatically obtain this information, so this
779
; likely won't need to be set (other than for a remote litecoind instance).
780
; litecoind.zmqpubrawblock=tcp://127.0.0.1:28332
781
; litecoind.zmqpubrawtx=tcp://127.0.0.1:28333
782
​
783
; Fee estimate mode for litecoind. It must be either "ECONOMICAL" or "CONSERVATIVE".
784
; If unset, the default value is "CONSERVATIVE".
785
; litecoind.estimatemode=CONSERVATIVE
786
​
787
; The maximum number of peers lnd will choose from the backend node to retrieve
788
; pruned blocks from. This only applies to pruned nodes.
789
; litecoind.pruned-node-max-peers=4
790
​
791
​
792
[autopilot]
793
​
794
; If the autopilot agent should be active or not. The autopilot agent will
795
; attempt to automatically open up channels to put your node in an advantageous
796
; position within the network graph.
797
; autopilot.active=true
798
​
799
; The maximum number of channels that should be created.
800
; autopilot.maxchannels=5
801
​
802
; The fraction of total funds that should be committed to automatic channel
803
; establishment. For example 0.6 means that 60% of the total funds available
804
; within the wallet should be used to automatically establish channels. The total
805
; amount of attempted channels will still respect the maxchannels param.
806
; autopilot.allocation=0.6
807
​
808
; Heuristic to activate, and the weight to give it during scoring. (default:
809
; top_centrality:1)
810
; autopilot.heuristic=preferential:1
811
​
812
; The smallest channel that the autopilot agent should create (default: 20000)
813
; autopilot.minchansize=20000
814
​
815
; The largest channel that the autopilot agent should create (default: 16777215)
816
; autopilot.maxchansize=20000
817
​
818
; Whether the channels created by the autopilot agent should be private or not.
819
; Private channels won't be announced to the network.
820
; autopilot.private=true
821
​
822
; The minimum number of confirmations each of your inputs in funding transactions
823
; created by the autopilot agent must have. (default: 1)
824
; autopilot.minconfs=2
825
​
826
; The confirmation target (in blocks) for channels opened by autopilot. (default:
827
; 3)
828
; autopilot.conftarget=2
829
​
830
​
831
[tor]
832
; Allow outbound and inbound connections to be routed through Tor
833
; tor.active=true
834
​
835
; Allow the node to connect to non-onion services directly via clearnet. This
836
; allows the node operator to use direct connections to peers not running behind
837
; Tor, thus allowing lower latency and better connection stability.
838
; WARNING: This option will reveal the source IP address of the node, and should
839
; be used only if privacy is not a concern.
840
; tor.skip-proxy-for-clearnet-targets=true
841
​
842
; The port that Tor's exposed SOCKS5 proxy is listening on. Using Tor allows
843
; outbound-only connections (listening will be disabled) -- NOTE port must be
844
; between 1024 and 65535
845
; tor.socks=9050
846
​
847
; The DNS server as IP:PORT that Tor will use for SRV queries - NOTE must have
848
; TCP resolution enabled. The current active DNS server for Testnet listening is
849
; nodes.lightning.directory
850
; tor.dns=nodes.lightning.directory
851
​
852
; Enable Tor stream isolation by randomizing user credentials for each
853
; connection. With this mode active, each connection will use a new circuit.
854
; This means that multiple applications (other than lnd) using Tor won't be mixed
855
; in with lnd's traffic.
856
;
857
; This option may not be used while direct connections are enabled, since direct
858
; connections compromise source IP privacy by default.
859
; tor.streamisolation=true
860
​
861
; The host:port that Tor is listening on for Tor control connections (default:
862
; localhost:9051)
863