Blockchain technology can address data falsification, single point of failure (SPOF), and DDoS attacks on centralized services. By utilizing IoT devices as blockchain nodes, it is possible to solve the problem that it is difficult to ensure the integrity of data generated by using current IoT devices. However, as the amount of data generated by IoT devices increases, scalability issues are inevitable. As a result, large amounts of data are managed on external cloud storage or distributed file storage. However, this has the disadvantage of being outside the blockchain network. This makes it difficult to ensure reliability and causes high latency during data download and upload. To address these limitations, we propose a method for managing large amounts of data in the local storage node of a blockchain network with improved latency and reliability. Each blockchain network node stores data, which is synchronized and recovered based on reaching a consensus between smart contracts in a cluster network. The cluster network consists of a service leader node that serves as a gateway for services and a cluster node that stores service data in storage. The blockchain network stores synchronization and recovery metadata created in the cluster network. In addition, we showed that the performance of smart contract execution, network transmission, and metadata generation, which are elements of the proposed consensus process, is not significantly affected. In addition, we built a service leader node and a cluster node by implementing the proposed structure. We compared the performance (latency) of IoT devices when they utilized the proposed architecture and existing external distributed storage. Our results show improvements up to 4 and 10 times reduction in data upload (store) and download latency, respectively.

The blockchain market has been experiencing rapid growth recently. Alongside this, Web3 services based on blockchain technology are expanding and gaining attention. These services can support not only encompass gaming and financial services but also leverage the numerous nodes existing in the network to distribute tasks, thereby supporting parallel computing. However, there is no way to directly access web3 services in the current network topology, which limits the expansion of services. Therefore, the current Web3 relies on centralized web servers as access points for services, resulting in the inevitable loss of benefits associated with decentralization, such as the shift in data sovereignty. In addition, the current Domain Name System(DNS) is managed by a single entity, ICANN. Such centralized management by a single entity includes a structural risk of potentially leading to monopolistic control by the institution in the future. To eliminate potential threats and enable direct access to web3, decentralized DNS can be considered. This approach can effectively mitigate the risk of monopolistic control by distributing authority through its structure. Additionally, It also ensures that the benefits of decentralization such as information ownership transfer are fully realized without the loss associated with the use of centralized access points. Therefore, this paper examines the existing implementations of decentralized DNS and proposes various interface designs to enable users to use these systems in a universal manner across different scenarios. After implementing these interfaces, we discuss their characteristics and the situations in which they are most effective. Additionally, we verified that accessing services through the implemented interfaces shows no significant time difference compared to accessing web2 via traditional DNS. Through these proposals and discussions, we aim to propose general criteria for interfaces that can be used with decentralized DNS.

DNS is an essential component for internet access, but the traditional centralized structure is not suitable for the rapidly growing Web3 ecosystem. Currently, Web3 services rely on Web2-based access paths, revealing limitations such as the Single Point of Failure (SPoF) issue and the compromise of decentralization principles. To address these issues, this paper proposes Setonix, a blockchain-based decentralized DNS. Experimental results of the implemented Setonix showed that it had only a marginal performance difference of up to approximately 5% compared to Google and Cloudflare DNS. Additionally, it demonstrated over 95% lower latency compared to Handshake DNS, proving its high efficiency. Setonix eliminates dependency on centralized access paths and brings the hierarchical address structure of existing domain names into the blockchain network, adhering to legacy systems to minimize user resistance. Additionally, it provides a blockchain-based architecture that supports cross-compatibility between traditional domain names and Web3 domain names through a simple interface. This design significantly enhances the scalability and accessibility of Web3, presenting a new standard for decentralized internet services. By doing so, it helps to establish a foundation that contributes to the growth and innovation of the Web3 ecosystem.

Although DNS has been continuously extended to improve usability and security, its centralized, server-based architecture leaves fundamental limitations unresolved, including single points of failure (SPOF), susceptibility to censorship, and exposure to DDoS. This study examines blockchain-based DNS (BDNS) as an alternative proposed to mitigate these structural issues. We first synthesize prior research and systems on BDNS, and then conduct a comparative analysis using practical deployability as the primary criterion. Specifically, we selected seven representative BDNS projects, including Namecoin, Handshake, and Ethereum Name Service (ENS), and evaluated them under a common set of criteria: (i) the record model, finality, and TTL semantics; (ii) friction along real resolution paths involving resolvers, browsers, and gateways; and (iii) interoperability with the legacy DNS, including DNSSEC and DNS over TLS(DoT)/DNS over HTTPS(DoH), together with migration scenarios. The analysis indicates that many systems rely on gateways and client-side extensions, limiting native resolution paths. It further finds that finality latency, dependence on off-chain indexing and availability, and the interplay of key management and tokenomics design increase operational complexity and raise barriers to adoption. Building on these findings, the paper derives operational requirements and proposes a coexistence-first, five-layer migration framework that incrementally integrates BDNS while retaining the legacy DNS. This provides an incremental path toward a more resilient, inclusive, and secure global naming infrastructure.