security-smart-contracts

Follow a four-phase procedure: map roles and value flows in reconnaissance, run syntactic and semantic sweeps, validate each candidate by tracing its full call chain, then report confirmed findings with severity and proof of concept. Static analyzers like Slither and Aderyn generate leads, but every lead needs a written attack path before promotion.

Run both, because they ship different detector sets and their disagreement is the interesting part. Slither offers richer printers and companion binaries for upgradeability and storage checks, while Aderyn produces lower false-positive volume and an MCP server. Deduplicate results by file, line, and vulnerability class.

Target a handler contract that bounds inputs with bound() rather than vm.assume, tracks ghost variables, and rotates through an actor array. Assert the six invariant families: conservation, solvency, monotonicity, access control, round trip, and no stuck funds. Set fail_on_revert to true and configure max_time_delay for time-dependent logic.

No. Checked arithmetic covers ordinary expressions only. Unchecked blocks, inline assembly, and type downcasts like uint128(x) still wrap or truncate silently at every compiler version. Every downcast and unchecked block remains an audit candidate regardless of pragma version.

Skip this workflow for off-chain application, cloud, container, or dependency security, which belong to other review processes. It also does not cover gas optimization, tokenomics or economic-design review without a security question, deep non-EVM chain analysis, or contracts you are not authorized to review.