mirror of
https://github.com/lightningnetwork/lnd.git
synced 2024-11-19 18:10:34 +01:00
b195d39ad7
The logger string used to identify the wtclient and wtclientrpc loggers was the same, leading to being unable to modify the log level of the wtclient logger as it would be overwritten with the wtclientrpc's one. To simplify things, we decide to use the existing RPC logger for wtclientrpc.
30 lines
1004 B
Go
30 lines
1004 B
Go
package wtclientrpc
|
|
|
|
import (
|
|
"github.com/btcsuite/btclog"
|
|
"github.com/lightningnetwork/lnd/lncfg"
|
|
"github.com/lightningnetwork/lnd/watchtower/wtclient"
|
|
)
|
|
|
|
// Config is the primary configuration struct for the watchtower RPC server. It
|
|
// contains all the items required for the RPC server to carry out its duties.
|
|
// The fields with struct tags are meant to be parsed as normal configuration
|
|
// options, while if able to be populated, the latter fields MUST also be
|
|
// specified.
|
|
type Config struct {
|
|
// Active indicates if the watchtower client is enabled.
|
|
Active bool
|
|
|
|
// Client is the backing watchtower client that we'll interact with
|
|
// through the watchtower RPC subserver.
|
|
Client wtclient.Client
|
|
|
|
// Resolver is a custom resolver that will be used to resolve watchtower
|
|
// addresses to ensure we don't leak any information when running over
|
|
// non-clear networks, e.g. Tor, etc.
|
|
Resolver lncfg.TCPResolver
|
|
|
|
// Log is the logger instance we should log output to.
|
|
Log btclog.Logger
|
|
}
|