-
Notifications
You must be signed in to change notification settings - Fork 37
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
Call for Input: Mark 7212 as "Moved" #345
Comments
I am in favour of merging this pull request. |
I would prefer Withdrawn rather than a one off status of Moved. But am not opposed to merging. (but don't have a vote) Move means copy and delete, so ideally we would delete (completely remove) the EIP but there are already references to it (such as https://eips.ethereum.org/EIPS/eip-7600). In future, moving an EIP to a RIP, we should issue the RIP a new number and set the EIP to Withdrawn, rather than creating another state to maintain. |
IMO, EIP-7212 should be treated the same way as ERCs when EIPs GitHub repo was forked. We can use the same process for RIP-7212 because when moved it carried the number which was allocated to an EIP. |
As the co-author of EIP/RIP-7212, I support merging this PR and bring 'Moved' status for the original EIP. I agree that it's a similar situation with ERCs and this necessity has been mentioned in the first RollCalls. This action will resolve recent confusion around the 7212 proposal and opens the space for L1 to directly implements an RIP or make changes by a new EIP if required. |
I think we should delete it |
+1 for delete |
Delete is fine by me. |
@SamWilsn deadline is August 2 (today in Australia). 3 votes for delete. Would be good to get this resolved (regret not renumbering the RIP). |
Consensus is to delete. |
Call for Input
Do we merge ethereum/EIPs#8101 ?
EIP-7212 is marked as "Moved", an unusual status.
Pull request is not merged, and 7212 remains both an EIP and an RIP.
Rough Consensus
August 2, 2024
Checklist
I, the opener of this Call for Input, have completed the following:
The text was updated successfully, but these errors were encountered: