defi-amm-security

Topics in the source

• DeFi AMM Security
• When to Use
• How It Works
• Execution Safety
• Examples
• Reentrancy: enforce CEI order
• Donation or inflation attacks
• Oracle manipulation

Critical vulnerability patterns and hardened implementations for Solidity AMM contracts, LP vaults, and swap functions. 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 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. 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. Vulnerable: Safe: Do not write your own guard when a hardened library exists. Using token.balanc

This is an excerpt. Refer to the complete source and its current requirements.