It has come to our attention that the implementation of ENS usernames in the current RC for V1 status app allows for registration of ENS usernames that are the list that the original ENS Dapp forbade.
As this is not pivotal to launching V1, I wanted to capture the majority of the conversation to shelve for after launch.
There have been a few solutions, namely:
- remove the list entirely, enable any registration that conforms to current in-app registration criteria (alphanumeric). Broadcast that anything that is a subdomain of
stateofus.ethwill never be an official channel of Status, and shouldn’t be treated as such. This can be extended to say that anything officcial will come from
status.ethand we can have in-app branding on anything with that to reinforce it (this could be a neat thing for Status CCs, tbh).
- widdle down the list to be smaller, and increase the in-app criteria to not allow names within that list. This list would be as minimal as possible, and only pertain to Status related things, not various other entities that are currently within the list.
- implement the list as is in the app, as the original ENS username Dapp had done, increase the UX of slashing so that people can see when a name is being used, and slash it easily.
My personal thoughts for now:
- If we keep the ability to slash, regardless of what is available to be slashed, then a dapp for slashing names easily should be created, and a portal to it should be easily available within the Status app.
- I am reticent to make very large changes to audited contracts without a formal review of the changes.
- In the name of decentralization and continuance, I am in favor of doing things that require the least amount of “policing” and bias from us, especially in terms of long term maintenance. The community should be in charge of this, and things should be able to exist without the existence of the status organization.