TL;DR
Sal is a comprehensive multi-modal workflow in Lean for designing and verifying replicated data types, combining automation, SMT assistance, and AI tools to improve correctness and debugging.
Contribution
It introduces Sal, a novel multi-modal verification workflow that integrates multiple proof techniques and debugging tools for replicated data types in Lean.
Findings
69% of verification conditions discharged by kernel automation
Counterexamples expose subtle bugs like enable-wins flag anomaly
Open-source code available at GitHub
Abstract
Designing correct replicated data types (RDTs) is challenging because replicas evolve independently and must be merged while preserving application intent. A promising approach is correct-by-construction development in a proof-oriented programming language such as F*, Dafny and Lean, where desired correctness guarantees are specified and checked as the RDTs are implemented. Recent work Neem proposes the use of replication-aware linearizability (RA linearizability) as the correctness condition for state-based CRDTs and mergeable replicated data types (MRDTs), with automation in the SMT-aided, proof-oriented programming language F*. However, SMT-centric workflows can be opaque when automation fails to discharge a verification condition (VC), and they enlarge the trusted computing base (TCB). We present Sal, a multi-modal workflow to design and verify state-based CRDTs and MRDTs in Lean.…
Peer Reviews
No public reviews on file for this paper yet. If you reviewed it on a platform where reviews are public (OpenReview, ICLR, NeurIPS, ICML), you can paste yours below so the community can read it here.
Code & Models
Videos
No videos yet. Explain this paper in a talk, walkthrough, or lecture? Add one.
