# Project Introduction

The Filecoin Naming Service (FNS) is a decentralized name service based on the Filecoin EVM. It resolves metadata into easy-to-read xxx.fil names. Each FNS domain is treated as an NFT, and the FNS contract complies with the interfaces of the ERC-721 standard. The NFT can be transferred and traded on secondary markets.

<figure><img src="https://2582887948-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F7n1T7otwx1O0SkXh2qmB%2Fuploads%2F0jPBCQFcVeMjo0cK1DkJ%2Fimage.png?alt=media&#x26;token=4faa3667-8fad-4a3e-a956-7be1be7c6f14" alt=""><figcaption></figcaption></figure>

FNS is similar to Ethereum's ENS (Ethereum Name Service) and Handshake. FNS allows users to use easy-to-remember domain names to access their data stored on the Filecoin network. By mapping the CID (Content Identifier) of a file to an easy-to-remember domain name, FNS provides a convenient way to access data stored on Filecoin without needing to remember complex CIDs. FNS also provides an easy-to-integrate way for developers to use the Filecoin network.

FNS provides a secure and decentralized way to resolve on-chain and off-chain address resources on the Filecoin network into simple human-readable domain names. It is an important part of the Filecoin ecosystem. It can not only make the filecoin system more readable and user-friendly, but also become an important infrastructure for web3.

Users can use FNS as an identity to access the web3 world, and only need to integrate the DNS domain name into FNS, and their domain name can be used as a wallet address, Web3 username and a decentralized website.

## Quick links

{% content-ref url="overview/what-we-do" %}
[what-we-do](https://opengate-lab.gitbook.io/fns/overview/what-we-do)
{% endcontent-ref %}

{% content-ref url="overview/our-features" %}
[our-features](https://opengate-lab.gitbook.io/fns/overview/our-features)
{% endcontent-ref %}

{% content-ref url="overview/faq" %}
[faq](https://opengate-lab.gitbook.io/fns/overview/faq)
{% endcontent-ref %}

## Get Started

We've put together some helpful guides for you to get setup with our product quickly and easily.

{% content-ref url="interaction-tutorial/how-to-transfer-fil-to-a-0x-wallet-address" %}
[how-to-transfer-fil-to-a-0x-wallet-address](https://opengate-lab.gitbook.io/fns/interaction-tutorial/how-to-transfer-fil-to-a-0x-wallet-address)
{% endcontent-ref %}

{% content-ref url="interaction-tutorial/how-to-register-a-fns-domain-name" %}
[how-to-register-a-fns-domain-name](https://opengate-lab.gitbook.io/fns/interaction-tutorial/how-to-register-a-fns-domain-name)
{% endcontent-ref %}

{% content-ref url="interaction-tutorial/how-to-register-a-fns-domain-name/fns-domain-referral-program" %}
[fns-domain-referral-program](https://opengate-lab.gitbook.io/fns/interaction-tutorial/how-to-register-a-fns-domain-name/fns-domain-referral-program)
{% endcontent-ref %}

{% content-ref url="interaction-tutorial/how-to-trade-fns-domain-names" %}
[how-to-trade-fns-domain-names](https://opengate-lab.gitbook.io/fns/interaction-tutorial/how-to-trade-fns-domain-names)
{% endcontent-ref %}


---

# 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://opengate-lab.gitbook.io/fns/project-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.