Cairo Optimization

Apply only after tests pass and behavior is locked.

When to Use

• Improving gas/resource usage in hot paths.
• Rewriting expensive loops/arithmetic patterns.
• Optimizing storage layout and integer choices.

When NOT to Use

• Early feature prototyping without tests.
• Security review as a substitute for correctness proofs.

Quick Start

1. Confirm baseline behavior with tests.
2. Profile target paths with python3 scripts/profile.py profile.
3. Apply one optimization class at a time.
4. Re-run tests and compare resource deltas.
5. Use anti-pattern/secure-pattern pairs to keep micro-optimizations explicit.
6. Encode stable optimization rules in ../evals/cases/contract_skill_benchmark.jsonl to prevent regressions.
7. Run cairo-auditor on touched files to ensure no security regressions were introduced.