1da054625b
This commit fixes a bug which would cause the node on the _receiving_ side of a channel force close to be blind of their immediately funds on-chain. The root of the issue was that within the btcwallet implementation of the WalletController method ‘NewRawKey’, the wallet wouldn’t request notifications for the new address, as the direct function from the waddrmgr was used which skips registration of the new address. To fix, this, we now ensure that btcwallet will receive notifications for keys used within the raw p2wkh commitment output. This ensures that the wallet is aware of funds that are made available as a result of a channel force closure by the channel counter party. |
||
|---|---|---|
| .. | ||
| btcwallet | ||
| channel_test.go | ||
| channel.go | ||
| config.go | ||
| interface_test.go | ||
| interface.go | ||
| log.go | ||
| parameters.go | ||
| README.md | ||
| reservation.go | ||
| script_utils_test.go | ||
| script_utils.go | ||
| size.go | ||
| wallet.go | ||
lnwallet
[
]
(https://travis-ci.org/lightningnetwork/lnd)
[
]
(https://github.com/lightningnetwork/lnd/blob/master/LICENSE)
[
]
(http://godoc.org/github.com/lightningnetwork/lnd/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