-
Notifications
You must be signed in to change notification settings - Fork 26
fix: enforce at the code level to not support hooks #208
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Closed
Closed
Changes from all commits
Commits
Show all changes
2 commits
Select commit
Hold shift + click to select a range
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hook validation is incomplete - critical gap in swap operations.
While this validation correctly prevents configuring tick limits for pools with hooks, it doesn't prevent swaps on such pools. The
swapUniswapV4function (line 719-738) relies onmaxSlippages[address(uint160(uint256(poolId)))]which is set viasetMaxSlippage(line 267-274), bypassing this hook check entirely.Attack scenario:
maxSlippagefor a pool with hooks (no validation)swapUniswapV4with that poolId🔎 Recommended fix: Add hook validation to swap operations
Option 1: Add validation in
UniswapV4Lib.swapfunctionIn
src/libraries/UniswapV4Lib.sol, add hook validation after retrieving the poolKey:function swap( address proxy, address rateLimits, bytes32 poolId, address tokenIn, uint128 amountIn, uint128 amountOutMin, uint256 maxSlippage ) external { require(maxSlippage != 0, "MC/max-slippage-not-set"); PoolKey memory poolKey = getPoolKeyFromPoolId(poolId); + + require(address(poolKey.hooks) == address(0), "MC/pool-has-hooks"); require( tokenIn == Currency.unwrap(poolKey.currency0) ||Option 2: Add validation in
setMaxSlippagefor Uniswap V4 poolsModify
setMaxSlippageto detect and validate Uniswap V4 poolIds. However, this is more complex as you'd need to distinguish pool types.Recommendation: Option 1 is cleaner and ensures runtime protection.
🤖 Prompt for AI Agents