> For the complete documentation index, see [llms.txt](https://docs.energyweb.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.energyweb.org/energy-solutions/digital-spine-by-energy-web/component-guides/energy-web-name-service-ens.md).

# Energy Web Name Service (ENS)

## Overview

The Energy Web Name Service enables users to map human-readable names (e.g., `name.ewc`) to their DID address and create a sub-name for other resources, like an email address or smart contract (e.g., `resource.name.ewc`). This is a deployment of the Ethereum Name Service on the Energy Web Chain. The Ethereum Name Service is a distributed, open and extensible naming system based on the Ethereum blockchain. ENS eliminates the need to copy or type long addresses.

* Map simple names like `alice.ewc` to Energy Web Chain addresses, content hashes, and metadata.
* Improve usability of dApps by returning human readable names instead of long hashes through 'reverse resolution’.

Like DNS, ENS operates on a system of dot-separated hierarchical names called domains, with the owner of a domain having full control over the allocation of subdomains.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## 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.energyweb.org/energy-solutions/digital-spine-by-energy-web/component-guides/energy-web-name-service-ens.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.