73aa40f00e
We only want to register the bbolt DB backend ("bdb") when we're not
compiling for a JS/WASM build targets. That's why we want to have that
import in only one file that we can add a build tag to. We remove it in
two other places since only one import is enough anyway.
|
||
|---|---|---|
| .. | ||
| btcwallet | ||
| chainfee | ||
| chancloser | ||
| chanfunding | ||
| chanvalidate | ||
| test | ||
| channel_test.go | ||
| channel.go | ||
| commit_sort_test.go | ||
| commit_sort.go | ||
| commitment.go | ||
| config.go | ||
| errors.go | ||
| interface.go | ||
| log.go | ||
| parameters.go | ||
| README.md | ||
| reservation.go | ||
| revocation_producer_itest.go | ||
| revocation_producer.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