608b9d96d1
This commit a bug introduced in the chain notifier while we were limiting the usage of mutexes within the package. In a prior commit a default case was introduced in the select statement in order to avoid the possibility of the main goroutine blocking when dispatching block epoch notification. In order to avoid this potentially disastrous bug, we now instead launch a new goroutine for each client to ensure that all notifications are reliably dispatched. |
||
|---|---|---|
| .. | ||
| btcdnotify | ||
| interface_test.go | ||
| interface.go | ||
| log.go | ||
| 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
txidhas 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