This EIP seems to be missing some details that should be considered:
- Doesn’t specify whether
SENDALLshould halt execution likeSELFDESTRUCTdoes - Whether the gas cost should be adjusted
- Providing an alternative for replacing code at a given address
- Plans for backwards compatibility beyond “get rekd”
The last I find is specifically important. As a platform for building immutable, composeable dApps breaking some functionality which some projects seem to critically rely on sets a bad precedent. There is some small precedent for mutating contracts via social consensus (DAO hack) but the circumstances were very different there.
Beyond harming users of such dApps it would encourage more immutability and upgradeability as devs may want to ensure that they can fix their protocol should the protocol choose to one day break it.