Wake 5 fuzzes Solidity from one prompt: an agent writes the fuzz test, an auditor reviews it in Python, and an EVM inside the Python process runs it as fast as Foundry.
Glossary definition
The 2026 major release of Wake: an EVM inside the Python process, an MCP server for agents, and fuzz tests a coding agent writes from one prompt.
Wake 5 makes an EVM embedded in the Python process,
revm, the default engine, so tests and fuzz campaigns run without a development
node. It adds wake mcp, a Model Context Protocol server that gives coding
agents the static facts the language server has, and bounds chain history to
keep multi-hour campaigns memory-stable.
With the engine in process, Wake 5 executes 29,931 transactions per second on the Daedaluzz L32 mazes, against 30,186 for Foundry and 2,600 for Echidna, as measured in the Wake 5 preprint. In manually guided fuzzing an agent can now write the harness from one prompt and an auditor reviews it as ordinary Python; the announcement describes the release and the migration guide lists the breaking changes from Wake 4.
Used in context
Wake 5 fuzzes Solidity from one prompt: an agent writes the fuzz test, an auditor reviews it in Python, and an EVM inside the Python process runs it as fast as Foundry.
Google and Janelia released the complete fruit-fly connectome on 3 September. Wired to the Daedaluzz mazes beside Echidna and Wake, how far does it get?