`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.
{
    
    BOOST_CHECK_EQUAL(AddTx(m_wallet, 1, 100, 120), 100);
    
    BOOST_CHECK_EQUAL(AddTx(m_wallet, 1, 200, 220), 100);
    
    BOOST_CHECK_EQUAL(AddTx(m_wallet, 2, 300, 0), 300);
    
    BOOST_CHECK_EQUAL(AddTx(m_wallet, 3, 420, 400), 400);
    
    
    BOOST_CHECK_EQUAL(AddTx(m_wallet, 4, 500, 390), 400);
    
    
    BOOST_CHECK_EQUAL(AddTx(m_wallet, 5, 50, 600), 300);
    
    SetMockTime(0);
}
BOOST_AUTO_TEST_CASE(LoadReceiveRequests)