# Setonix: Blockchain-Based Hierarchy Domain Name System for Web3
## 6 Experimental Results  
In this section, the hierarchical structure of Setonix is uploaded to the actual blockchain, and a comparison is made with other DNSs and blockchain-based DNSs through the proxy interface. The blockchain used was the Sepolia network, which is Ethereum's testnet, and the user (or machine) sending the requests through the installed proxy interface used a Windows OS PC for compatibility. The detailed specifications of the PC are a 13 th Gen Intel(r) Core(tm) i9-13900 CPU, 64 GB RAM, Realtek Gaming 2.5 GbE Family Controller #2 NIC, and a 1 Gbps bandwidth network. Domain registration on the Sepolia Testnet incurred a cost of approximately USD 0.5 for registering a single domain name, as no additional fees were required by policy. While this cost may vary slightly depending on the type of network, congestion, or the length of the domain name, it is significantly more affordable compared to other systems. For instance, ENS requires an annual fee of USD 640 plus additional network fees for domains of 3-character length, and Handshake DNS transactions typically average around USD 20 but can vary widely based on rarity [28]. The experiment first evaluated three DNSs: Google and Cloudflare as representative traditional DNSs, and Handshake as a blockchain-based DNS capable of resolving traditional domain names. The most noticeable aspect for users when using DNSs is the latency during resolving to access services. Therefore, resolving latency was chosen as a key test parameter and measured accordingly. In Figure 6, the graph on the left shows the results of resolving domain names using the local resolver on a Windows PC, while the graph on the right shows the latency when resolving each DNS through the custom resolver within the proposed proxy-based interface. The resolving latency measurement experiment was conducted through the following design and process:  
* Domain selection: The top 100 resolvable domains were chosen using Cloudflare's top 1 M websites list. * The resolving process compared two methods for each DNS: the Original Resolver method and the Setonix Interface method, which includes the resolver function. In the Original Resolver method, a local resolver was used to resolve domain names. In con  
Figure 6: This represents the latency differences when resolving through the Original Resolver and Setonix’s proxy-based interface for each DNS. Each error bar indicates the maximum and minimum values for the corresponding data. trast, the Setonix Interface method employed a proxy-based interface specifically designed for Setonix to resolve domain names. * Experiment process: Resolving was performed randomly without duplication for the top 100 prepared domain names. After resolving each of the 100 domains once in a single experiment, the cache was flushed. This process was repeated 20 times to obtain sufficient data. * Data processing: The data obtained through the experiment process were aggregated for each item and divided by 20 to calculate the average. Finally, the result was divided by 100 to derive the average resolving time per attempt. First, both Google and Cloudflare, the two conventional DNSs, showed an average latency of less than 50 ms for each resolving request. In contrast, the blockchain-based Handshake DNS showed a relatively higher latency, averaging over 200 ms. However, more significantly, in the case of Handshake, which uses a PoW-based consensus algorithm, it appears that the inherent TPS (Transactions Per Second) limitations of this algorithm have had a greater impact. Additionally, for conventional DNS, there was no significant difference in latency between using the local resolver and passing through the proxy. However, a notable difference was observed in Handshake, which operates on a blockchain basis. This can be interpreted as the result of Handshake, which was created by a smaller community compared to established DNSs, being optimized for requests made through the more commonly used local resolvers rather than for those using open-sourced customized DNS tools.