-
Notifications
You must be signed in to change notification settings - Fork 118
Neo Address Resolution #133
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
Merged
Merged
Changes from all commits
Commits
Show all changes
3 commits
Select commit
Hold shift + click to select a range
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,47 @@ | ||
<pre> | ||
NEP: 18 | ||
Title: Neo Address Resolution | ||
Author: Erik Zhang <[email protected]> | ||
Type: Standard | ||
Status: Accepted | ||
Created: 2021-02-13 | ||
</pre> | ||
|
||
==Abstract== | ||
|
||
This NEP describes a standard for storing Neo addresses in TXT records. | ||
The wallet and client should use the method described in this NEP to store and resolve the TXT record of the domain name, so that users can use the NNS domain name to transfer assets or use dapps. | ||
|
||
==Motivation== | ||
|
||
NNS currently provides regular DNS service to allow users to add A, CNAME, TXT and AAAA records for domain names. | ||
However, we do not provide direct support for Neo addresses in NNS. | ||
We need a way to map domain names in NNS to Neo addresses to support complex application scenarios. | ||
|
||
==Specification== | ||
|
||
[https://tools.ietf.org/html/rfc1464 RFC 1464] describes the general syntax of a TXT attribute: | ||
|
||
<pre> | ||
"<attribute name>=<attribute value>" | ||
</pre> | ||
|
||
We use <code>address</code> as the attribute name of the Neo address: | ||
|
||
<pre> | ||
"address=<Neo address>" | ||
</pre> | ||
|
||
The following TXT record map the domain name to the Neo address <code>NUVPACMnKFhpuHjsRjhUvXz1XhqfGZYVtY</code>: | ||
|
||
<pre> | ||
"address=NUVPACMnKFhpuHjsRjhUvXz1XhqfGZYVtY" | ||
</pre> | ||
|
||
==Rationale== | ||
|
||
A dapp can add a Neo address to its domain name to allow users to send assets, or allow the front end to use the domain name to call the contract. | ||
|
||
The user can set a domain name for his address, so that his transaction party is difficult to be deceived by a fake address, and it can also reduce the chance of wrong transfer. | ||
|
||
==Implementation== |
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Uh oh!
There was an error while loading. Please reload this page.