Call for Input: Modify ERC-6492 Reference Implementation

[SamWilsn]

Call for Input

Decision	Do we merge ethereum/ERCs#878 ?
If Affirmed	ethereum/ERCs#878 is merged.
If Rejected	No change
Method	Rough Consensus
Deadline	March 21st , 2025

Background

This pull request modifies the reference implementation in ERC-6472 to prevent an attack.

Checklist

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

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

[SamWilsn]

opposed

---

Based on precedent (ERC-20 & ERC-223), I don't think we should modify the final ERC. That said, I am extremely open to ideas on how to handle security disclosures moving forward.

[frangio]

More precedent here: #291

As I expressed then, I believe this kind of change should be accepted. Here are the options I proposed:

Depending on how strict we want to be about immutability we can choose from a range of options:

1. Simply add a "RETRACTED" message at the top of the reference implementation section.
2. Delete the reference implementation section and replace it with "[RETRACTED]".
3. Delete it, and leave a message explaining the reasons it was retracted.

[SamWilsn]

From EIPIP today, @g11tech is also opposed.