f88f6f68d4
In this commit, we extract some of the helper test variables and functions into their own file and guard them under a build flag. This is needed as some unit tests will be introduced in a future commit where most of the same functions within the interface tests are reused. In order to prevent these variables and functions from being exportable, we guard them by the "debug" build tag. |
||
---|---|---|
.. | ||
bitcoindnotify | ||
btcdnotify | ||
neutrinonotify | ||
height_hint_cache_test.go | ||
height_hint_cache.go | ||
interface_debug.go | ||
interface_test.go | ||
interface.go | ||
log.go | ||
queue_test.go | ||
queue.go | ||
README.md | ||
test_utils.go | ||
txconfnotifier_test.go | ||
txconfnotifier.go |
chainntnfs
The chainntnfs package implements a set of interfaces which allow callers to receive notifications in response to specific on-chain events. The set of notifications available include:
- Notifications for each new block connected to the current best chain.
- Notifications once a
txid
has reached a specified number of confirmations. - Notifications once a target outpoint (
txid:index
) has been spent.
These notifications are used within lnd
in order to properly handle the
workflows for: channel funding, cooperative channel closures, forced channel
closures, channel contract breaches, sweeping time-locked outputs, and finally
pruning the channel graph.
This package is intentionally general enough to be applicable outside the
specific use cases within lnd
outlined above. The current sole concrete
implementation of the ChainNotifier
interface depends on btcd
.
Installation and Updating
$ go get -u github.com/lightningnetwork/lnd/chainntnfs