936fcc1f16
In this commit, we introduce a nice optimization with regards to lnd's interaction with a bitcoind backend. Within lnd, we currently have three different subsystems responsible for watching the chain: chainntnfs, lnwallet, and routing/chainview. Each of these subsystems has an active RPC and ZMQ connection to the underlying bitcoind node. This would incur a toll on the underlying bitcoind node and would cause us to miss ZMQ events, which are crucial to lnd. We remedy this issue by sharing the same connection to a bitcoind node between the different clients within lnd. |
||
|---|---|---|
| .. | ||
| btcwallet | ||
| channel_test.go | ||
| channel.go | ||
| config.go | ||
| errors.go | ||
| fee_estimator_test.go | ||
| fee_estimator.go | ||
| interface_test.go | ||
| interface.go | ||
| log.go | ||
| parameters.go | ||
| README.md | ||
| reservation.go | ||
| script_utils_test.go | ||
| script_utils.go | ||
| signdescriptor_test.go | ||
| signdescriptor.go | ||
| sigpool.go | ||
| size_test.go | ||
| size.go | ||
| test_utils.go | ||
| transactions_test.go | ||
| txout_test.go | ||
| txout.go | ||
| wallet.go | ||
| witnessgen.go | ||
lnwallet
The lnwallet package implements an abstracted wallet controller that is able to drive channel funding workflows, a number of script utilities, witness generation functions for the various Lightning scripts, revocation key derivation, and the commitment update state machine.
The package is used within lnd as the core wallet of the daemon. The wallet
itself is composed of several distinct interfaces that decouple the
implementation of things like signing and blockchain access. This separation
allows new WalletController implementations to be easily dropped into
lnd without disrupting the code base. A series of integration tests at the
interface level are also in place to ensure conformance of the implementation
with the interface.
Installation and Updating
$ go get -u github.com/lightningnetwork/lnd/lnwallet