NameWrapper updates (including testnet deployment addresses)

[jefflau.eth]

@hodl.esf.eth This has now been deployed to testnet. I’ve updated the addresses above.

[hodl.esf.eth]

Thanks Jeff…

Can you verify the contracts on Etherscan?

[jefflau.eth]

Contracts are now verified!

[jefflau.eth]

I’ve just post the draft executable proposal to the forum: [Draft] [Executable] Activate new .eth controller and new Reverse Registrar

[serenae]

If you wrapped any names in a previous deployment of the Name Wrapper, and you want to unwrap them, see this guide: Goerli - Unwrapping From Old Name Wrapper

[jefflau.eth]

[Draft] [Executable] Activate new .eth controller and new Reverse Registrar

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 …

[danielseo]

Any updates or expected date for mainnet deploy?

[garypalmerjr]

(It is literally the last message before you posted.)
This will go to vote on Monday,
…then voting period is seven days.

[hodl.esf.eth]

I don’t think so… Vote is delayed for one last review of the code and should get findings back next Monday. Date of vote will probably be discussed then.

[nick.eth]

The NameWrapper, and new versions of the PublicResolver, ETHRegistrarController, and ReverseRegistrar have all been deployed to mainnet. Addresses of these new contracts can be found here: Mainnet deploy of new contracts by Arachnid · Pull Request #236 · ensdomains/ens-contracts · GitHub

They will not be active until the DAO approves a vote to activate them. This will be forthcoming shortly, after the ENS team verifies the deployment.

Edit: We’ve identified a misconfiguration in the original deployment. I’ve redeployed and the team is verifying the new version.

[meta8.eth]

Congratulations everybody!

[wolfram]

Hey Nick, is it mandatory for platforms to subscribe to the new contracts or can it still use the (now) old registry/controller/registrar/resolvers in parallel?

[nick.eth]

The old .eth registrar controller will remain usable until deprecated (separately); there’s no rush to do that as it still works just fine. Users can use the old resolvers just fine, though they won’t be able to use them with wrapped names.

We’re not upgrading the registry or .eth registrar (in fact, they’re not upgradeable).

The new reverse registrar will need to be used immediately; only one registrar can exist at a time.

[3531]

woohoo!

[hodl.esf.eth]

Great news on the mainnet deployments. Congratulations to the team.

I was wondering if before the voting commenced there would also be some visibility of the changes to the metadata of namewrapper. This seems like a very important detail as it contains information across all the marketplaces / dapps for the state of the names, permissions, expiries etc.

Metadata does not seem to be working currently on Goerli.

---

Also, I know it would require another deployment but I would consider adding in events for eip-4906 Metadata Update Extension so when there is any changes to expiry / fuses the marketplaces can pick them up without a manual refresh of metadata.

[jefflau.eth]

Vote is now up! Tally | ENS Proposal

Updating above addresses to include mainnet deployments

[serenae]

I think the metadata service has yet to be updated, I believe @mdt is working on that.

See this PR for an example of what will be added to the metadata: add namewrapper specific traits to the metadata by mdtanrikulu · Pull Request #150 · ensdomains/ens-metadata-service · GitHub

• Namewrapper State (string)
  • Wrapped | Emancipated | Locked
• Namewrapper Expiry Date (date)
• Namewrapper Fuse States (object)
  • Boolean true|false for every individual fuse/permission

[hodl.esf.eth]

Thanks for the reply.

Shouldn’t this be completed before the voting starts? No-one actually know what this is going to look like on opensea / looksrare until it is finished and working on goerli.

Is there going to be enough time to complete and test it before the deployment datetime?

Also, have you considered implementing eip-4906?

[serenae]

Well, wrapped names will be a new contract, so new collection I believe on most platforms.

OpenSea and most other places will just show those two new state/expiry traits, for wrapped names.

OpenSea and most other places will likely not show anything for the individual fuse states, as that is a complex object and not just a string/date/number. However, perhaps other platforms more in tune with ENS could show extra information, like ENS.Vision.

EIP-4906 probably doesn’t make sense as the ENS metadata service is not on-chain at all. It is a separate service run by ENS Labs Actually, see below

[hodl.esf.eth]

eip-4906 event tells the marketplace there has been a change and to pull the metadata again from whichever the uri is, (onchain / ipfs / centralised). If a fuse is burned then markets won’t update unless the metadata is manually refreshed.