Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Minimal namespace implementation (spike) #972

Closed
7 tasks done
husio opened this issue Aug 16, 2019 · 1 comment
Closed
7 tasks done

Minimal namespace implementation (spike) #972

husio opened this issue Aug 16, 2019 · 1 comment
Assignees
Milestone

Comments

@husio
Copy link
Contributor

husio commented Aug 16, 2019

As a user, I want to be able to register a custom namespace in bns, so that I can provide human readable blockchain address aliases to my customers under my own brand name (i.e. *evilcorp).

The new namespace specification was written - IOV Namespace Technical Specification. This issue is about the minimal implementation of the namespace functionality. Adding less crucial events or attributes can be done in separate issues.

Acceptance criteria

  • A user must be able to register a namespace using provided label,
    • a label must be at least 1 character long
    • a label cannot be longer than 16 characters
    • a label can be made of the following characters abcdefghijklmnopqrstuvwxyz0123456789-_
    • once created, a namespace label must not be changed
  • A namespace label must be unique - no two namespaces can have the same label,
  • When a namespace is created, the transaction main signer becomes the new namespace owner,

Non goals

  • namespace expiration, freezing, unregistration
  • referencing a blockchain address with a namespace
  • namespace queries
  • any username related functionality
@husio husio added this to the Namespace 🦄 milestone Aug 16, 2019
@husio husio changed the title Implement namespace functionality Minimal namespace implementation Aug 16, 2019
@kmw101 kmw101 changed the title Minimal namespace implementation Minimal namespace implementation [ SPIKE ] Aug 20, 2019
@husio husio self-assigned this Aug 26, 2019
@husio husio changed the title Minimal namespace implementation [ SPIKE ] Minimal namespace implementation (spike) Aug 26, 2019
husio added a commit that referenced this issue Aug 26, 2019
Update the existing username implementation and add the username entity.
With this change any number of namespaces can be registered. Each
username must be registered within an existing namespace.

resolve #972 and #973
husio added a commit that referenced this issue Aug 26, 2019
Update the existing username implementation and add the username entity.
With this change any number of namespaces can be registered. Each
username must be registered within an existing namespace.

resolve #972 and #973
husio added a commit that referenced this issue Aug 26, 2019
Update the existing username implementation and add the username entity.
With this change any number of namespaces can be registered. Each
username must be registered within an existing namespace.

resolve #972 and #973
husio added a commit that referenced this issue Oct 21, 2019
Update the existing username implementation and add the username entity.
With this change any number of namespaces can be registered. Each
username must be registered within an existing namespace.

resolve #972 and #973
@husio
Copy link
Contributor Author

husio commented Oct 21, 2019

Specification has changed and new issues are created.

@husio husio closed this as completed Oct 21, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant