# PNS: Your Identity in Polkadot

## Why PNS Matters

Imagine sending tokens to `0x6C6b33B45573DE6C04E7b644246129DDb3d8610D` when you could just use `alice.dot`. PNS transforms complex Polkadot addresses into human-readable names, making web3 more accessible and safer.

### Real-world Impact

* ✅ Send assets to `company.dot` instead of `0x6C6...10D`
* 🔒 Reduce transaction errors
* 🌐 One name works across all Polkadot parachains
* 🎯 Build your web3 identity and brand

## Why Choose PNS?

### For Users

* **Universal Identity**: One name for all Polkadot services
* **Asset Protection**: Never send to wrong addresses again

### For Developers

* **Simple Integration**: Easy to add PNS to your projects
* **Extensible**: Add custom records and features

### For Projects

* **Brand Protection**: Secure your project's identity
* **Enhanced UX**: Make your dApp more user-friendly
* **Ecosystem Ready**: Integration with major Polkadot tools

This project is licensed under the MIT License - see the LICENSE file for details.


---

# 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://pns.gitbook.io/pns/readme.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.