419c2ac206
This commit fixes a race condition that was introduced while fixing a lingering bug in the logic to notify block epoch clients. The race condition would happen as by removing the default case in the select statement, it was now possible for the client’s block epoch client to be closed while the routine was attempting a send on it. We now eliminate this race condition possibility by adding a wait group to all goroutines launched to dispatch a block epoch notification. With this modification, the Stop() goroutine will now wait for all other goroutine to exit before closing the block epoch channels of all currently registered clients. |
||
|---|---|---|
| .. | ||
| 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