lnd/lncfg
Wilmer Paulino 0431701262
multi: only allow specifying towers to TowerClient through RPC
With the introduction of the WatchtowerClient RPC subserver, the lnd
configuration flag to specify private watchtowers for the client is no
longer needed and can lead to confusion upon users. Therefore, we remove
the flag completely, and only rely on the watchtower client being active
through a new --wtclient.active flag.
2019-07-30 15:18:17 -07:00
..
address_test.go lncfg/address_test: test LNAddress parsing, refactor addr tests 2019-01-09 16:37:56 -08:00
address.go lncfg/address: expose TCPResolver 2019-06-13 19:54:18 -07:00
caches.go lncfg/caches: adds Caches sub config 2019-04-01 16:34:04 -07:00
interface.go lncfg/interface: define Validator iface + variadic Validate 2019-04-01 16:33:50 -07:00
monitoring_off.go rpcserver+monitoring/config: enable Prometheus monitoring. 2019-06-11 11:26:09 -07:00
monitoring_on.go rpcserver+monitoring/config: enable Prometheus monitoring. 2019-06-11 11:26:09 -07:00
watchtower.go lncfg: add Watchtower config 2019-06-13 19:54:19 -07:00
workers_test.go config: add sanity check to prevent non-negative worker counts 2019-03-13 20:32:52 -07:00
workers.go lncfg/workers: reduce default write pool workers to 8 2019-04-22 16:30:27 -07:00
wtclient.go multi: only allow specifying towers to TowerClient through RPC 2019-07-30 15:18:17 -07:00