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
{{ message }}
This repository has been archived by the owner on Apr 28, 2024. It is now read-only.
sherlock-admin opened this issue
Oct 23, 2023
· 0 comments
Labels
DuplicateA valid issue that is a duplicate of an issue with `Has Duplicates` labelMediumA valid Medium severity issueRewardA payout will be made for this issue
Protocol is incompatible with ZkSync Era due to differences in address deviation
Summary
ZkSync utilizes a different prefix than most other EVM based chains. Instead of using "ff" it uses zksynceCreate2. This causes computePoolAddress to return incorrect pool addresses. Due to this the protocol will be broken when deployed there.
sherlock-admin
changed the title
Ancient Malachite Jay - Protocol is incompatible with ZkSync Era due to differences in address deviation
0x52 - Protocol is incompatible with ZkSync Era due to differences in address deviation
Oct 30, 2023
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Labels
DuplicateA valid issue that is a duplicate of an issue with `Has Duplicates` labelMediumA valid Medium severity issueRewardA payout will be made for this issue
0x52
medium
Protocol is incompatible with ZkSync Era due to differences in address deviation
Summary
ZkSync utilizes a different prefix than most other EVM based chains. Instead of using "ff" it uses zksynceCreate2. This causes
computePoolAddress
to return incorrect pool addresses. Due to this the protocol will be broken when deployed there.Vulnerability Detail
See summary
Impact
Contracts are nonfunctional on ZkSync
Code Snippet
ApproveSwapAndPay.sol#L271-L291
Tool used
Manual Review
Recommendation
Rewrite
computePoolAddress
account for this difference.Duplicate of #104
The text was updated successfully, but these errors were encountered: