[Wanchain] Week 4 WNS Update
Last week, we talked about how WNS (Wanchain Name Service) will interact with Wanchain 3.0 Alpha testnet (read week 3 update). This week, we will discuss the components we considered for deploying WNS.
In order to ensure WNS could work flawlessly within the Wanchain ecosystem, 3 major components were taken into consideration in deploying the Wanchain Name Service:
- Registry
- Registrar
- Resolver
A Registry maintains a list of WNS related information, such as the owner of the domain, a resolver address, and a time-to-live (TTL) integer value.The owner may be either a user or a smart contract, and they are acceptable to:
- Set the resolver and TTL for the domain
- Transfer the ownership of a domain
- Change the ownership of subdomains
The Wanchain registry is deliberately straightforward and exists only to map from a name to the resolver responsible for it.
A registrar is responsible for allocating new names to users through customized trading rules. Rules are implemented to prevent monopoly in the WNS market.
First of all, users can’t bid domain less than six characters. Secondly, an 8-week lock-up period limits the availability of WNS once deployed, to give people time and space for adoption and to prevent any single entity to dominate the WNS market. Thirdly, the auction opens for bidders to join in the first three days and closes for the last two days. Bidders should come back and reveal their bids. The unrevealed bid will not be entitled to the domain acquisition. Lastly, every interaction (bid, buy, sell) will result in the transaction fees. The smart contract could be designed accordingly to compromise the need of Wanchain, hence fees could be either burned, incentivize the contract creator or contribute back to the Wanchain community.
A resolver tells users the resource associated with a name, for instance, a Wanchain wallet address, or an IPFS content hash. There are some public resolvers that anyone can point their domains at and use.
The diagram below explains the procedure behind purchasing and resolving the WNS.
User will purchase a WNS through the registrar, which will request a new name to the registry. Once the purchase is confirm, user can claim their name from the registrar. If the user wants to access decentralized service through Wanchain domain name, the resolver will query the name to registry, which will return the corresponding address or alphanumeric hash and its content to the user, just like how DNS resolves domains into IP addresses to find the correct content for its users.
Community Contribution
Last but not least, we would like to share our WNS Github repo here. Feel free to create an issue for any suggestion or bugs. We value communities’ contribution so any feedback will be highly appreciated.
Thank you for reading.
Stay tuned by joining Portal Network’s Channels.
Social Media: Telegram | Reddit | Twitter | Facebook | Github |Websites & Products: Official Website | FORUM | MUMEI | KAIZEN |
