WithdrawPeriphery uses incorrect value for MAX_BPS which will allow much higher slippage than intended
WithdrawPeriphery accidentally uses an incorrect value for MAX_BPS which will allow for much higher slippage than intended.\\n```\\nuint256 internal constant MAX_BPS = 1000;\\n```\\n\\nBPS is typically 10,000 and using 1000 is inconsistent with the rest of the ecosystem contracts and tests. The result is that slippage values will be 10x higher than intended.
Correct MAX_BPS:\\n```\\n-   uint256 internal constant MAX_BPS = 1000;\\n+   uint256 internal constant MAX_BPS = 10_000;\\n```\\n
Unexpected slippage resulting in loss of user funds, likely due to MEV
```\\nuint256 internal constant MAX_BPS = 1000;\\n```\\n