# Ethereum Name Service Ethereum Name Service (ENS) is a decentralized system that allows users to associate human-readable names with Ethereum addresses. It is built on top of the Ethereum blockchain and operates as a decentralized autonomous organization (DAO). ENS is important because it makes it easier for users to interact with the Ethereum network and reduces the risk of sending money to the wrong address. Instead of using a long and confusing string of numbers and letters (e.g. 0x1234567890abcdef) to represent an Ethereum address, users can use a simple and easy-to-remember name like "mywallet.eth" or "mywallet.art". This simplifies the process of identifying and interacting with Ethereum addresses, and it also increases the security and trustworthiness of these interactions. It is important for top-level domains (TLDs) such as .ART to join ENS because it increases the usability and accessibility of the Ethereum network for users. For example, if users can register and use their DNS domains with ENS, it will make it easier for them to identify and interact with Ethereum addresses on these domains. This will also increase the security and trustworthiness of these interactions, as users will be able to verify that they are interacting with the correct Ethereum address using the corresponding ENS name. In summary, ENS is a decentralized system that allows users to associate human-readable names with Ethereum addresses, and it is important for TLDs to join ENS because it increases the usability and accessibility of the Ethereum network for users. Please visit [ENS documentation](https://docs.ens.domains/) for [FAQ](https://docs.ens.domains/frequently-asked-questions). --- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://docs.protocol.art/ethereum-name-service.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.