Security checklist for Solidity AMM contracts, liquidity pools, and swap flows. Covers reentrancy, CEI ordering, donation or inflation attacks, oracle manipulation, slippage, admin controls, and integer math. Use when auditing or writing Solidity AMM, liquidity pool, or swap code.

DeFi AMM Security Critical vulnerability patterns and hardened implementations for Solidity AMM contracts, LP vaults, and swap functions. When to Use Writing or auditing a Solidity AMM or liquidity pool contract Implementing swap, deposit, withdraw, mint, or burn flows that hold token balances Reviewing any contract that uses token.balanceOf(address(this)) in share or reserve math Adding fee setters, pausers, oracle updates, or other admin functions to a DeFi protocol How It Works Use this as a checklist plus pattern library. Review every user entrypoint against the categories below and prefer the hardened examples over hand rolled variants. Execution Safety The shell commands in this skill are local audit examples. Run them only in a trusted checkout or disposable sandbox, and do not splice untrusted contract names, paths, RPC URLs, private keys, or user supplied flags into shell commands. Ask before installing tools or running long fuzzing/static analysis jobs that may consume significant local or paid resources. Never include secrets, private keys, seed phrases, API tokens, or mainnet signing credentials in command examples, logs, or reports. Examples Reentrancy: enforce CEI order Vulnerable: Safe: Do not write your own guard when a hardened library exists. Donation or inflation attacks Using token.balanceOf(address(this)) directly for share math lets attackers manipulate the denominator by sending tokens to the contract outside the intended path. Track internal accounting and measure actual tokens received. Oracle manipulation Spot prices are flash loan manipulable. Prefer TWAP. Slippage protection Every swap path needs caller provided slippage and a deadline. Safe reserve math For large reserve math, avoid naive a b / c when overflow risk exists. Admin controls Prefer explicit acceptance for ownership transfer and gate every privileged path. Security Checklist Reentrancy exposed entrypoints use nonReentrant CEI ordering is respected Share math does not depend on raw balanceOf(address(this)) ERC 20 transfers use SafeERC20 Deposits measure actual tokens received Oracle reads use TWAP or another manipulation resistant source Swaps require amountOutMin and deadline Overflow sensitive reserve math uses safe primitives like mulDiv Admin functions are access controlled Emergency pause exists and is tested Static analysis and fuzzing are run before production Audit Tools

defi-amm-security