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

configurechains for Sepolia testnet with alchemyProvider #2219

Closed
1 task done
MrVa55 opened this issue Apr 23, 2023 · 4 comments
Closed
1 task done

configurechains for Sepolia testnet with alchemyProvider #2219

MrVa55 opened this issue Apr 23, 2023 · 4 comments

Comments

@MrVa55
Copy link

MrVa55 commented Apr 23, 2023

Is there an existing issue for this?

  • I have searched the existing issues

Package Version

@wagmi/chains version "0.2.19",

Current Behavior

Trying to configure Sepolia with AlchemyProvider gives error "Error: unsupported network (argument="network", value={"name":"sepolia","chainId":11155111,"ensAddress":null}, code=INVALID_ARGUMENT, version=providers/5.7.2)". Page continuously reloads

Error doesn't happen with publicProvider or with other chains.

Expected Behavior

configuring sepolia to add to client without error

Steps To Reproduce

import { sepolia } from '@wagmi/core/chains';
import { alchemyProvider } from 'wagmi/providers/alchemy'
const { provider, webSocketProvider } = configureChains([sepolia], [ alchemyProvider({ apiKey: process.env.NEXT_PUBLIC_ALCHEMY_API_KEY }) ]);

Link to Minimal Reproducible Example (StackBlitz, CodeSandbox, GitHub repo etc.)

No response

Anything else?

No response

@derodero24
Copy link

derodero24 commented Apr 24, 2023

Same with wagmi v0.12.12. Work around it by using v0.12.11.

@jxom
Copy link
Member

jxom commented Apr 24, 2023

Ethers v5 doesn't support Sepolia yet. Will need to use the jsonRpcProvider as a workaround and enter the URL manually.

@technophile-04
Copy link
Contributor

Ethers v5 doesn't support Sepolia yet. Will need to use the jsonRpcProvider as a workaround and enter the URL manually.

Tysm @jxom 🙌

Question : Any reason why this breaks in 0.12.0 and not in 0.11.7 (last 0.11.x version) ?

Because I see even 0.11.x was also using ethers v5 .

The reason why I said it breaks at 0.12.0 is because I tried incrementally upgrading wagmi version starting from 0.11.6 and it started breaking at 0.12.0.

My assumption: In 0.11.x it would go to the next provider provided in an array... in our case its publiProvider() but something was changed in 0.12.0 which is breaking it, its not fallbacking

Thanks again 🙌

Copy link
Contributor

github-actions bot commented Jan 9, 2024

This issue has been locked since it has been closed for more than 14 days.

If you found a concrete bug or regression related to it, please open a new bug report with a reproduction against the latest wagmi version. If you have any other comments you can create a new discussion.

@github-actions github-actions bot locked and limited conversation to collaborators Jan 9, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants