03506fabe9
- It has two three methods to be created: - new: where the user can pass any custom StrategyEncoder - tycho_router: where the default SplitSwapStrategyEncoder with Tycho Router will be used - direct_execution: where the user can encode only the execution data and integrate this into their workflow. - This replaces StrategyEncoderRegistry - EVMTychoEncoder holds directly the StrategyEncoder and not the registry (per one init of the EVMTychoEncoder there is only one possible StrategyEncoder) - Update quickstart - Update bin (add subcommands to bin to create a different instance of EVMEncoderBuilder) --- don't change below this line --- ENG-4246 Took 33 minutes Took 38 seconds Took 38 seconds
14 lines
399 B
Rust
14 lines
399 B
Rust
use crate::encoding::{
|
|
errors::EncodingError,
|
|
models::{Solution, Transaction},
|
|
};
|
|
|
|
/// An encoder must implement this trait in order to encode a solution into a Transaction for
|
|
/// execution using a Tycho router or related contracts.
|
|
pub trait TychoEncoder {
|
|
fn encode_router_calldata(
|
|
&self,
|
|
solutions: Vec<Solution>,
|
|
) -> Result<Vec<Transaction>, EncodingError>;
|
|
}
|