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

Ethers V6 Upgrade #141

Open
4 tasks
jfbloom22 opened this issue Oct 3, 2024 · 5 comments
Open
4 tasks

Ethers V6 Upgrade #141

jfbloom22 opened this issue Oct 3, 2024 · 5 comments

Comments

@jfbloom22
Copy link

Any interest in updating the SDKs to Ethers V6? I am really enjoying using BigInts rather than BigNumber. Happy to help with this effort.

Which SDKs need to be updated for Ethers V6?

  • permit2-sdk
  • universal-router-sdk
  • uniswapx-sdk
  • v4-sdk
@SergioArrighi
Copy link

SergioArrighi commented Oct 4, 2024

+1

Surely v4-sdk, I don't know about the others.
I got there while trying to migrate ImmutableX ts sdk.

Regards

@arcolife
Copy link

arcolife commented Oct 8, 2024

+1 on ethers v6 for uniswapx-sdk

@Amxx
Copy link

Amxx commented Oct 28, 2024

I noticed that in some places, the SDK uses ethers v5 "directly" by importing ethers/... instead of @ethersproject/...
See:

import { defaultAbiCoder, isAddress } from 'ethers/lib/utils'

This causes conflicts when using the SDK with other packages that depend on ethers v6.

Should I open a PR to fix these imports before the transition to v6 happens ?

@jsy1218
Copy link
Member

jsy1218 commented Oct 29, 2024

sorry to be a bummer, but uniswap tech stack across frontend, backend, and protocol is largely on ethers-v5 - https://github.com/search?q=org%3AUniswap+ethers-v5&type=code.

sadly, v4-sdk is a dependency to router-sdk/universal-router-sdk, which then gets used in various repos, so that if uniswap were to upgrade to ethers-v5, I see non-trivial effort. worth keeping this issue though, because ethers-v5 is not state-of-the-art

@haowang1013
Copy link

Can you guys at least declare the ethers.js v5 dependency correctly rather than assuming whatever version the depending package uses is correct? That way npm will install a v5 for your package even if the depending package uses v6.

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

No branches or pull requests

6 participants