lnd/chainntnfs
Olaoluwa Osuntokun 45bbeb8f84
chainntnfs/btcdnotify: properly include SpendingHeight in SpendDetails
This commit modifies the btcdnotify implementation of the ChainNotifier
interface to properly include the height in which the watched output
was spent in the SpendDetail sent as a notification.

The set of tests have also been updated to assert that the proper
spending height is included in received notification.
2017-05-11 15:20:36 -07:00
..
btcdnotify chainntnfs/btcdnotify: properly include SpendingHeight in SpendDetails 2017-05-11 15:20:36 -07:00
README.md multi: fix formatting issues in packge README's 2017-03-27 16:25:25 -07:00
interface.go chainntnfs: add the ability to cancel spend+epoch notifications 2017-02-21 01:42:50 -08:00
interface_test.go chainntnfs/btcdnotify: properly include SpendingHeight in SpendDetails 2017-05-11 15:20:36 -07:00
log.go lnd: partially fix golint warnings 2017-03-13 16:30:23 -07:00

README.md

chainntnfs

Build Status MIT licensed GoDoc

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