a393362eb8
This commit fixes a slight scripting related issue as a result of default policy in Bitcoin Core 0.13.1. With this version of Bitcoin Core, nodes will now enforce a policy that ensures the first argument of OP_IF is either an empty vector or a 0x01 value. Our current sent of functions to generate the witness for the delay clause of the commitment transaction instead uses a 0x00 value rather than an empty byte vector. With this commit we fix the issue by ensuring that we use an empty vector rather an 0x00 for forcing the commitment delay script pathway. |
||
|---|---|---|
| .. | ||
| 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