use std::{collections::HashSet, sync::LazyLock}; pub const DEFAULT_EXECUTORS_JSON: &str = include_str!("../../../config/executor_addresses.json"); pub const DEFAULT_ROUTERS_JSON: &str = include_str!("../../../config/router_addresses.json"); pub const PROTOCOL_SPECIFIC_CONFIG: &str = include_str!("../../../config/protocol_specific_addresses.json"); /// These protocols support the optimization of grouping swaps. /// /// This requires special encoding to send call data of multiple swaps to a single executor, /// as if it were a single swap. The protocol likely uses flash accounting to save gas on token /// transfers. pub static GROUPABLE_PROTOCOLS: LazyLock> = LazyLock::new(|| { let mut set = HashSet::new(); set.insert("uniswap_v4"); set.insert("balancer_v3"); set.insert("ekubo_v2"); set }); /// These protocols support the optimization of transferring straight from the user. pub static IN_TRANSFER_OPTIMIZABLE_PROTOCOLS: LazyLock> = LazyLock::new(|| { let mut set = HashSet::new(); set.insert("uniswap_v2"); set.insert("uniswap_v3"); set.insert("ekubo"); set }); /// These protocols expect funds to be in the router at the time of swap. pub static PROTOCOLS_EXPECTING_FUNDS_IN_ROUTER: LazyLock> = LazyLock::new(|| { let mut set = HashSet::new(); set.insert("vm:curve"); set.insert("balancer_v2"); // TODO remove uniswap_v4 when we add callback support for transfer optimizations set.insert("uniswap_v4"); set });