UniswapError: chainId can not be found on the provider
See original GitHub issuenode version v14.18.0
npm version v6.14.15
issue
running npm run-script dev
results in
UniswapError: chainId can not be found on the provider
...
at Sniper.<anonymous> (pool-sniper/src/sniper.ts:88:43)
Issue Analytics
- State:
- Created 2 years ago
- Reactions:1
- Comments:13 (7 by maintainers)
Top Results From Across the Web
simple-uniswap-sdk - npm Package Health Analysis | Snyk
This will use your node you pass in you must pass us the chainId as well, this stops the ethers instance calling pointless...
Read more >Error "No chain ID defined" - MetaMask Support - Zendesk
If you are using the Ethereum Mainnet, try toggling networks. Specifically, tap on the top of MetaMask where it says "Ethereum Main...
Read more >ethers providers TypeScript Examples - ProgramCreek.com
You can vote up the ones you like or vote down the ones you don't like, ... throw new UniswapError( 'chainId can not...
Read more >Hardhat metamask error - "Trying to send a raw transaction ...
reactjs - Hardhat metamask error - "Trying to send a raw transaction with an invalid chainId. The expected chainId is 31337" - Stack...
Read more >Error: chainId address mismatch - Ethereum Stack Exchange
i found the answer i have been struggling with this for a week! i just changed the Network Id in the ganache to...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Hey I’m the author of simple-uniswap-sdk I’m happy to support polygon natively so you don’t need this patch. Will take a look this week (tomorrow probably) for you guys, this could remove any need to do the patch script!
Also the sdk is about to support any custom network with config so that can cover any other custom networks in future.
Super open to support any networks in the sdk so please raise any issues if you want any others supported!
Ah, damn sorry. Thought that had resolved the issue. Reopening, will diagnose shortly.