lnd.xprv/chainntnfs
Valentine Wallace 98d1482942
chainntnfs/interface_test: fix unreliable historical block ntfns test
After joining the two forked chains, it is necessary to ensure they both agree on the same best hash before proceeding to UnsafeStart the notifier.
This is because when the BitcoindClient starts, it retrieves its best known block then calls GetBlockHeaderVerbose on the hash of the retrieved block. This block could be a reorged block if JoinNodes has not completed sync. If it is the case that the best block retrieved has been reorged out of the chain, GetBlockHeaderVerbose errors because bitcoind sets the number of confirmations to -1 on reorged blocks, and the btcd rpc client panics when parsing a block whose number of confirmations is negative.

This parsing error is expected to be fixed, and as a more permanent solution chain backends should ensure that the `best block` they retrieve during startup has not been reorged out of the chain.
2018-08-31 16:18:25 -07:00
..
bitcoindnotify chainntnfs/bitcoindnotify: disable height hints in testing 2018-08-26 15:34:05 -07:00
btcdnotify chainntnfs/btcdnotify: disable height hint cache in testing 2018-08-26 15:34:20 -07:00
neutrinonotify chainntnfs/neutrinonotify: update to latest API changes 2018-08-24 03:36:25 -07:00
height_hint_cache_test.go chainntnfs/height_hint_cache_test: add tests for disabled cache 2018-08-26 15:32:09 -07:00
height_hint_cache.go chainntnfs/height_hint_cache: add disable flag to hint cache 2018-08-26 15:32:06 -07:00
interface_debug.go chainntnfs: guard test chain notifier under debug flag 2018-08-24 03:36:25 -07:00
interface_test.go chainntnfs/interface_test: fix unreliable historical block ntfns test 2018-08-31 16:18:25 -07:00
interface.go chainntnfs/interface: fix TxConfStatus godocs for linter 2018-08-24 11:29:09 -07:00
log.go lnd: remove seelog logger 2017-06-25 14:19:56 +01:00
queue_test.go chainntnfs: Implement unbounded concurrent-safe FIFO queue. 2017-11-16 15:15:22 -08:00
queue.go chainntnfs: Implement unbounded concurrent-safe FIFO queue. 2017-11-16 15:15:22 -08:00
README.md multi: fix formatting issues in packge README's 2017-03-27 16:25:25 -07:00
test_utils.go chainntnfs/test_util: set 10ms trickleInterval for miner 2018-08-24 13:50:47 +02:00
txconfnotifier_test.go chainntnfs: cache confirm hints within TxConfNotifier 2018-08-21 12:55:50 -04:00
txconfnotifier.go chainntnfs: cache confirm hints within TxConfNotifier 2018-08-21 12:55:50 -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