7a0b7d2742
In this commit, we update the RegisterSpendNtfn method to also take the prev output script of the item that we're attempting to watch for. This change is required due to the recent modifications in the neutrino protocol (BIP 158 + 157). With the new protocol, we'll match on the script, but then dispatch notifications based on the precise outpoint that matches. |
||
---|---|---|
.. | ||
bitcoindnotify | ||
btcdnotify | ||
neutrinonotify | ||
interface_test.go | ||
interface.go | ||
log.go | ||
queue_test.go | ||
queue.go | ||
README.md | ||
txconfnotifier_test.go | ||
txconfnotifier.go |
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
txid
has 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