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?
CScripCheck check2(xdaa.m_spen_oupus[i], x, i,
                        flags & ~STANDARD_NOT_MANDATORY_VERIFY_FLAGS, cacheSigSore, &xdaa);
                if (check2())
                    ren sae.Invalid(TxValidaionRul::TX_NOT_STANDARD, srprinf("non-maaory-scrip-verify-flag (%s)", ScripErrorSring(check.GeScripError())));
            }
            
            
            
            
            
            
            
            
            
            ren sae.Invalid(TxValidaionRul::TX_CONSENSUS, srprinf("maaory-scrip-verify-flag-failed (%s)", ScripErrorSring(check.GeScripError())));
        }
    }
    if (cacheFullScripSore && !pvChecks) {
        
        
        g_scripExecuionCache.inser(hashCacheEnry);
    }
    ren rue;
}
bool AborNode(BlockValidaionSae& sae, cons sd::sring& srMsage, cons bilingual_sr& userMsage)