assert-violation

Using assert() for input validation causes vulnerabilities because it consumes all gas on failure and should only check invariants. This Skill detects assert() misuse in Solidity contracts, identifying when it improperly validates user input or external calls instead of require().

You detect improper assert() usage by analyzing contract logic to differentiate true invariant checks from conditions triggered by external factors. This Skill examines attached Solidity files and flags assert() statements used for input validation or external call checking.

Assert() behavior changes significantly across Solidity versions regarding gas consumption and error handling. This Skill analyzes assert violations with Solidity version awareness, considering the different gas behaviors before and after version 0.8.0.

You should use require() instead of assert() when validating user input or checking external call results, reserving assert() strictly for testing internal invariants. This Skill audits smart contracts to enforce this distinction and prevent denial-of-service attacks.

Improper assert() usage can lead to denial-of-service or griefing attacks by unexpectedly reverting transactions and consuming gas when triggered by user input. This Skill identifies these vulnerabilities to ensure contracts correctly handle validation and state checks.