Skip to content
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(uniswapx-sdk): change MULTICALL_ADDRESS to be chainId specific #46

Merged
merged 2 commits into from
Jun 17, 2024

Conversation

zhongeric
Copy link
Contributor

@zhongeric zhongeric commented Jun 17, 2024

PR Scope

Please title your PR according to the following types and scopes following conventional commits:

  • fix(SDK name): will trigger a patch version
  • chore(<type>): will not trigger any release and should be used for internal repo changes
  • <type>(public): will trigger a patch version for non-code changes (e.g. README changes)
  • feat(SDK name): will trigger a minor version
  • feat(breaking): will trigger a major version for a breaking change

Description

Since zksync has a different implementation of CREATE2, addresses are no longer consistent with other EVM chains. We've seen this in permit2 deployments. This PR updates the default exports of uniswapx-sdk to use the correct address for multicall3 on zksync, as per https://github.com/mds1/multicall/blob/main/deployments.json#L927

How Has This Been Tested?

Tests

Are there any breaking changes?

Any direct consumers of the MULTICALL_ADDRESS export of uniswapx-sdk will have to change to use multicallAddressOn(chainId). I'm not aware of any codebases using this besides fee-collector, which is what motivated this change.

If there are breaking changes, please ensure you bump the major version Bump the major version (by using the title feat(breaking): ...), post a notice in #eng-sdks, and explicitly notify all Uniswap Labs consumers of the SDK.

(Optional) Feedback Focus

[Specific parts of this PR you'd like feedback on, or that reviewers should pay closer attention to]

(Optional) Follow Ups

[Things that weren't addressed in this PR, ways you plan to build on this work, or other ways this work could be extended]

@zhongeric zhongeric requested a review from a team as a code owner June 17, 2024 17:34
Copy link
Contributor

@codyborn codyborn left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🚢

Copy link

graphite-app bot commented Jun 17, 2024

Graphite Automations

"Request reviewers once CI passes on sdks monorepo" took an action on this PR • (06/17/24)

1 reviewer was added and 1 assignee was added to this PR based on 's automation.

@zhongeric zhongeric merged commit 81dccb0 into main Jun 17, 2024
7 checks passed
Copy link

🎉 This PR is included in version @uniswap/uniswapx-sdk-v2.1.0-beta.5 🎉

The release is available on:

Your semantic-release bot 📦🚀

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants