# Name Service (SNS)

Satoshis are the foundation of our entire protocol ecosystem, and their ordinal numbers can be considered as indices of satoshis. However, the ordinal numbers are 64-bit integers, which are too long and not easy to remember. In order to quickly index each satoshi, it is necessary to develop a name service based on satoshis, allowing users to remember satoshis that hold significant meaning to them. The relationship between ordinal numbers and names is similar to the relationship between IP addresses and domain names. The SAT20 Name Service is a completely decentralized, BTC-based name service that is available to everyone on a fair basis and is not controlled by any third party.

The core of the name service is that each name is unique, and there are no sub-namespace. This avoids the possibility of fraud. Each name is an NFT (Non-Fungible Token) that is engraved on a satoshi. A Satoshi has only one name, and the name and Satoshi are also in one-to-one correspondence. Names are bound to satoshis, so whoever owns the satoshi also owns the name. When a satoshi is transferred, the name is transferred along with it. Names are also a type of sat asset.

The SAT20 name service is based on and expands upon the fundamental rules of .BTC. For example, the SAT20 naming service supports various domain extensions, such as .SATS and .X, as well as names without monkey characters, such as ABC and XYZ.

The SAT20 naming service aims to become the foundational DID service for the Bitcoin ecosystem.


---

# 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.sat20.org/english/asset-issuance-protocol-ordx/sns.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.