smart-contract-formal-verification
Enables your agent to verify smart contract security. It analyzes state transition rules and properties to ensure robustness.
What it does
This tool helps ensure smart contracts (programs that run on a blockchain) work exactly as intended by using rigorous mathematical tests to find potential security flaws before they are used.
When to use it
- ✓When creating security rules for a new contract.
- ✓When auditors and developers need to review a contract together.
- ✓To generate reports showing if a contract is secure.
Example of what to ask your AI
“How can I verify if my cryptocurrency trading contract is secure from hackers?”
Want more? Open the sections below.
How to use
The easiest way: copy the message below and paste it into Claude, ChatGPT, Cursor or any AI. It reads the skill and follows the instructions.
Skill link
Ready-to-paste message
How it works
It defines the contract's operating rules, applies mathematical tests to see if these rules are always followed, and generates reports on security. This helps find problems before the contract is put into use.
Installation
Easiest way: copy the skill link and paste it into Claude, ChatGPT or Cursor asking it to follow the instructions.
In the terminal (Claude Code, Codex, Cursor), in your project folder:
npx skills add sickn33/agentic-awesome-skills --skill smart-contract-formal-verificationOr download just the file:
curl -L https://raw.githubusercontent.com/sickn33/agentic-awesome-skills/main/plugins/agentic-awesome-skills-claude/skills/smart-contract-formal-verification/SKILL.md -o SKILL.mdTechnical content (original SKILL.md)
Original text by the author, straight from GitHub.
Smart Contract Formal Verification
What it is: Applies rigorous mathematical invariant proofs, symbolic execution engines, and property-based fuzz tests to verify smart contract safety.
Overview
Provides a standardized, auditable framework and data model for Smart Contract Formal Verification operations across distributed engineering and decentralized application systems.
When to Use This Skill
- When formalizing architectural contracts, security invariants, or operational limits for Smart Contract Formal Verification.
- When cross-functional review is required between protocol developers, smart contract auditors, and AI engineering agents.
- When generating reproducible CSV, SQL DDL, JSON Schema, and Notion property registers for tracking compliance.
How It Works
- Define the parameters, thresholds, and identity bindings required for the target operational register.
- Select appropriate boundary enforcement values from validated enum select sets.
- Export standardized artifacts (CSV table, SQL DDL, JSON Schema) to integrate into validation CI pipelines.
Field Reference
| # | Field Name | Type | SQL Type | JSON Schema Type | Notion Property Type | Example Value |
|---|---|---|---|---|---|---|
| 1 | Formal Spec ID | id |
SERIAL PRIMARY KEY |
integer |
Text | SPEC-001 |
| 2 | Target Contract Module | text |
VARCHAR(64) |
string |
Text | vault_liquidity_engine |
| 3 | State Transition Property | text |
VARCHAR(128) |
string |
Text | Total Assets Equals Sum of Shares |
| 4 | Verification Method | select |
VARCHAR(64) |
string |
Select | Foundry Invariant Fuzzing |
| 5 | Fuzz Runs Count | number |
INTEGER |
number |
Number | 100000 |
| 6 | Symbolic Execution Engine | select |
VARCHAR(32) |
string |
Select | Certora Prover |
| 7 | Counterexample Discovered | select |
VARCHAR(16) |
string |
Select | No |
| 8 | Mathematical Theorem Proved | select |
VARCHAR(16) |
string |
Select | Yes |
| 9 | Invariant Violation Tolerance | currency |
NUMERIC(14,2) |
number |
Number | 0.00 |
| 10 | Formal Verification Status | select |
VARCHAR(32) |
string |
Select | Formally Verified |
| 11 | Proof Generation Date | date |
DATE |
string, format: date |
Date | 2026-10-01 |
Select Options
Verification Method
Foundry Invariant Fuzzing | Halmos Symbolic Execution | Certora Rule Prover | SMT Solver
Symbolic Execution Engine
Certora Prover | Halmos | Z3 SMT | None (Fuzzing Only)
Counterexample Discovered
Yes | No
Mathematical Theorem Proved
Yes | No
Formal Verification Status
Formally Verified | Violations Found | Proof In Progress
Relations
Audit Reference-> links to the formal review documentation or test repository.Target Architecture-> links to the deployed contract or autonomous agent runtime component.
Examples
Prompt
How do I configure and track Smart Contract Formal Verification for our production environment?
Recommended Next Step
Generate the unified field schema, SQL DDL migration, and JSON validation schema to register into your system catalog.
Workflow: Define criteria -> Run automated verification -> Record baseline -> Monitor invariants.
Best Practices
- Enforce strict typing on numerical bounds and currency amounts; avoid unstructured free-text fields for critical states.
- Re-run validation test suites on every state-altering commit or parameter change.
- Keep example data synthetic and isolated from production cryptographic keys or private endpoints.
Limitations
- Provides architectural specifications, data models, and verification schemas; does not execute direct transaction signing without authorized external tooling.
- Requires network connectivity and valid RPC credentials when querying on-chain states.
Security & Safety Notes
- All parameters declare
risk: safe. No unauthorized state modification or privileged credential access is performed. - Use synthetic dummy keys and mock addresses in test suites and local verification scripts.
Common Pitfalls
- Problem: Mismatched decimal precision between contract runtime and database register. Solution: Always verify decimals using the explicit field mapping in this reference.
- Problem: Missing authorization checks prior to state update.
…
FAQ
What are 'invariants'?
These are rules that must always be true for the contract, like 'the total money in the account can never decrease on its own'.
What is 'symbolic execution'?
It's a way to test the contract with generic values to see all possible paths it can take and if any of them lead to an error.
Can this tool fix my contract?
No, it identifies security issues. The fix needs to be made by the contract developers.
Details
Original description by the author
Foundry and Soroban formal invariant verification register: state transition rules, boundary invariant properties, and symbolic execution checks.
Popularity
- GitHub stars
- 48k
- Ranking position
- #4198
- License
- MIT
- Updated
- 10/15/2026
Comments
- …
More skills from this repository
00-andruia-consultant
Helps your agent start or improve AI projects. It analyzes code, suggests tools, and creates action plans in Spanish.
sickn33/agentic-awesome-skills
007
Lets your agent perform security audits and threat modeling. It's useful for protecting projects against attacks and vulnerabilities.
sickn33/agentic-awesome-skills
10-andruia-skill-smith
Helps your agent create or improve AI tools. It defines how tools work, writes documentation, and validates the structure.
sickn33/agentic-awesome-skills
20-andruia-niche-intelligence
Lets your agent create a summary about a specific industry. It's useful for understanding the context, rules, usage patterns, and risks of a project, using reliable sources.
sickn33/agentic-awesome-skills
Similar skills
django-security
Helps your agent implement security practices in Django applications. It focuses on authentication, authorization, and prevention against common attacks, ensuring more secure code.
affaan-m/ECC
laravel-security
Helps your agent secure Laravel applications against threats. Implements security practices for authentication, authorization, and common attack prevention.
affaan-m/ECC
module-regression
Helps your agent manage changes in large projects. Ensures code changes in one part don't break other parts.
affaan-m/ECC