Replies: 2 comments 4 replies
-
You'll need to use ethers v6 with opensea-js v7. It should be okay to use both ethers v5 and v6 for the meantime if you need to use v5 with other packages. |
Beta Was this translation helpful? Give feedback.
-
@ryanio Thanks for the help, but it doesn't work. More info on our use case:
Privy is the embedded wallet of our app. So to instantiate opensea-js SDK, we proceed as follows:
This code worked well (and still works) with opensea-js-6.x. But when we switched to opensea-js-7, it no longer works with this Privy provider. Privy only supports Ethers.js v5, so we have no control over the provider version we pass to opensea-js: https://docs.privy.io/guide/frontend/embedded/usage/3p-libraries The error I had at the beginning was this one:
I then modified the SDK instantiation as follows:
With this instantiation, execution goes further, but ends up crashing with the error:
Privy provides an lll provider, but using it I get the same error as above:
Having reached an impasse, we decided to switch back to opensea-js-6.x, but this version unfortunately does not support BaseSepolia I'm currently stuck. If you have an idea for a solution, it would help a lot. |
Beta Was this translation helpful? Give feedback.
-
Hello!
After switching to version 7 of opensea-js, interoperability with providers of Privy (which we use) no longer works, and this is blocking us.
Privy only supports Ethers.js version 5.7. And the other providers it supplies (Web3js and EIP1193 providers) don't work with opensea-js version 7 either.
Although, the EIP1193 provider seemed to be working fine, until I encountered an error "TypeError: signer.signTypedData is not a function at Seaport.signOrder".
Is it possible for you to add support for other providers to expand the possibility of interacting with your client?
Integrating Privy with third-party libraries:
Thank you
Beta Was this translation helpful? Give feedback.
All reactions