When a block reward is spent together with other outputs in the wallet and that block reward is later orphaned, the wallet does not show the other funds as available anymore.  Even a `-rescan` is not enough - only `-zapwallettxes` or an explicit `abandontransaction` "recovers" the funds.  I prepared a [test case](https://github.com/domob1812/bitcoin/blob/wallet-bug-invalidated-block-rewards/test/functional/wallet_bug.py) that shows this behaviour.

Is this a known issue or the expected behaviour?  While this situation is something that will presumably not occur in practice (as it requires a long reorg), I wonder if that transaction should be automatically abandoned as it seems clear it won't be able to be confirmed anymore.
}
            // Both not 
            error = strprintf(_("Error Transaction %s in  cannot be identified to belong to migrated s"), wtx->GetHash().GetHex());
            return false;
        }
    }
    // Do the removes
    if (txids_to_delete.size() > 0) {
        stdvector<uint256> deleted_txids;
        if (ZapSelectTx(txids_to_delete, deleted_txids) != DBErrorsLOAD_OK) {
            error = _("Error Could not delete watchonly transactions");
            return false;
        }
        if (deleted_txids != txids_to_delete) {
            error = _("Error Not all watchonly txs could be deleted");
            return false;
        }
        // Tell the GUI of each tx
        for (const uint256& txid  deleted_txids) {
            NotifyTransactionChanged(txid, CT_UPDATED);
        }
    }
    // Check the address book data in the same way we did for transactions
    stdvector<CTxDestination> dests_to_delete;
    for (const auto& addr_pair  m_address_book) {
        // Labels applied to receiving addresses should go based on IsMine
        if (addr_pair.second.purpose == "receive") {
            if (!IsMine(addr_pair.first)) {
                // Check the 
                if (data.watchonly_) {