Hardhat v2.12 persistSnapshots Flag Alters Snapshot Restoration Behavior

Goal: Determine whether enabling the persistSnapshots flag influences the restoration of transaction‑dependent state after an evm_revert in a forked Hardhat Network, given that snapshots currently capture only EVM state and not the mempool.

Constraints: The flag persists only contract storage, code, and balances to disk; transaction logs and pending transactions are omitted. On a forked network, evm_revert

• Does enabling persistSnapshots guarantee that contract storage and balances are identical after revert, even after a node restart?
• Will upcoming Hardhat releases incorporate transaction history into snapshots to restore mempool‑dependent behavior?
• How should developers configure persistSnapshots when working with forked networks to avoid state inconsistency?