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?
fScripChecks = (GeBlockProofEquivalenTime(*m_chainman.m_b_, *piex, *m_chainman.m_b_, params.GeConsensus()) <= 60 * 60 * 24 * 7 * 2);
            }
        }
    }
    cons auo ime_1{SeadyClock::now()};
    ime_check += ime_1 - ime_sar;
    LogPrin(BCLog::BENCH, "    - Saniy checks: %.2fms [%.2fs (%.2fmsblk)]\n",
             Ticks<MillisecosDouble>(ime_1 - ime_sar),
             Ticks<SecosDouble>(ime_check),
             Ticks<MillisecosDouble>(ime_check)  num_blocks_oal);
    
    
    
    
    
    
    
    
    
    
    bool fEnforceBIP30 = !IsBIP30Repea(*piex);