# Introduction

<figure><img src="https://3277765323-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FStOwhwvhAvs3L45w42Xw%2Fuploads%2FETMAlKEh3QKjlpZy08K8%2FSliceimg.png?alt=media&#x26;token=cb63b7c2-3068-47b7-838b-8dafea273415" alt=""><figcaption></figcaption></figure>

## What Is Pulse Domains?

Pulse Domains, the PulseChain Naming Service (PNS), is meant to bring adoption and utility to the Pulsechain Ecosystem, namely, by allowing public addresses to have a human-readable, memorable link. Everyone is encouraged to interact with the protocol as they are permissionless contracts on the PulseChain blockchain.

\
What is PNS?

PulseChain Name Service (PNS) has a main utility to map human-readable names (ex. ‘alex.pls’) to machine-readable identifiers such as PulseChain addresses, other cryptocurrency addresses, content hashes, and metadata.

<figure><img src="https://3277765323-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FStOwhwvhAvs3L45w42Xw%2Fuploads%2FXKf0OgxyZVKcS00QXJU8%2FExample_1%20(1).png?alt=media&#x26;token=eeca9383-8282-4267-a339-33e17c55bb0a" alt=""><figcaption><p>Example of a 0x Public Address being converted to PNS</p></figcaption></figure>

PNS has similar goals to DNS, the internet’s Domain Name Service, but has a significantly different architecture due to the capabilities--and constraints--provided by EVM blockchains. Similarly, like DNS, PNS operates on a system of dot-separated hierarchical names called domains, with the owner of a domain having full control over subdomains.

Top-level domains (‘.pls’) are owned by smart contracts called registrars, which specify rules governing the allocation of their subdomains. Anyone may, by following the rules imposed by these registrar contracts, obtain ownership of a domain for their own use. PNS also supports importing in DNS names already owned by the user for use on PNS.

<figure><img src="https://3277765323-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FStOwhwvhAvs3L45w42Xw%2Fuploads%2Fh8hSgxDOIMo1MDaeeaz2%2FExample2%20(1).png?alt=media&#x26;token=1c497121-2d5d-442c-8529-f8fa3c09064b" alt=""><figcaption><p>Sub Domain Example</p></figcaption></figure>

Because of the hierarchical nature of PNS, anyone who owns a domain at any level may configure subdomains - for themselves or others - as desired. For instance, if Alex owns 'alex.pls' he can create 'pay.alex.pls' and configure it as he wishes.

## Quick links

{% content-ref url="registration-faq" %}
[registration-faq](https://docs.pulse.domains/registration-faq)
{% endcontent-ref %}

## Get Started

We've put together some helpful guides for you to get started.

{% content-ref url="guides/domain-registration" %}
[domain-registration](https://docs.pulse.domains/guides/domain-registration)
{% endcontent-ref %}

{% content-ref url="guides/updating-your-profile" %}
[updating-your-profile](https://docs.pulse.domains/guides/updating-your-profile)
{% 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://docs.pulse.domains/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.
