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.

Sign up for GitHub

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

Jump to bottom

Add native NNS contract #1179

Closed
lock9 opened this issue Oct 22, 2019 · 4 comments
Closed

Add native NNS contract #1179

lock9 opened this issue Oct 22, 2019 · 4 comments
Labels
design Issue state - Feature accepted but the solution requires a design before being implemented feature Type: Large changes or new features ledger Module - The ledger is our 'database', this is used to tag changes about how we store information

Comments

@lock9
Copy link
Contributor

lock9 commented Oct 22, 2019

Summary
We need a way to name addresses and contracts to make the platform more user-friendly.

Do you have any solution you want to propose?
We discussed in NCA to have NNS as a native contract.

Where in the software does this update applies to?

  • Ledger
  • Other: Native Contracts
@lock9 lock9 added the discussion Initial issue state - proposed but not yet accepted label Oct 22, 2019
@lock9 lock9 mentioned this issue Oct 22, 2019
Closed
15 tasks
@shargon
Copy link
Member

shargon commented Oct 22, 2019

Maybe is better to implement the possibily of register protocols, like nash:// , nos:// ... moonlight://

@erikzhang
Copy link
Member

erikzhang commented Oct 22, 2019 •
edited
Loading

nns://

@diskooooo
Copy link
Contributor

nns://

Why not neo://?

NEO is the protocol specification (e.g. HTTP), whereas NNS is the name system (e.g. DNS) and speaks NEO.

@doubiliu
Copy link
Contributor

Maybe determining the adjustment of the economic model is a prerequisite.You know Domain trading depends on GAS. 😂

@lock9 lock9 added ledger Module - The ledger is our 'database', this is used to tag changes about how we store information feature Type: Large changes or new features labels Nov 9, 2019
@lock9 lock9 added design Issue state - Feature accepted but the solution requires a design before being implemented and removed discussion Initial issue state - proposed but not yet accepted labels Nov 17, 2019
@doubiliu doubiliu mentioned this issue Feb 20, 2020
Closed
@roman-khimov roman-khimov mentioned this issue Feb 1, 2021
Closed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
design Issue state - Feature accepted but the solution requires a design before being implemented feature Type: Large changes or new features ledger Module - The ledger is our 'database', this is used to tag changes about how we store information
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
5 participants
@shargon @erikzhang @lock9 @diskooooo @doubiliu