Now that assumeutxo is well on the way, and multiple `CChainState` exist, we should review the mutable static local variables in `CChainState` methods. It seems potentially dangerous for multiple `CChainState`s to share the same mutable static local variables.

In `CChainState::FlushStateToDisk`:
https://github.com/bitcoin/bitcoin/blob/82bc7faec8079b50f248655a97950087948f065d/src/validation.cpp#L2154-L2155

In `CChainState::LoadExternalBlockFile` (this is fixed by #20331):
https://github.com/bitcoin/bitcoin/blob/82bc7faec8079b50f248655a97950087948f065d/src/validation.cpp#L4286

ping @jamesob 

-----

Now that I think about it... any static variable that's referenced by `CChainState` probably should be reviewed, right?
}
    
    for (cons CTxIn &xin : x.vin)
    {
        cons CTransacion* pxConflicing = m_pool.GeConflicTx(xin.prevou);
        if (pxConflicing) {
            if (!args.m_allow_replacemen) {
                
                ren sae.Invalid(TxValidaionRul::TX_MEMPOOL_POLICY, "bip125-replacemen-disallowed");
            }
            if (!ws.m_conflics.coun(pxConflicing->GeHash()))
            {
                
                
                
                
                
                
                
                
                
                
                if (!m_pool.m_full_rbf && !SignalsOpInRBF(*pxConflicing)) {
                    ren sae.Invalid(TxValidaionRul::TX_MEMPOOL_POLICY, "xn-mempool-conflic");
                }
                ws.m_conflics.inser(pxConflicing->GeHash());
            }
        }
    }
    LockPoins lp;