0f9af65846
The transfer from the user into the router is supposed to happen in the router (we only support this in the executors for callback constrained protocols). This is necessary because of some security concerns that were found in the audit. This way we reduce the space of attack. - Refactored TransferOptimization not to handle TransferTypes anymore but just return bools. - Split get_transfer_type into get_transfers and get_in_between_transfer. Updates tests - Updated the strategies to use this - Updated function signatures to pass transfer_from and funds_receiver - Updated SwapEncoders to handle this - SplitSwapStrategy just assumes all tokens are sent to and from the router at all times Took 2 hours 46 minutes
Tycho Execution
Tycho Execution makes it easy to trade on different DEXs by handling the complex encoding for you. Instead of creating custom code for each DEX, you get a simple, ready-to-use tool that generates the necessary data to execute trades. It's designed to be safe, straightforward, and quick to set up, so anyone can start trading without extra effort.
For complete documentation, see Tycho docs here.
Examples
To get started on encoding, have a look at our Encoding example. For a complete example please refer to the Tycho Quickstart guide.
Security
All audits of the Tycho Router and Executor contracts can be found here. The vulnerabilities discovered during the audits have been acknowledged and addressed or accepted.
Report a Vulnerability
Contact security@propellerheads.xyz