Foundry’s November 13 nightly updates Tempo account handling and test workflows

For developers using Foundry to send Tempo transactions or run contract tests, the nightly release reported on November 13, 2026, at 15:10 (UTC+08:00) lists changes across cast, forge, cheatcodes, formatting and execution. This is a changelog of software changes, not a claim about their adoption or performance in a particular project.

Tempo accounts and transactions

cast and forge now detect Tempo configurable-account senders, while cheatcodes add configurable-account signing. In cast, the release also adds access-key authorization for those accounts, adjusts digest help, and handles raw WebAuthn signatures. Another fix uses Tempo lane nonces and carries --auth on account-abstraction (AA) transactions. A separate Tempo fix preserves 7702 authorizations when resolving a fee token.

Testing, execution and output

forge can now minimize counterexamples from stateless fuzz tests—tests that try varied inputs to find a failure, without carrying state between test cases. Its test discovery is scoped to project paths, and live logs are kept out of JSON output. An invariant-testing fix retains shrinking progress at the deadline; shrinking is the process of reducing a failing test case.

The release also lists lower per-opcode and per-call test overhead in the Ethereum Virtual Machine (EVM), which executes smart contracts; prefetching state for simulated calls on forks; and fixes for clearing storage of committed contract creations and retaining cheatcode writes made after reverted restores. These are changelog descriptions, not independent test results.

Other fixes and cleanup

cast now decodes Safe v1.3.0 result events and verifies Safe transaction hashes locally. Its wallet new command ignores CHAIN unless the user opts in. The formatter ignores blank lines when inlining bodies. A symbolic-code cleanup removes unused solver and application binary interface (ABI) code; ABI code relates to how contract calls and results are encoded.