With the new Name Wrapper, we will add a new .eth controller that allows registering wrapped names directly as well as registering with multiple records and adding a reverse record in 1 transaction. This will reduce the transactions required from 4 to 2 (for adding records + reverse). This will be added as a controller to the NameWrapper, and the NameWrapper will be added as the new controller of the existing .eth Base Registrar.
We will also replace the current reverse registrar with a new reverse registrar which allows the new controller to set the reverse on registration, as well as adds support for the owner of contract to retrospectively claim their reverse node.
Specification
Prior to this executable proposal the Name Wrapper, new Reverse Registrar, new .eth Controller and new Public Resolver will be deployed. The new .eth controller will be set as the controller of the Name Wrapper. The new Public Resolver will be set as the default resolver on the reverse registrar.
After these actions have been taken, we can do the following calls with this proposal to complete the contract upgrades:
Is there any possibility of users mistakenly sending funds to any new addresses? If so, it would be a good time to implement the capability to get funds back to people (in the future).
After much discussion with rest of the team, we’ve decided to delay the vote for one last code review of the NameWrapper and dependencies. The code review will last this week and we should receive the findings by Monday next week. Once received, I will relay back any findings in the NameWrapper update thread.
Despite my confidence in the code as-is, I don’t think we can ever be overly careful with the next version of the ENS contracts. Lessons within the industry in the recent and distant past have shown time and time again that we are not infallible.
Closing this thread now and have opened a new one with an updated proposal, with a couple small additions to interfaceIds that need to be set by the DAO to allow discovery of the new contracts.
