nemesis-auditor

To run a deep security audit for business logic flaws and state inconsistencies, use an iterative multi-pass approach. This method alternates between questioning logic assumptions and detecting state desync errors until convergence, catching complex vulnerabilities that single-pass audits miss.

Yes, this iterative code analysis tool audits smart contracts written in Solidity and Move. It is language-agnostic and also supports Rust, Go, C++, Python, and TypeScript, analyzing intricate business logic and state synchronization across these programming languages.

Iterative auditing is a feedback loop model that runs alternating passes of business logic interrogation and state inconsistency detection. It finds vulnerabilities at the intersection of logical flaws and state synchronization errors, converging only when no further issues are detected.

Yes, you need Claude Code CLI installed to perform this deep-logic security audit. The auditing agent operates through the CLI to execute iterative passes and analyze the codebase for complex vulnerabilities arising from state desync and logic flaws.

The best way to detect state synchronization errors is combining state desync detection with business logic interrogation in an iterative loop. This multi-pass approach maps state inconsistencies across the codebase, ensuring precise state synchronization free from vulnerabilities.

You should avoid a multi-pass iterative security audit when seeking rapid, superficial vulnerability scanning. This approach is designed for deep convergence on complex logic and state interplay, making it intensive and potentially excessive for simple codebases without intricate state synchronization requirements.