Prove Move smart contract properties with Move Prover and MSL.
npx skills add https://github.com/gounthar/bazel-riscv --skill aptos-move-prover
Please help me install this Agent Skill. Skill: aptos-move-prover Source: https://github.com/gounthar/bazel-riscv/tree/main/.claude/skills/aptos/move-prover Command: npx skills add https://github.com/gounthar/bazel-riscv --skill aptos-move-prover
Provides expertise on Move Prover and MSL to prove contract properties for all inputs.
Ask: "How do I specify and prove a transfer invariant with Move Prover?"
High-intent search queries and answers about installing and using this skill.
Move Prover uses the Move Specification Language (MSL) to formally verify contract properties for all inputs. You write spec blocks with preconditions, postconditions, invariants, and abort conditions, then the prover generates proofs or counterexamples using SMT-based solvers like Z3 or CVC5.
Spec blocks define formal specifications using MSL constructs: requires (preconditions), ensures (postconditions), aborts_if (abort conditions), modifies (state changes), and emits (events). Attach them to Move functions and modules to specify expected behavior the prover will verify.
Yes. Move Prover verifies invariants across complex contracts, including token transfer logic. Define invariants in spec blocks to assert properties that must hold across all inputs and state changes; the prover proves them or produces counterexamples showing violations.
When a proof fails, Move Prover returns a counterexample—a concrete input or state sequence that violates your specification. This identifies the bug or incomplete specification so you can fix the contract logic or refine the spec to match actual behavior.
No. Move Prover abstracts SMT solvers (Z3, CVC5) internally. You write specifications in MSL syntax; the prover handles solver integration. Understanding basic predicate logic and invariant design helps, but deep solver expertise is not required.
Quantifiers (forall, exists) express properties over collections or global state in MSL. Pragma directives configure verification strategies—like loop unrolling depth or timeout limits—to optimize proof search and handle complex specifications.
patrykgzFormally verify Rust code with Creusot and Pearlite specifications.
gountharGuide Move smart contract testing on Aptos with unit, integration, and Prover workflows.
hairyfPerform symbolic testing on EVM smart contracts using Halmos and SMT solvers.
gountharProve Move smart contract properties with Move Prover and MSL.
