ef520f49c3
In this commit, we extend the ProcessChanSyncMsg to detect a case where we don’t have the necessary revocation window to send out a new commit. This can arise if the remote party sends us a new state, but we haven’t yet fully processed their FundingLocked message yet, so we would be unable to create a new commitment state. We fix this by enumerating each of our actions in the case of an error. If we get ErrNoWindow, then this indicates that we can’t give the remote party the commitment we would like to optimistically send over. This isn’t an issue though, as in the next round, we’ll resynchronize our state. |
||
|---|---|---|
| .. | ||
| btcwallet | ||
| channel_test.go | ||
| channel.go | ||
| config.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 | ||
| 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 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