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
ECIP-1056: Agharta EVM and Protocol Upgrades #131
Comments
Hi core dev team, I was wondering if there are any technical chats between yourselves about it and if Agharta changes are good. e.g.: Via EIP-1702 new account version:
Is all generally ok with eip-1702, 145, 1014 and 1052? Or are there disagreements that will be sorted out after Atlantis? |
yes, all four EIPs make a lot of sense. We should not get distracted now though and focus on Atlantis. Will organize calls after Atlantis |
I highly suggest we name the hardfork Agartha instead of Agharta. Agharta is a Miles Davis album: https://www.youtube.com/watch?v=crpJgZxqMcg Agartha is the Hollow Earth kingdom: https://en.wikipedia.org/wiki/Agartha |
Im not sure its been mentioned, but this would make anyone looking to develop a new EVM would need to implement all previous versions as well. That being said, we must be prudent to ensure that changes are very well documented, and the implementation of each version can be replicated by following this documentation with relative ease. We should hold off on including this ECIP until the following are very well defined: What will be the canonical model for describing the EVM |
what specifically are you referring to? |
@BelfordZ When I asked more about EVM versioning on ETH All Core Devs, it was clear that there were two different "levels" of versioning which we need to model:
|
@soc1c I was referring to the implicit use of EIP-1702, which has since been removed. Please dismiss above comment. |
Please can an ECIP Editor close this issue? Agharta is shipped. Thanks! |
Thanks, @soc1c |
No description provided.
The text was updated successfully, but these errors were encountered: