Analysis updated 2026-05-18
Formalize a crypto protocol, smart contract, or distributed system in Lean 4 to verify its correctness.
Compare multiple design candidates by their formally proven properties before building.
Use the security-audit skill to search an existing formal model for broken assumptions and counterexamples.
| internetmaximalism/lean-reinforced-concrete | 0petru/sentimo | 0xblackash/cve-2026-46333 | |
|---|---|---|---|
| Stars | 17 | 17 | 17 |
| Language | — | Python | C |
| Setup difficulty | easy | moderate | moderate |
| Complexity | 4/5 | 3/5 | 4/5 |
| Audience | developer | developer | researcher |
Figures from each repo's GitHub metadata at analysis time.
Requires familiarity with Claude Code skills and, to get real value, some background in formal methods or Lean.
This repository is a small collection of Claude skills, packaged instructions that extend what an AI coding assistant can do, focused on formal verification using the Lean 4 proof language. Each skill lives in its own folder with a description file and optional helper scripts. The first skill, lean-formal-audit, helps translate a real system, such as a cryptographic protocol, smart contract, distributed system, or business rule set, into formal mathematical statements in Lean, so its behavior can be proven correct or compared against alternative designs. The second skill, lean-security-audit, is described as the offensive counterpart: it takes an existing formal model built by the first skill and actively tries to break it, questioning the assumptions behind its safety proofs, generating edge case test scenarios from the specification, and searching for concrete counterexamples that disprove claimed properties. Using either skill means copying or linking its folder into a project's local Claude configuration folder, or into a user-wide folder to make it available across every project. There is no application to run and no separate installation process beyond that copy step. This fits developers and security researchers who already use Claude for coding and want structured help applying formal methods, the mathematical technique of proving software correct, to audit real systems for hidden assumptions or bugs. The two skills are meant to work together as a pair: the first builds confidence that a system's design is sound by proving properties about it, while the second actively tries to tear that confidence down by hunting for gaps in the proof, unfinished steps, or variables that were never properly constrained. Treating those gaps as bug signals rather than minor loose ends is the core idea behind the project, and it gives a team a repeatable way to stress test both the system being audited and the formal argument used to justify it.
A pair of Claude skills that help formalize real systems in the Lean proof language and then try to break the resulting formal proofs to find hidden bugs.
No license is stated in the README.
Setup difficulty is rated easy, with roughly 5min to a first successful run.
Mainly developer.
This repo across BitVibe Labs
Verify against the repo before relying on details.