Review the spec before the AI-generated Solidity

In an article published on November 17, 2026, the author argues that reviewing AI-generated code can become a bottleneck. The proposed shift is to review what the code must do before checking whether the code does it: write the required properties in English, have a person review them, then use a formal verification tool to check the implementation against those properties.

The article describes a demonstration by Certora CEO Mooly Sagiv involving an ERC-4626 USDC vault. An agent inferred properties and generated Solidity code and CVL rules. According to the article, the prover then found a dilution flaw of about 5 wei caused by high-water-mark rounding; the flaw was subsequently fixed.

That example also shows the limit of the workflow: a prover checks the rules it is given, so the specification itself needs scrutiny. The article identifies writing the specification as the hardest part of formal verification and discusses checking its quality before a team relies on spec review.

Further reading