When reth uses multiple storage backends (RocksDB for history indices + MDBX for changesets), a commit order race condition causes execution divergence during block validation.
The bug manifests as "nonce 917 too high, expected 0" because:
- RocksDB history indices commit first, saying "account X was modified at block N"
- MDBX changesets haven't committed yet
- Read path follows RocksDB's pointer to a non-existent changeset