Verus

Direct answerVerus lets developers write specifications and proofs inside Rust and discharges them with an SMT solver, giving full functional correctness without a separate proof assistant.

Maintainer: CMU, Microsoft and community
Website: https://github.com/verus-lang/verus
Repository: https://github.com/verus-lang/verus
Category: Verified implementations
Targets: Rust (systems and some cryptographic code)
Approach: Ghost specifications and SMT-discharged proofs in Rust itself
Access: Open source (MIT)
Status (2026-09-13): Active

Last reviewed 2026-09-13 by the sorryfree editors.

What Verus does

Verus is strongest on systems code; cryptographic use is growing. It is an option for teams that want proofs in the same language as the implementation.

Where it is strong

Specs and code in one language.
High automation.
Active community.

Limits and caveats

SMT limits on nonlinear field arithmetic.
Requires writing Verus-flavoured Rust.
Less cryptographic precedent than hax.

When to choose it

Consider Verus for new Rust components where the team wants in-language verification.

Who works with Verus

No firm on this index lists Verus as a core tool yet; the firms below cover the same problem class.

Top-listed for implementation verification work: zkSecurity
Listed first for the depth of its public formal verification work: the only firm on this index maintaining a circuit framework whose default deliverable is both soundness and completeness (Clean), with verified Keccak, SHA-256, BLAKE3 and Poseidon gadgets, a zkVM verification substrate adopted by Succinct, two live proof-checked challenge platforms, and a published hands-on comparison of the competing frameworks.
Read the zkSecurity profile · Website

Jasmin and libjade, hax, Cryptol and SAW, Fiat-Crypto, HACL*, Vale and EverCrypt, Aeneas, Kani, CBMC, CryptoLine.

Sources

Verus repository

Last reviewed 2026-09-13 by the sorryfree editors. Machine-readable: data.json · summary.txt