mirror of
https://github.com/lightningnetwork/lnd.git
synced 2024-11-19 09:53:54 +01:00
dfd9f6d1ca
This commit fixes to distinct bugs in the way we previously dipatched notifications for transactions which needed a historical dispatch. Previously we would compare transactions when scanning the block using the `tx.Hash` field. This was incorrect has the `Hash` field is actually the wtxid, not the txid which should be the item being compared. We fix this within the second bug fix by actually using the txid to find the proper transaction. The second fix has to due with a slight race condition which led to an off-by-one error when dispatching the historical confirmation. If while we were dispatching the confirmation, a new block was found, then we could calculate the wrong block height (off by one) as we were using the ‘currentHeight’ instead the height of the block which included the transaction. |
||
|---|---|---|
| .. | ||
| 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