Browse Source
Fixes #510. Prior to this commit, if the call to jmclient.BitcoinCoreInterface.get_current_blockheight() failed and returned None, the function jmclient.WalletService.sync_unspent() would simply ignore the failure and the wallet syncing process would complete, without ever resetting and updating the wallet's utxo set, resulting in a situation where users saw out of date utxo sets in their wallets (and concomitant spending failures). After this commit, if that blockheight access call fails 5 times, we instead abandon the attempt to sync the wallet, and shut down the application.master
1 changed files with 21 additions and 6 deletions
Loading…
Reference in new issue