5044cd6468
This commit fixes a prior bug in the logic for registering a new spend notification. Previously, if the transaction wasn’t found in the mempool or already confirmed within the chain, then GetRawTransactionVerbose would return an error which would cause the function itself to exit with an error. This issue would then cause the server to be unable to start up as the breach arbiter would be unable to register for spend notifications for all the channels that it needed to be watching. We fix this error simply by recognizing the particular JSON-RPC error that will be returned in this scenario and treating it as a benign error. |
||
|---|---|---|
| .. | ||
| 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