PREVENTING NAME SQUATTING:

I think the best way to do this is to make usernames separate from keys and verification of a key owner's identity more valuable then usage of a username.

1. Duplicates of usernames are ALLOWED (they are not currently)
2. Duplicates of keys are prohibited (as it is now)

3. Anyone can create multiple copies of the username GOOGLE, but only one GOOGLE can be verified, and that verification lives on-chain.
4. Verification is by Associations (as planned, or another method decided by the current stakeholders)

5. Nodes can choose to:
a. only display Verified usernames in searches
b. allow a toggle for showing unverified usernames in searches
c. display a badge for verified usernames

ETH ERC20 tokens, Cardano tokens, and WAVES tokens all allow unlimited duplicate names specifically to prevent name-squatting.

And here are some resources about this:

ERC20:
ethereum.stackexchange.com/questions/24725/are-erc20-token-names-unique

Cardano:
forum.cardano.org/t/unique-token-name/51301

WAVES:
github.com/wavesplatform/waves-documentation/blob/master/en/waves-client/assets-management/issue-an-asset.md

Microsoft XBOX method:
thesun.co.uk/tech/9268049/xbox-gamertag-change-any-name-free/amp

And an overview of options from one of the smartest people in Blockchain (he doesn't mention allowing duplicates for some reason?)
medium.com/edenoneos/how-to-prevent-name-squatting-d35796cded35

What do you think about allowing unlimited duplicate names?

🕉️☀️💜🙏

@nader @AlexValaitis @salilsethi

#usernames #abuse #dev #developers

Posted via @cloutfeed