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.
This commit is contained in:
7 files changed
+49
-76
No files matched your search
@@ -1081,7 +1081,7 @@ func newServer(listenAddrs []net.Addr, chanDB *channeldb.DB,
|
||||
return nil, err
|
||||
}
|
||||
|
||||
if cfg.WtClient.IsActive() {
|
||||
if cfg.WtClient.Active {
|
||||
policy := wtpolicy.DefaultPolicy()
|
||||
|
||||
if cfg.WtClient.SweepFeeRate != 0 {
|
||||
@@ -1104,7 +1104,6 @@ func newServer(listenAddrs []net.Addr, chanDB *channeldb.DB,
|
||||
Dial: cfg.net.Dial,
|
||||
AuthDial: wtclient.AuthDial,
|
||||
DB: towerClientDB,
|
||||
PrivateTower: cfg.WtClient.PrivateTowers[0],
|
||||
Policy: policy,
|
||||
ChainHash: *activeNetParams.GenesisHash,
|
||||
MinBackoff: 10 * time.Second,
|
||||
|
||||
Reference in new issue
Block a user