# Setonix: Blockchain-Based Hierarchy Domain Name System for Web3
## 1 Introduction  
Web3 allows users to own the data generated on the web, involving a shift from the traditional server-client model to a serverless topology [1, 2]. Therefore, Web3 is generally implemented on a well-known decentralized serverless system, which is based on blockchain networks with a high level of security, to support this serverless topology [3, 4]. Currently, Web3 services are offered across various fields, including gaming [5], finance (DeFi) [6, 7], non-fungible token (NFT) marketplaces [8], and decentralized cloud storage [9]. These Web3 services, which are being offered in various sectors like Web2, are considered to have high growth potential due to the advantages of serverless topology and their broad applicability across different fields [10].  
According to [11], the number of papers published on Web3 has increased more than eightfold in recent years. Additionally, based on the data in [12], it is estimated that by 2030, the Web3 market will grow to approximately USD 16 billion in the U.S. alone and around USD 65 billion globally, indicating significant potential for development. However, despite being recognized for its high growth potential and being built on a serverless blockchain network, Web3 faces the contradictory issue of relying on centralized Web2-based pages as access points for services. The reason for this is that there is currently no platform or program capable of directly supporting access to decentralized web services. Even if one wishes to use traditional web access methods, under the current topology, passing through centralized pathways remains inevitable.  
Generally, an essential component in providing users with easy access to web services is the DNS [13]. However, as implied by the term'server', each server has a centralizedstructure with a fixed location. The centralized structure poses a threat to the stability of all Web3.0 services, which are implemented on a blockchain and emphasize decentralization, due to the SPoF issues and potential attack vectors inherent in such a structure [14; 15].  
Furthermore, in this context, the shift to a serverless topology signifies a departure from the traditional method where servers with fixed physical locations had to be rented or owned to provide web services through the server-client model. As the transition to Web3 progresses, the burden of owning fixed servers decreases, allowing anyone to easily create these services, which ultimately suggests that many Web3 services will emerge [16]. With the explosive growth of Web3 services, the existing DNS structure and the number of servers it relies on are insufficient to support access. As mentioned earlier, the fundamental differences in the structure pose challenges for Web3 access via conventional DNS. Even aside from this issue, the servers responsible for handling the exponentially growing load of Web3 services will not only fail to provide an optimal user experience, but also create significant management challenges for DNS operators.  
Here, before formally specifying the problem and proposing a solution, we clarify the terminology to prevent confusion. This helps maintain consistency when referring to blockchain-based DNSs, dedicated domain names, and traditional DNSs like Cloudflare [17] throughout the paper. First, 'conventional domain' refers to domain names like 'google.com' that are commonly in use today. Such domain names are typically served by 'conventional DNS' systems like Cloudflare, but they can also be served by blockchain-based DNSs like Handshake [18], depending on DNS functionality. 'Web3 domain' refers to domain names structured with unconventional TLDs, such as'superdomain.hdns'. These domains can only be served by blockchain-based DNS and not by conventional DNS. Consequently, registration can only take place on blockchain-based DNSs, where these domains are stored.