-
Notifications
You must be signed in to change notification settings - Fork 62
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-1054] Move Atlantis to Final, Add EIP-684 #134
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Welcome to Atlantis! Thank you everyone for the hard work of pushing this project over the finish line
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
EIP 684 applies retroactively starting from genesis. It should not has a hard fork number, and thus I don't believe it belongs here.
Where would it go? This is an ongoing discussion on ETH - it should definitely be added to the Atlantis META. Similarly it should be added to the Byzantium META |
@GregTheGreek I still don't quite believe that 684 was the impact for the previous Classic Geth bug. The issue is that it shouldn't really affect anything before |
I do agree, I don't think it was the root of the bug. |
@GregTheGreek If we agree that 684 wasn't the cause for any consensus bugs, then I believe my original argument stands. This is something that retroactively applies to genesis, and it does not fit into a Meta ECIP with a hard fork number. However, we should use a separate documentation to note that 684 is in effect. |
I created #142 to address the issue of 684. |
Moves Atlantis to FINAL, closes #67
Adds missing EIP-684, ref ethereum/EIPs#2220 and ethereum/EIPs#2252