The two-pool smart contract that I cooked up in a previous lesson was useful for educational purposes, but it has several key issues that make it unsuitable for production arbitrage:
It’s insecure
It uses the router
It requires approval
It consumes too much gas
It does too many transfers
It skips identity checks on both the
execute()
and callback functions
Th…
Keep reading with a 7-day free trial
Subscribe to Degen Code to keep reading this post and get 7 days of free access to the full post archives.