You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Refuse to load a wallet if it requires a rescan lower than the height of
an unvalidated snapshot we're running -- in more general terms, if we
don't have data for the blocks.
// We can't rescan beyond non-pruned blocks, stop and throw an error.
2916
+
// We can't rescan beyond blocks we don't have data for, stop and throw an error.
2914
2917
// This might happen if a user uses an old wallet within a pruned node
2915
2918
// or if they ran -disablewallet for a longer time, then decided to re-enable
2916
2919
// Exit early and print an error.
2920
+
// It also may happen if an assumed-valid chain is in use and therefore not
2921
+
// all block data is available.
2917
2922
// If a block is pruned after this check, we will load the wallet,
2918
2923
// but fail the rescan with a generic error.
2919
-
error = _("Prune: last wallet synchronisation goes beyond pruned data. You need to -reindex (download the whole blockchain again in case of pruned node)");
2924
+
2925
+
error = chain.hasAssumedValidChain() ?
2926
+
_(
2927
+
"Assumed-valid: last wallet synchronisation goes beyond "
2928
+
"available block data. You need to wait for the background "
2929
+
"validation chain to download more blocks.") :
2930
+
_("Prune: last wallet synchronisation goes beyond pruned data. You need to -reindex (download the whole blockchain again in case of pruned node)");
0 commit comments