Prevent full handshake rescans on btcd reconnect.
If a rescan fails (for example, due to a disconnected btcd) in the btcd handshake, the last block height from a rescanprogress notification should be used for the next rescan job on next wallet connect. Previously, this rescan would always start at the earliest block height for any wallet address if the transaction store could not be read at wallet startup. This change unsets the boolean flag which would cause a full rescan at next connect when a rescan progress notification is received and a partial sync height is written. Fixes #87.
This commit is contained in:
parent
733677433d
commit
2c3845bbbd
1 changed files with 1 additions and 0 deletions
|
@ -394,6 +394,7 @@ func (am *AccountManager) rescanListener() {
|
|||
continue
|
||||
}
|
||||
}
|
||||
acct.fullRescan = false
|
||||
am.ds.ScheduleWalletWrite(acct)
|
||||
err := am.ds.FlushAccount(acct)
|
||||
if err != nil {
|
||||
|
|
Loading…
Reference in a new issue