`ScanForWalletTransactions()` has the following comment about its return value:

```
 * Returns null if scan was successful. Otherwise, if a complete rescan was not
 * possible (due to pruning or corruption), returns pointer to the most recent
 * block that could not be scanned.
```

This is not strictly true. If `abortrescan` is called, then `ScanForWalletTransactions()` will return `nullptr`, even though the scan wasn't successful to the tip.

This in turn causes a minor bug in `importmulti`, where the call doesn't return the correct error and warning about potentially not finding transactions if `abortrescan` was called.

I think the correct fix is for `ScanForWalletTransactions()` to inform the caller that the rescan was aborted.
{
        return CalculateMaximumSignedInputSize(tx->vout[out], pwallet, use_max_sig);
    }
    void GetAmounts(std::list<COutputEntry>& listReceived,
                    std::list<COutputEntry>& listSent, CAmount& nFee, const isminefilter& filter) const;
    bool IsFromMe(const isminefilter& filter) const
    {
        return (GetDebit(filter) > 0);
    }
    
    bool IsEquivalentTo(const CWalletTx& tx) const;
    bool InMempool() const;
    bool IsTrusted(interfaces::Chain::Lock& locked_chain) const;
    int64_t GetTxTime() const;
    
    bool RelayWalletTransaction(interfaces::Chain::Lock& locked_chain, CConnman* connman);
    
    bool AcceptToMemoryPool(interfaces::Chain::Lock& locked_chain, const CAmount& nAbsurdFee, CValidationState& state);
    
    
    
    
    
    
    std::set<uint256> GetConflicts() const NO_THREAD_SAFETY_ANALYSIS;
};
class COutput