I’m in favor of this proposal.
I don’t share at all the reverence for immutability regarding DAOs and dApps. For sure, we need it for the base layer. It doesn’t mean that it automatically translates to any collective decision.
The whole point of governance tokens, forums, and votes is to empower the community to make decisions. About everything, and as the community see fits. The last time I checked (and I just checked again), Immutability is not part of the core principles approved in the ENS constitution. Why should it become a reason to do or not to do certain things now?
If there have been obvious mistakes that cost members their tokens and that we can fix without occurring much effort nor cost as a community, why shouldn’t we do it, if it’s not out of respect for a principle that we haven’t approved in the first place?
I hear that there’s the risk of creating a precedent. Yes, if this proposal makes sense now, it could happen again - and what’s wrong with that? If it happens again but the then-conditions make it irrelevant or too costly or detrimental to the project, we can and will downvote it then. We don’t have a jurisprudential system that forces us to comply with our previous judgments. If we vote yes, we won’t have to help users every time they make a mistake, just as voting any proposal won’t necessarily create an enforceable precedent.
I like the last idea of @AvsA regarding charging a fee that will be used to pay for the implementation, though.
I will vote YES - just need to wait for feedback from my delegators first.