Foundry’s November 11 nightly migrates from revm to evm2

Builders using Foundry to test contract behavior have a runtime change to review in its November 11, 2026 nightly release: the project lists a migration from revm to evm2 (#17541, by @mablr). A related refactor removes the direct revm dependency from evm-core (#18375, also by @mablr).

The release notes also list fixes across local-chain testing and EVM execution:

  • Anvil now makes reorganized blocks differ from the blocks they replace, rejects blob transactions on OP Stack, and rejects transactions below intrinsic or floor gas (#18275, #18278 and #18279, by @figtracer).
  • EVM execution retains initial call depth across specification changes and keeps isolated self-destructs until the transaction ends (#18363, by @mablr; #18332, by @figtracer).
  • Symbolic testing, which reasons about possible execution paths, gains fixes for assertion failures in symbolic revert data, invariant checks after setUp, and CREATE2 address derivation with symbolic salts (#18315, #18338 and #18355, by @figtracer).
  • Forge now ends foundry.lock with a trailing newline (#18379, by @mablr).

These are changes listed for a nightly build, not evidence of adoption or a claim that every contract workflow is affected.

Further reading