lnd.xprv/chainntnfs/neutrinonotify
Olaoluwa Osuntokun 36c299c1d8
chainntnfs/neutrinonotify: fix early historical confirmation dispatch
In this commit, we fix an existing bug within the logic of the neutrino
notifier. Rather than properly dispatching only once a transaction had
reached the expected number of confirmations, the historical dispatch
logic would trigger as soon as the transaction reached a single
confirmation.

This was due to the fact that we were using the scanHeight variable
which would be set to zero to calculate the number of confirmations.
The value would end up being the current height, which is generally
always greater than the number of expected confirmations. To remedy
this, we’ll now properly use the block height the transaction was
originally confirmed in to know when to dispatch.

This also applies a fix that was discovered in
93981a85c0b47622a3a5e7089b8bca9b80b834c5.
2017-12-07 19:08:48 -08:00
..
confheap.go chainntnfs/neutrinonotify: add ChainNotifier implementation for neutrino 2017-06-05 19:04:56 -07:00
driver.go chainntnfs: Rename file with typo in filename. 2017-10-19 20:00:16 -07:00
neutrino.go chainntnfs/neutrinonotify: fix early historical confirmation dispatch 2017-12-07 19:08:48 -08:00