-
Notifications
You must be signed in to change notification settings - Fork 5.5k
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
EIP-1014 failed to go through the workflow #1698
Comments
Thank you for the reference. I request please that in future, project managers will promote to LAST CALL and then ACCEPTED status /before/ an EIP will be announced as part of a hard fork. |
Can we close this issue? |
Yes. In future, the cat herders eip monitoring subcommittee will assist here. |
Reference: this happened again on the latest hard fork #2447 This issue is still relevant |
There has been no activity on this issue for two months. It will be closed in a week if no further activity occurs. If you would like to move this EIP forward, please respond to any outstanding feedback or add a comment indicating that you have addressed all required feedback and are ready for a review. |
This issue was closed due to inactivity. If you are still pursuing it, feel free to reopen it and respond to any feedback or request a review in a comment. |
EIP-1014 is currently listed as draft status, however according to announcement from @Souptacular at https://blog.ethereum.org/2019/01/11/ethereum-constantinople-upgrade-announcement/ the latest EF version of clients will support this hard fork on block 7,080,000.
@vbuterin please use the EIP workflow process outlined in EIP-1.
The text was updated successfully, but these errors were encountered: