-
Notifications
You must be signed in to change notification settings - Fork 25
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
Add 1inch AggregationRouterV6 clear signing metadata #85
base: master
Are you sure you want to change the base?
Conversation
}, | ||
{ | ||
"chainId": 324, | ||
"address": "0x111111125421cA6dc452d289314280a0f8842A65" |
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.
On zkSync ( chainId: 324) RouterV6 has different address, correct one is: 0x6fd4383cb451173d5f9304f041c7bcbf27d561ff
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.
Is there a way to officially confirm this? I was unaware of the different addresses when I checked a few through etherscan. A repo, doc page, or somewhere else to verify the address?
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.
At the moment there is two ways to verify:
- it's available on the official Github: https://github.com/1inch/limit-order-protocol
- You also can perform swap on zkSync on app.1inch.io and see where transaction goes
I also asked 1inch team put it some where into official docs
Hi @taiyangc, we have fixed the CI issues, could you update your branch so that the linter runs ? |
Based on the latest 1inch ABI definitions here https://etherscan.io/address/0x111111125421ca6dc452d289314280a0f8842a65#code
Tested locally on developer-preview