New ENS App Bug Bash!

[serenae]

1. You can create subnames on unwrapped names as well. When a name is wrapped, technically (from the perspective of the ENS registry / .eth registrar) the Name Wrapper contract is the owner. The NW issues that wrapped NFT to you in return. If you unwrap the name, then that wrapped NFT is burned, and you are returned control (Owner/Manager) over the name in the core ENS contracts.

2. You are only seeing that because on Goerli, there have been multiple revisions to the Name Wrapper contract. So you wrapped your name in an earlier version. However the manager UI only recognizes the current latest revision. There is a guide on unwrapping from old revisions on Goerli here:

Goerli - Unwrapping From Old Name Wrapper

If you had wrapped your name on the Goerli testnet in a previous test deployment of the Name Wrapper, then the v3 alpha manager UI will not allow you to unwrap it. Instead, you will need to unwrap it manually via contract. Hopefully this guide will help. Also see this thread for additional context on the Name Wrapper: NameWrapper updates (including testnet deployment addresses) 1. Determine Wrapper Contract Primary Method - Calling Upgrade 2. Calculate parent nodehash / name bytes 2a. Usi…

3. When you perform the commit transaction, that is good for 7 days. But it does not reserve the name for you. If you have performed the commit but not the final register tx, then someone else can register the name before you. However, the commit transaction does not reveal what name you are registering, as it’s only a hash value on-chain. FYI none of this has changed with the new contracts, that’s how it currently works today as well. I agree that the current language “prevents others from registering this name before you do” can be misleading.