History

Olaoluwa Osuntokun 399d9c974f chainntnfs: ensure ntfn cancellation loop will exit This commit fixes a slight bug introduced. We now ensure that the cancel loop always exists if the ChainNotifier has been signaled for a quit.		2017-08-01 17:14:11 -07:00
..
btcdnotify	chainntnfs: ensure ntfn cancellation loop will exit	2017-08-01 17:14:11 -07:00
neutrinonotify	chainntnfs: ensure ntfn cancellation loop will exit	2017-08-01 17:14:11 -07:00
interface_test.go	chainntnfs: extend interface test to ensure initial conf height is correct	2017-07-11 17:38:43 -07:00
interface.go	lnwallet: use new ChainNotifier API, typo fixes	2017-05-11 15:21:05 -07:00
log.go	lnd: remove seelog logger	2017-06-25 14:19:56 +01:00
README.md	multi: fix formatting issues in packge README's	2017-03-27 16:25:25 -07:00

README.md

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