4b15310c08
This commit fixes a race condition that was uncovered by the race condition detector surrounding cancelling active block epoch notifications. Previously we would close the main notification channel for each client, at tine this would cause a read/write race condition if an active grouting was attempting to dispatch a notification. We now fix this use by using a distinct channel for signaling cancellation to the active grouting, and another to signal cancellation to any notification observers. |
||
|---|---|---|
| .. | ||
| 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