-
Notifications
You must be signed in to change notification settings - Fork 14
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
Feat/multi quoter not isolation #57
Conversation
MixedQuoterRecorder.getPoolSwapTokenAccumulation(poolHash, zeroForOne); | ||
uint256 swapAmountOut; | ||
amountIn += accAmountIn; | ||
(swapAmountOut, gasEstimateForCurAction) = quoteExactInputSingleStable( |
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.
do we need to have "quote*WithAccumulation" version for ss pool as well ? Not familiar with it's charging rule, does the fee also auto get reinvested into the pool ?
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.
should not need.
it is different from v2.
/// @param key The pool key. | ||
/// @return poolHash The hash of the pool. | ||
function getV4CLPoolHash(PoolKey memory key) internal pure returns (bytes32) { | ||
return keccak256(abi.encode(key, SWAP_V4_CL)); |
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.
curious, why not directly key.toId() here ?
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.
no special reason, just do not want to confuse , and keep same style with other pools
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.
lgtm, the only concern is that will it hit gas limit for a block i.e. 30M (for v4, actions are executed repeatedly)
i suggest we can do a quick deployment and let FE verify
All swap results will influence the outcome of subsequent swaps within the same pool