Account Name Service

[ilblackdragon]

Implement Account Name Service: system that defines how new accounts can be called.

High level design:

• To register Top Level Name: ".near", ".com", etc - you need to burn some number of NEAR tokens (the shorter the name, more tokens it costs).
• Any account can create sub-accounts that are prefixed by this account. E.g. account "gmail.com" can create "blah@gmail.com" or "blah.gmail.com".

[eriktrautman]

Adding comments from on-desk chat yesterday.

Re: TLDs Basically, making a full with-TLD name the default (eg foo.near) seems like bad UX since users will always be redundantly typing the .near part. I get that we're trying to allow TLD registrars to set up specific criteria for handling all names that are registered within their namespace so they can defend against squatting on legitimate names (eg Google may want to register the .google TLD and guarantee that each sub address matches to a gmail account ((ok, ignore that we may violate the dot-naming convention here))). But users will hate it... and we're in a virtual world that's been comfortable for a long time with using handles and acknowledging that a handle doesn't always correspond to that person (eg a celebrity)'s real identity. So let's just make normal handles without . the default, ignoring squatting issues, and use the . TLDs to denote specific registrars who can have their own state criteria.

Re: Protected keywords Seems like the easiest / not-overengineered solution to reserving keywords is just hardcoding an index of blacklisted usernames like admin near etc.

[evgenykuzyakov]

@eriktrautman So basically . would be a restricted character in the account ID. And it can only be used with domain-style names. Is it correct?

[eriktrautman]

Sounds accurate. So ‘foobar’ is valid but ‘foo.bar’ is only valid if the bar issuing authority is the one issuing it. Same for *.near and the near issuing authority.

On Thu, Jun 6, 2019 at 10:29 AM Evgeny Kuzyakov ***@***.***> wrote: @eriktrautman <https://github.com/eriktrautman> So basically . would be a restricted character in the account ID. And it can only be used with domain-style names. Is it correct? — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#968>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AAWW5HXVT44ZVCVB6J2TJGDPZFCQ5ANCNFSM4HPWBTWA> .

-- — Erik S. Trautman Building a scalable, mobile-first blockchain at NEAR Writing | LinkedIn | Twitter

[evgenykuzyakov]

Implemented