Skip to content

Formal-verification annotations (kani-ready) #239

@Miracle656

Description

@Miracle656

Background

Adding #[kani::proof] annotations to invariants pays off later when full kani runs are feasible. Even without running, the annotations document intent.

What to build

Annotate key invariants (signature low-S, nonce monotonicity, expiration) with #[kani::proof] proof harnesses guarded by #[cfg(kani)].

Key files

  • contracts/wallet/src/auth/proofs.rs (new)

Acceptance criteria

  • At least 3 proof harnesses
  • Documented in contracts/wallet/PROOFS.md

Drips Wave · Complexity: Advanced · 200 points

Metadata

Metadata

Assignees

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions