c62af2f232
We don't want to be responsible for holding private keys -> the user is the one that should do this outside of tycho-execution Done: - Remove signature from EncodedSolution - Introduce UserTransferType and pass that everywhere instead of is_permit2_active and token_in_already_in_router - Remove signing from permit2. Added it to the encoding_utils.rs only - Mark encode_full_calldata as deprecated - Backwards compatibility: still accept a signer for the encode_full_calldata case - Update all tests Took 2 hours 10 minutes Took 13 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