b3643ed7a9
In this commit, we address a bug within the wallet when running with Neutrino where it wouldn't be able to mark it as synced with the chain due to not receiving a RescanFinished notification if it was a block behind the chain. This happened because of the order in which the notifications are delivered within the underlying Neutrino ChainService, FilteredBlockConnected gets dispatched before BlockConnected. This doesn't always work however because there is an implicit dependency between them in which BlockConnected must occur first. To address it, rather than switching the order in which the notifications are dispatched, we just check if we can dispatch the final RescanFinished notification after dispatching BlockConnected. Co-Authored-By: Roei Erez <roeierez@gmail.com> |
||
|---|---|---|
| .. | ||
| bitcoind_client.go | ||
| bitcoind_conn.go | ||
| block_filterer.go | ||
| block_filterer_test.go | ||
| interface.go | ||
| log.go | ||
| neutrino.go | ||
| queue.go | ||
| rpc.go | ||