fc8337b146
In this commit, we modify the `ChanSyncMsg` to send an invalid commitment secret in `ChanSyncMsg`. We do this in order to force the remote party to force close off-chain, if we're restoring a channel from scratch and we never had any state updates within the channel. We need to do this, as otherwise the remote party will think we can resume as they're able to verify their own commit secret for state zero. |
||
|---|---|---|
| .. | ||
| 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 | ||
| sigpool.go | ||
| size_test.go | ||
| test_utils.go | ||
| 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