Olaoluwa Osuntokun ed7eae819a chainntnfs/btcdnotify: don't error if tx not found for historical conf dispatch ... This commit fixes a prior mishandled error when attempting historical confirmation dispatches. In the prior version of this code fragment, if the transaction under the spotlight wasn’t found within the mempool, or already in the chain, then an error would be returned by b.chainConn.GetRawTransactionVerbose, which would case the function to exit with an error. This behavior was incorrect, as during transaction re-broadcasts, it was possible for transaction not yet to be a member of either set. We fix this issue by ensuring that we treat the JSON error code as a benign error and continue with the notification registration.		2017-09-12 17:06:58 +02:00
..
btcd.go	chainntnfs/btcdnotify: don't error if tx not found for historical conf dispatch	2017-09-12 17:06:58 +02:00
confheap.go	chainntnfs: extend interface test to ensure initial conf height is correct	2017-07-11 17:38:43 -07:00
driver.go	multi: switch from btcrpcclient to rpcclient	2017-08-24 18:54:24 -07:00