You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Refactor TrailsRouter to accept Multicall3 address as a constructor argument (#83)
* Refactor TrailsRouter to accept Multicall3 address as a constructor argument
- Updated TrailsRouter contract to initialize MULTICALL3 address via constructor instead of as an immutable variable.
- Modified deployRouter function to pass Multicall3 address during TrailsRouter deployment.
- Added a mock AlwaysFailingMulticall3 for testing purposes to simulate failure scenarios in tests.
- Updated relevant test cases to reflect changes in constructor and deployment logic.
* Update gas snapshots and modify expectedRouterAddress to include Multicall3 address
- Adjusted gas usage for various test cases in TrailsRouter and TrailsRouterTest to reflect recent performance changes.
- Updated expectedRouterAddress function in TrailsRouterDeploymentTest and TrailsRouterShimDeploymentTest to incorporate the Multicall3 address in the CREATE2 address calculation.
* Change MULTICALL3 to immutable in TrailsRouter contract
- Updated the MULTICALL3 state variable in the TrailsRouter contract to be immutable, ensuring it can only be set once during contract deployment. This change enhances gas efficiency and contract integrity.
* Update gas snapshots for TrailsRouter and TrailsRouterTest
- Adjusted gas usage metrics for various test cases in TrailsRouter and TrailsRouterTest to reflect recent performance optimizations.
- Minor updates made to individual test cases for consistency and accuracy in gas calculations.
* Update TrailsRouter contract to rename state variables to immutable variables
- Changed the comment for the MULTICALL3 variable to clarify its immutable status, enhancing code readability and consistency with naming conventions.
0 commit comments