# Setonix: Blockchain-Based Hierarchy Domain Name System for Web3
## 6 Experimental Results
Additionally, the inherent lower performance of Handshake means that even relatively minor issues, such as an additional hop introduced by the proxy, can significantly increase latency. Figure 7 is a graph comparing the resolving latency of two types of domain names in blockchain-based DNSs: Handshake and Setonix. The experiment was conducted in the same way as in Figure 6, using 100 domains of each DNS type, and the results show the average resolving latency for each individual request. All resolving tools used Setonix's proxy-based interface, and for Handshake, the internal custom resolver of the tool was pointed to the Handshake DNS. Figure 7: The difference in resolving latency for conventional domain names and internal Web3 domain names was measured for both Setonix and the blockchain-based DNS Handshake. Error bars indicate the maximum and minimum values for the average of each dataset. The results show that Setonix is overwhelmingly superior to Handshake for both conventional and Web3 domain names. This aligns with the analysis of Figure 6, where Handshake's comparatively high latency was attributed to its operation on a PoW-based system with significantly slower TPS and its complex internal implementation. It can also be observed that Web3 domain names have over 15% lower latency compared to conventional domain names. This is because Web3 domains are uploaded to the internal blockchain and can be resolved immediately, whereas conventional domains must go through multiple steps, such as the TLD and SLD, via the internally implemented root zone. In contrast, Setonix shows no significant difference between Web3 domain names and conventional domain names due to its simpler internal implementation and the efficient domain classification by the protocol checker. Figure 8 is a graph that allows a side-by-side comparison of the latency of Web3 domain names from three blockchain-based DNSs, ENS, Handshake, and Setonix, with two conventional DNSs. The experiment was conducted in the same manner as before, using a cache flush method. Since ENS does not allow resolution through resolvers that do not follow its Web3 query rules, the test was conducted with 100 pre-selected ENS domain names according to these rules. As with Setonix and Google, the data represent the average values. As seen in the chart, ENS shows the worst latency, even slower than Handshake. This is because ENS has a similarly complex internal implementation as Handshake and also uses a more complicated method of exchanging data, relying solely on its Web3 query system instead of the standard DNS approach. Additionally, unlike conventional DNSs, which can optimize the path to the DNS server through methods like CDN or Anycast, ENS cannot use such methods. This further contributes to its lower performance. In contrast, Setonix shows latency comparable to Cloudflare even for its Web3 domains. This result is due to its simple internal components, efficient hierarchy processing methods, and the combination of a well-designed interface. In Figure 9, caching is allowed, and to demonstrate the effects of caching, the graph shows how latency changes over successive attempts, unlike the previous experiment. Each time represents the result of resolving 100 different domain names, as in the previous experiment. The key difference here is that instead of showing the average values, the full  
Figure 8: Resolving latency for each DNS: Web3 domain names for blockchain-based DNSs like ‘superdomain.hdns’ and conventional domain names for conventional DNSs like ‘google.com’. Error bars indicate the maximum and minimum values for the average of each dataset. set of 100 attempts is displayed to illustrate the change in latency over time. Note that the vertical axis is in seconds. As can be seen from the legend in Figure 9, the dashed line represents the results of resolving through Setonix's proxy-based interface, while circles represent Google DNS, triangles represent Cloudflare, and squares represent Handshake.