-
Notifications
You must be signed in to change notification settings - Fork 47
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 #288
Comments
I'm also interested in this topic |
Wen ethers v6? |
It's been a year since the release of ethers.js v6. Many projects are now based on v6, and downgrading to v5 just for Defender is difficult. I urge you to promptly support ethers.js v6. |
What's the status on this? @shahnami @spalladino @tirumerla @MCarlomagno |
Hello @froggiedev apologies for the late reply. We have this item in our todo list and we are planning to tackle it in next few weeks. We will keep you updated once it's released. |
Hello Folks, we released ethers v6 support in the latest defender-sdk package. You can use defender-sdk package with defender 2.0. Please let us know if this works for you or any feedback you may have on defender-sdk packages. We are looking into adding ethers v6 to defender-client packages but timeline is unknown. We also have plans to deprecate defender-client packages soon would recommend switching to defender-sdk if it works for your usecases. Please let me know if you have any questions. |
Awesome news!, we'll try it out and let you guys know. Thanks |
The relay package in defender-sdk is still using ethers5. Are you planning on upgrading this this to 6? Reference:
|
Hi @stewart-lore that's correct, we upgraded ethers from v5 to v6, but we still are using 5.x version for |
I've tried using When I try and wait for a transaction to be mined using
ethers.js v6 changed Ethers v5 TransactionResponse Ethers v6 TransactionResponse |
The best way to replicate the Ethers v6 compatibility issue of the relay signer is to run the ethers-signer example in the Defender SDK. It uses Ethers v6 and is currently failing |
For anyone using Hardhat, you'll need to down the "@nomicfoundation/hardhat-chai-matchers": "^1.0.6",
"@nomiclabs/hardhat-ethers": "^2.2.3",
"@openzeppelin/defender-sdk": "^1.9.0",
"ethers": "^5.7.2",
"hardhat": "^2.18.3", |
Almost a year and still no Ethers v6? The impact on |
@jkirkpatrick we are deprecating this package in favor of defender-sdk, which already supports ethers v6. I attach some resources:
|
@MCarlomagno So you're saying the current documentation and installation guides for Defender v2 are incorrect, and if I don't start by cloning the starter repo, I am out of luck due to the lack of a migration guide? |
Could you share the incorrect docs please? so we can fix them as soon as possible |
Any plans to upgrade relayer to use ethers v6?
The text was updated successfully, but these errors were encountered: