# Setonix: Blockchain-Based Hierarchy Domain Name System for Web3
## 4 Design of Setonix DNS for Supporting Fully Decentralized Web3 Access
### Design Consideration  
The conventional DNS is generally implemented by dividing servers into root, TLD, and SLD, where different parts of each address are stored. Subsequently, queries are called recursively through these servers. Address lookup requests from users are designed to query each server in this recursive manner, sequentially, until the result is returned. The intent behind this implementation is to distribute the load by processing DNS requests across multiple servers rather than a single server. More importantly, it simplifies registration and lookup through an address system separated by dots ('.'). This makes it especially useful for easily verifying ownership in the subdomain part under a domain name.  
For example, in the case of Google's domain, the entity that owns the domain name 'google' connected to the TLD '.com' in 'google.com' naturally holds ownership of the associated subdomains under the current address system rules. This allows them to freely create relevant and useful domain names for their services, such as'map.google.com' or 'drive.google.com'. This means that these subdomains can be created without interference from anyone other than the owner of 'google.com'.  
The address system provided by the DNS proposed in this paper must be designed so that users can transition to and use the Web3-specific address system without experiencing significant load. To achieve this, the system follows the principle of implementing an address format similar to the existing one. This ensures ease of use and management through a hierarchical address structure, even on a blockchain-based platform. However, the SLDs, such as.co,.ac, and.go, come in a wide variety, and there is no consistent rule between domains that include SLDs and those that do not. Therefore, to reduce implementation complexity and enhance manageability, this system defines the basic domain format as \"domain name + TLD\".  
Like the conventional DNS, the DNS implemented on a decentralized system must also guarantee ownership of the domain name to the requester based on the registered domain name. However, due to the characteristics of Web3 and decentralization, where user information is not stored in a specific location, this cannot be conducted in the same way as before. Therefore, to enable this functionality, a smart contract that guarantees ownership will be implemented. Users prove their identity through their wallet address, and once ownership is issued via the ownership contract, they can verify their ownership of the domain name.  
As mentioned in the introduction, since it is not possible to access a DNS uploaded to the blockchain using traditional methods, an interface is also necessary to provide easy access for users. First, this interface must be implemented as a smart contract capable of interacting with the decentralized DNS uploaded to the blockchain network. Second, to maximize user convenience, it must support all types of domain names without requiring any additional transition process on the user's side. In other words, it should support both conventional domain names used to access Web2 services and separate domain names used to access Web3 services. In summary, a hierarchical naming system that offers great convenience in management and usage is designed to function on a blockchain-based decentralized platform. A separate smart contract is used to assign ownership to each decentralized domain name operating within this system. Additionally, to ensure the smooth use of the DNS that supports this address system, the goal is to integrate a proxy-based interaction tool to deliver the result.