07629e5da1
We check if the channel is FullySynced instead of comparing the local and remote commit chain heights, as the heights might not be in sync. Instead we call FullySynced which recently was modified to use compare the message indexes instead, which is _should_ really be in sync between the chains. The test TestChanSyncOweRevocationAndCommitForceTransition is altered to ensure the two chains at different heights before the test is started, to trigger the case that would previously fail to resend the commitment signature. |
||
|---|---|---|
| .. | ||
| 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