-
Notifications
You must be signed in to change notification settings - Fork 952
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
No compatible chain found for the selected EVM version. Consider opening an issue to update our internal store with your desired chainId. #5389
Comments
Yes I'm currently experiencing same issue, except for Chain id 14 (Flare) and chain 16 (Songbird) if I switched to chain id 1 I have no issue and can interact with that network. Same for other EVM chains I've been developing and working on UUPS Upgradeable contracts all day and all last night. this issue seemed to have happened mid day today while I was testing a contract. I've had to resort to interacting with the contracts and performing upgrades via hardhat, ethers, and node.js with scripts which sucks as i used remix for mainly testing with ease. hopefully this issue gets resolved.. ive noticed they had a recent fail on their recent push maybe that has something to do with it |
Also happens with chain ID 8453 (Base) |
I am also experiencing this issue with Chain ID 8008135 (Fhenix Helium) |
This is a weird problem, I have just deployed my contract few days ago, and the today, when I want to deploy a new one with another wallet, it's said:
Honestly,I don't know what happened, just don't work anymore. |
I am experiencing the same issue in Remix. When attempting to deploy a contract on the Amoy network (chain ID: 80002), I receive the following error message: "No compatible chain found for the selected EVM version. Consider opening an issue to update our internal store with your desired chainId." Despite this message, I was able to deploy the contract. However, none of the functions in the contract are working after deployment. |
Same here, a contract that worked perfectly fine untill few hours ago now gives me the following error message "No compatible chain found for the selected EVM version. Consider opening an issue to update our internal store with your desired chainId." Currently on Blast Sepolia, chainID: 168587773 |
Same issue on Amoy Network(Chain ID:80002). In my case I was trying to access deployed contract using 'At Address' and this error occured |
I've been getting the same error since yesterday. Chain ID: 167009 |
I've been getting the same error since today. Chain ID: 1319 |
I've been getting the same error since today. Chain ID: 1337 |
I have same error since today |
yes just observed that now, any solution? |
same problem different chain since today |
same issue with all chains |
Same issue for me on all chains i.e BSC, Bsc testnet, Sepolia etc |
Same issue for me (ChainId: 1301) |
I encountered the same problem with Remix when I tried to deploy the contract on Ganache's local blockchain and received the message. However, trying to change the EVM version on Remix did not solve the problem. However, contract deployment can be carried out normally on Sepolia testnet. |
its fixed everyone |
Great! Everything is normal here now. |
Describe the bug
A clear and concise description of what the bug is.
i have been developing using UUPS upgradebale proxy pattern and mid upgrade remix got stuck. so i refrresehd the page and clear my activity on metmask. once i did this i then tried to interact with contracts and or upgrade my contracts and i get this error
No compatible chain found for the selected EVM version.
Consider opening an issue to update our internal store with your desired chainId.
To Reproduce
Steps to reproduce the behavior:
then this error
No compatible chain found for the selected EVM version.
Consider opening an issue to update our internal store with your desired chainId.
Expected behavior
i need to interact with Flare EVM as i have for 5 years not sure whats going on
Screenshots
If applicable, add screenshots to help explain your problem.
Desktop (please complete the following information):
Additional context
Add any other context about the problem here.
The text was updated successfully, but these errors were encountered: