-
Notifications
You must be signed in to change notification settings - Fork 1.2k
EVM Map Patch update #6520
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
EVM Map Patch update #6520
Conversation
✅ Deploy Preview for reliable-cocada-166884 ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
|
This update has fixed the problem for me. The logic should be that deployment to all chains are allowed to use the default VM - (now at Prague). If a chain contacts us, we can limit that that chain's EVM maximum fork - but it will be up to them to get back to us to tell us that they have made an update. Although they will likely forget to contact us again to bring them up to date. for a little history: evmmap.tx was originally done for Celo Mainnet which was not up to the latest EVM. So we limited it. They have been up to date for some time now. |
|
why did you comment out everything? |
f28a0a0 to
905646e
Compare
|
@joeizang - can you respond to Yann? The reason is because when a chain is listed it limits that chain to the specified EVM. But we need to remove all the limitations and only add them when the chain contacts us. Probably for merging the commented lines can be removed - unless there is a reason to keep them commented out. Also Mainnet could be removed from all of the EVMs because it will be always up to date with the latest (by definition). |
|
View your CI Pipeline Execution ↗ for commit 243fdf1
☁️ Nx Cloud last updated this comment at |
|
❌ E2E failures detected (workflow: web) Last run: Wed, Nov 12, 2025, 08:06 AM UTC Top failing tests (1/1):
Report generated by CI; artifacts are retained per CircleCI retention settings. |
4371571 to
243fdf1
Compare
fixes #6518