2a614cc596
Follow up labelling of external transactions with labels for the transaction types we create within lnd. Since these labels will live a life of string matching, a version number and rigid format is added so that string matching is less painful. We start out with channel ID, where available, and a transaction "type". External labels, added in a previous PR, are not updated to this new versioned label because they are not lnd-initiated transactions. Label matching can check this case, then check for a version number. |
||
|---|---|---|
| .. | ||
| 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