Call for Input: Mark 7212 as "Moved"

[SamWilsn]

Call for Input

Decision	Do we merge https://github.com/ethereum/EIPs/pull/8101 ?
If Affirmed	EIP-7212 is marked as "Moved", an unusual status.
If Rejected	Pull request is not merged, and 7212 remains both an EIP and an RIP.
Method	Rough Consensus
Deadline	August 2, 2024

Checklist

I, the opener of this Call for Input, have completed the following:

• [x] Filled in a descriptive title.
• [x] Filled in the "Decision" field.
• [x] Filled in the "If Affirmed" field.
• [x] Filled in the "If Rejected" field.
• [x] Filled in the "Method" field.
• [x] Filled in the "Deadline" field to be thirty days from creation.
• [x] Added any relevant background information (or removed the section.)
• [x] Published a notice in writing to the usual channels frequented by EIP Editors (likely Discord.)
• [x] Commented on this Call for Input, clearly stating my opinion (or abstention.)

[SamWilsn]

I am in favour of merging this pull request.

[abcoathup]

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.

[poojaranjan]

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.

[poojaranjan]

EIP-7212 was also discussed in the ACDE meeting as it is being considered for the Pectra upgrade. Adding screenshots of suggestions that surfaced.

[ulerdogan]

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.