ed7eae819a
This commit fixes a prior mishandled error when attempting historical confirmation dispatches. In the prior version of this code fragment, if the transaction under the spotlight wasn’t found within the mempool, or already in the chain, then an error would be returned by b.chainConn.GetRawTransactionVerbose, which would case the function to exit with an error. This behavior was incorrect, as during transaction re-broadcasts, it was possible for transaction not yet to be a member of either set. We fix this issue by ensuring that we treat the JSON error code as a benign error and continue with the notification registration. |
||
|---|---|---|
| .. | ||
| btcdnotify | ||
| neutrinonotify | ||
| 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