> For the complete documentation index, see [llms.txt](https://terranameservice.gitbook.io/terra-name-service-tns/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://terranameservice.gitbook.io/terra-name-service-tns/introduction.md). # Introduction When transacting on Terra, users normally interact with wallet addresses—long strings of alphanumeric characters that are unreadable and almost impossible to remember. Similar to the way web users replace numerical IP addresses by registering domain names through the Domain Name Service (DNS), blockchain users can transform long and unreadable Terra addresses to a unique on-chain profile with .ust domain. In this white paper, we introduce a protocol, Terra Name Service (TNS), which allows users to map their terra address with the domain name they like. This would enable terra users to craft the name of their wallet address to be short and human-readable. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## 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, and the optional `goal` query parameter: ``` GET https://terranameservice.gitbook.io/terra-name-service-tns/introduction.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. 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.