# ZNS Subgraph

Developing a subgraph for the ZNS protocol, which is based on ENS contracts, requires providing specific additional information.

#### 🔍 Domain Search on INK Explorer

ZNS domains on INK (like `hello.ink`) are now fully integrated with the official INK [Blockscout Explorer.](https://explorer.inkonchain.com/)\
Users can search for `.ink` names directly — just like they do for wallet addresses or ENS names.

✅ Live Example: `hello.ink`

<figure><img src="/files/WvU3IzOGawNjJyfNBuEi" alt=""><figcaption></figcaption></figure>

The ZNS protocol has a constant variable called **`identifier`** that uniquely describes the protocol across multiple chains. This value is crucial for calculating the namehash, and therefore, the subgraph should be aware of it.

<div><figure><img src="/files/XTLD3W6Dynj0w3aevr7C" alt=""><figcaption></figcaption></figure> <figure><img src="/files/PxqG2Ii0xx4YkbJtn7GK" alt=""><figcaption></figcaption></figure></div>

<figure><img src="/files/VdSLW0f7XmoqVzGXXAEc" alt=""><figcaption></figcaption></figure>

Blockscout and ZNS are excited to announce their collaboration, aimed at enhancing flexibility and features in name service implementations. This partnership leverages the strengths of both platforms to provide a seamless user experience for discovering and managing decentralized applications (DApps) and name services.

Blockscout now supports Name Services for chains, including ZNS for <mark style="color:purple;">**INK,  Polygon, and Blast.**</mark> Users can search by name in the search bar or use the dedicated Name Services lookup page accessible from the Blockscout Explorer:&#x20;

* [INK Blockscout Name Domains ](https://explorer.inkonchain.com/name-domains?only_active=true\&protocols=zns-ink)

<figure><img src="/files/POwNfkL161UXFuddJX4F" alt=""><figcaption></figcaption></figure>

* [**Polygon Blockscout Name Domains**](https://polygon.blockscout.com/name-domains)

<figure><img src="/files/K3xwKr2VJ8XglQd3L55Z" alt=""><figcaption><p>ZNS Connect Subgraph on Blockscout Explorer menu Polygon</p></figcaption></figure>

* [**Blast Blockscout Name Domains**](https://blast.blockscout.com/name-domains)

<figure><img src="/files/yg898aC6W1lKIx3WfxMD" alt=""><figcaption><p>ZNS Connect Subgraph on Blockscout Explorer menu on Blast</p></figcaption></figure>

#### For more technical details and to explore the ZNS Subgraph, visit: [<mark style="color:purple;">ZNS Subgraph on GitHub</mark>](https://github.com/blockscout/blockscout-rs/tree/main/blockscout-ens/graph-node/subgraphs/zns-subgraph)

#### Developing a Subgraph for ZNS

Creating a subgraph for the ZNS protocol, which is based on ENS contracts, involves providing specific additional information. The ZNS protocol includes a constant variable called "**identifier**" that uniquely describes the protocol across multiple chains.

#### Conclusion

The partnership between Blockscout and ZNS marks a significant step forward in enhancing the user experience for name service implementations. By integrating ZNS into Blockscout Explorer and developing a robust subgraph for the ZNS protocol, we are making it easier for users to navigate and utilize decentralized applications and services.

&#x20;[Stay tuned for more updates as we continue to innovate and improve the blockchain ecosystem.](#user-content-fn-1)[^1]

Want to integrate ZNS search on your chain? Contact us → <info@znsconnect.io>

[^1]:


---

# 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.znsconnect.io/developer-guide/zns-subgraph.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.