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(v2-sdk): support zksync #35

Closed

Conversation

jsy1218
Copy link
Member

@jsy1218 jsy1218 commented Jun 5, 2024

Description

We are supporting ZkSync within v2-sdk. We need to update the pair address computation for zk sync.

How Has This Been Tested?

unit tests

Are there any breaking changes?

No

(Optional) Feedback Focus

No

(Optional) Follow Ups

Will locally test within SOR before merging this PR

Copy link
Member Author

jsy1218 commented Jun 5, 2024

This stack of pull requests is managed by Graphite. Learn more about stacking.

Join @jsy1218 and the rest of your teammates on Graphite Graphite

@jsy1218 jsy1218 force-pushed the jsy1218/v2-sdk-support-zksync branch from 8826595 to 0862e87 Compare June 5, 2024 19:32
Copy link

socket-security bot commented Jun 5, 2024

New dependencies detected. Learn more about Socket for GitHub ↗︎

Package New capabilities Transitives Size Publisher
npm/[email protected] None 0 1.91 MB npm-matterlabs

View full report↗︎

@jsy1218 jsy1218 marked this pull request as ready for review June 5, 2024 19:34
@jsy1218 jsy1218 requested a review from a team as a code owner June 5, 2024 19:34
@hensha256
Copy link
Contributor

just checking you know that v2 isnt deployed? this code might be needed in future but will not be used for now until v2 is deployed

INIT_CODE_HASH
)
const salt = keccak256(['bytes'], [pack(['address', 'address'], [token0.address, token1.address])])
const initCodeHash = INIT_CODE_HASH
Copy link
Contributor

Choose a reason for hiding this comment

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

the initcodehash is different for zksync 😢

Copy link
Contributor

Choose a reason for hiding this comment

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

we dont have a v2 one (because its not deployed) but it would be different to the EVM one

Copy link
Member Author

Choose a reason for hiding this comment

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

alright, I guess I will abandon this PR for now. I thought the salt and init code hash would be the same, so that we can preempt to change the v2-sdk.

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

Successfully merging this pull request may close these issues.

2 participants