# Introduction

As the Monad ecosystem expands, users will need a convenient way to interact with dApps, protocols; and the need for an efficient means to engage with dApps and protocols becomes essential. Using cryptocurrency addresses can be cumbersome and error-prone sometimes.&#x20;

This is where Nad Name Service shines.

### What is Nad Name Service ?

Nad Name Service (NNS) is a distributed, open web3 name service based on the Monad blockchain.

At its core, NNS provides mapping between human-readable names like 'salmo.nad' to machine-readable identifiers such as cryptocurrency addresses, content hashes, metadata, and more.

DApps and protocols integrated with NNS enable users to use  human-readable names instead of cryptocurrency addresses , making interactions as seamless and smooth as possible.

<figure><img src="/files/GTgIAMPss41eJFrBYjfa" alt=""><figcaption><p>Name mapping by NNS</p></figcaption></figure>

### NNS Names

Nad Name Service supports a wide range of character sets and emojis, allowing users to choose any name they want. This enables users to freely express their style through their chosen names.

Examples of valid name:

* salmo.nad
* 🥚keone🥚.nad
* 🐸🤝🐸.nad
* 안녕하세요.nad
* 你好.nad
* ...

Each name will be a NFT so that users can easily trade names on NFT marketplaces.

***

### Profile

Each name comes with a customizable profile. Users can personalize their profile by setting an avatar, adding social links, and configuring text records for their name.


---

# 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.nad.domains/overview/introduction.md?ask=<question>
```

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.
