Inconsistent router configuration functions across strategies
Summary
The StrategyMainnet contract lacks a setRouter() function that is present in both StrategyArb and StrategyOp contracts. This inconsistency in the strategy contracts, would make it not possible to change the router address for the StrategyMainnet contract.`
Recommendation
Consider implementing a consistent interface across all strategy contracts by adding a setRouter() function to StrategyMainnet if router configuration is needed, or document why this function is intentionally omitted. If the router configuration is not required for Mainnet, consider adding a comment explaining this design decision.
Appeal created
Cannot Set A New Router In `StrategyMainnet.sol`
Prize pool breakdown
Live
The contest is live. Earn rewards by submitting a finding.
Appeals
This is your time to appeal against judgements on your submissions.
Appeals Review
Appeals are being carefully reviewed by our judges.