73757eb84d
The `restoreStateLogs` function now properly restores the `addCommitHeightLocal` field of a settle or fail's parent add. Previously, any updates' parent in unsignedAckedUpdates would have the field set to the default value of 0. This would cause a force closure when receiving a commitment due to our belt-and-suspenders checks for update logs during commitment validation. The bug in question occurs because the `addCommitHeightLocal` field is only populated for a restored add if the add is on the local commitment. `TestChannelRestoreCommitHeight` is expanded in `lnwallet/channel_test.go` to demonstrate restoration now works. The faulty state transition: ``` <----fail---- <----sig----- -----rev----> (add no longer on Alice's commitment) *Alice restores* (addCommitHeightLocal of failed htlc is 0) ``` NOTE: Alice dies after sending a revocation but before signing a commitment. This is possible because there is a select block in the link that can potentially exit after sending over the revocation but before signing the next commitment state for the counterparty. |
||
|---|---|---|
| .. | ||
| btcwallet | ||
| chainfee | ||
| chancloser | ||
| chanfunding | ||
| chanvalidate | ||
| channel_test.go | ||
| channel.go | ||
| commit_sort_test.go | ||
| commit_sort.go | ||
| commitment.go | ||
| config.go | ||
| errors.go | ||
| interface_test.go | ||
| interface.go | ||
| log.go | ||
| parameters.go | ||
| README.md | ||
| reservation.go | ||
| sigpool.go | ||
| test_utils.go | ||
| test_vectors_anchors.json | ||
| test_vectors_legacy.json | ||
| transactions_test.go | ||
| transactions.go | ||
| wallet.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