akovalenko/lnd.xprv
1
0
Fork 0
Code Issues Pull Requests Projects Releases Wiki Activity
16c304a4c1
lnd.xprv/chainntnfs
History
Alex 89e2ba41c9 chainntnfs/bitcoindnotify: rescan blocks manually instead of rewinding
2018-04-06 20:35:27 -06:00
..
bitcoindnotify chainntnfs/bitcoindnotify: rescan blocks manually instead of rewinding 2018-04-06 20:35:27 -06:00
btcdnotify chainntnfs/btcd: add logic for mempool argument to RegisterSpendNtfn 2018-04-03 11:24:07 +02:00
neutrinonotify chainntnfs/neutrino: add bool to RegisterSpendNtfn 2018-04-03 11:24:07 +02:00
interface_test.go chainntfnfs test: add testSpendNotificationMempoolSpends for btcd backend 2018-04-03 11:24:08 +02:00
interface.go chainntnfs interface: add mempool argument to RegisterSpendNtfn 2018-04-03 11:24:07 +02:00
log.go lnd: remove seelog logger 2017-06-25 14:19:56 +01:00
queue_test.go chainntnfs: Implement unbounded concurrent-safe FIFO queue. 2017-11-16 15:15:22 -08:00
queue.go chainntnfs: Implement unbounded concurrent-safe FIFO queue. 2017-11-16 15:15:22 -08:00
README.md multi: fix formatting issues in packge README's 2017-03-27 16:25:25 -07:00
txconfnotifier_test.go chainntnfs: Send negative confirmation notifications. 2017-12-14 19:16:15 -08:00
txconfnotifier.go multi: fix several typos in godoc comments 2017-12-17 18:40:05 -08: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