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
Hardcoded value seen in v3-periphery/contracts/libraries/PoolAddress.solis 0xa598dd2fba360510c5a8f02f44423a4468e902df5857dbce3ca162a43a3a31ff, which results in incorrect pool address computation.
When the value is updated to 0xe34f199b19b2b4f47f68442619d555527d244f78a3297ea89325f843f87b8b54 (as seen in the Uniswap v3 SDK and this issue Uniswap/v3-sdk#113) the pool address computations align with pools currently deployed on mainnet.
Not sure why this value is in the file. From a external user pov, it was unexpected.
The text was updated successfully, but these errors were encountered:
this issue exists on the 0.8 branch. introduced by b325bb0, which changes to pool init code hash even though the hash used to deploy pools is immutable and not affected by the changes in this commit.
Hardcoded value seen in
v3-periphery/contracts/libraries/PoolAddress.sol
is0xa598dd2fba360510c5a8f02f44423a4468e902df5857dbce3ca162a43a3a31ff
, which results in incorrect pool address computation.When the value is updated to
0xe34f199b19b2b4f47f68442619d555527d244f78a3297ea89325f843f87b8b54
(as seen in the Uniswap v3 SDK and this issue Uniswap/v3-sdk#113) the pool address computations align with pools currently deployed on mainnet.Not sure why this value is in the file. From a external user pov, it was unexpected.
The text was updated successfully, but these errors were encountered: