You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
At present, we already have xxx.walrus.site, which is used to provide content service websites.
But this is still not perfect. First of all, its suffix is long, and unfamiliar users may not associate the name walrus with sui.
If you register the .sui root domain name and keep it synchronized with the NS information on the chain, then:
Shorter URL and strong correlation with SUI
Turn the WEB3 domain name into a real domain name, which can be directly entered in the browser website bar for access, which is currently not done by all other public chains
Improve the product strength of SUI-NS. If we really do this, it is also in line with SUI's purpose of "migrating users from WEB2 to WEB3"
At present, walrus only provides content access services and does not have the function of setting DNS resolution. If we complete this function, then imagine that we can use majoson.sui as an email address?
If SUI officials are willing to register the .sui root domain name, we are willing to contribute related functions, including:
dns resolution server
User settings interface
Logic bound to NS or walrus
This must be a great feature, looking forward to your reply!
The text was updated successfully, but these errors were encountered:
At present, we already have xxx.walrus.site, which is used to provide content service websites.
But this is still not perfect. First of all, its suffix is long, and unfamiliar users may not associate the name walrus with sui.
If you register the .sui root domain name and keep it synchronized with the NS information on the chain, then:
majoson.sui
as an email address?If SUI officials are willing to register the
.sui
root domain name, we are willing to contribute related functions, including:This must be a great feature, looking forward to your reply!
The text was updated successfully, but these errors were encountered: