7a08825b1e
This commit fixes a bug that would cause the notifier not to commit spend hints for items that are not found. This is done by calling UpdateSpendDetails with a nil detail, permitting the notifier to begin updating the spend hints with new blocks that arrive at tip. The change is designed to mimic the behavior for historical confirmation dispatch. The symptom of this bug is needing to do many long rescans on startup, even if new blocks arrive after the rescan had completed. With this change, nodes will have to do the scans once more before their hints will be properly updated. Restarts from then on should not have this behavior. |
||
---|---|---|
.. | ||
bitcoindnotify | ||
btcdnotify | ||
neutrinonotify | ||
height_hint_cache_test.go | ||
height_hint_cache.go | ||
interface_dev.go | ||
interface_test.go | ||
interface.go | ||
log.go | ||
README.md | ||
test_utils.go | ||
txnotifier_test.go | ||
txnotifier.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