lnd/chainntnfs
eugene de71195bcb
chainntnfs/neutrinonotify: update EndHeight after filter update
After the error is received on the filter update errChan, update the
EndHeight if we're performing a historical scan. If a block was mined
after the call to RegisterConf/RegisterSpend but before the filter was
updated, then the block would not have the filter applied. This means
that a block containing the desired conf/spend parameters would be
undetected. Fix this by ensuring the historical scan also includes this
height, as it would previously not be included.
2021-08-27 14:12:02 -04:00
..
bitcoindnotify mod+kvdb+channeldb: use btcwallet new DB interface 2021-08-04 14:55:55 +02:00
btcdnotify mod+kvdb+channeldb: use btcwallet new DB interface 2021-08-04 14:55:55 +02:00
neutrinonotify chainntnfs/neutrinonotify: update EndHeight after filter update 2021-08-27 14:12:02 -04:00
test mod+kvdb+channeldb: use btcwallet new DB interface 2021-08-04 14:55:55 +02:00
height_hint_cache_test.go mod+kvdb+channeldb: use btcwallet new DB interface 2021-08-04 14:55:55 +02:00
height_hint_cache.go multi: use kvdb.Backend for height hint DB 2021-08-04 14:55:51 +02:00
interface_dev.go chainntnfs: switch debug tag to dev 2018-10-05 12:59:34 +09:00
interface.go trivial: typo fix 2020-08-13 07:33:52 +08:00
log.go multi: init subsystem loggers via build pkg 2018-10-05 13:04:45 +09:00
README.md multi: unify code blocks in READMEs 2021-01-22 09:14:11 +01:00
test_utils.go kvdb: move channeldb/kvdb to top level 2021-05-07 14:18:56 +02:00
txnotifier_test.go txnotifier test: add test for confirmation after cancellation 2020-09-16 11:23:02 +02:00
txnotifier.go chainntnfs: skip conf dispatch if ntfn already dispatched 2021-08-27 14:11:55 -04:00

chainntnfs

Build Status MIT licensed GoDoc

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