71228a6b06
This commit removes a faulty check we did to determine if the channel commitments were fully synced. We assumed that if out local commitment chain had a height higher than the remote, then we would have state updates present in our chain but not in theirs, and owed a commitment. However, there were cases where this wasn't true, and we would send a new commitment even though we had no new updates to sign. This is a protocol violation. Now we don't longer check the heights to determine if we are fully synced. A consequence of this is that we also need to check if we have any pending fee updates that are nopt yet signed, as those are considered non-empty updates. |
||
---|---|---|
.. | ||
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