> For the complete documentation index, see [llms.txt](https://ednsdomains.gitbook.io/edns-sdk-doc/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://ednsdomains.gitbook.io/edns-sdk-doc/readme.md).

# @edns/sdk

As a name and lookup service built on the Polygon blockchain, EDNS provides a Decentralized Domain Naming Service for Web3.0-related demands, including NFT, Cryptocurrency Wallet, Web hosting, DeFi ID, and GameFi ID in the Digital world, by translating machine-readable addresses to human-readable addresses.

EDNS Domains aims at being the pioneer of Web 3.0 disruption by supporting users with innovative Web 3.0 products.  Endeavouring to serve a wider range of users, EDNS will expand to support more blockchains, and ultimately become a multi-chain platform. Thus, we cordially invite different blockchain projects to join the EDNS ecosystem and grow together in this Web 3.0 journey.

To start with, our EDNS Eco-members are encouraged to integrate the EDNS Software Development Kit (SDK) with your dApp products to create a seamless user experience.

Unlike traditional domains in the Web 2.0 world, decentralized domains can integrate dApps from various chains and be more secure. Furthermore, by linking wallets, decentralized domains can simplify platform operations and data management for projects by optimising the user login step, which also greatly enhance the user experience. Accelerating blockchain projects’ entry into Web 3.0, our easy-to-integrate SDK can work well with different types of dApps, for example, wallets, NFT platforms, GameFi games and more.


---

# 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, and the optional `goal` query parameter:

```
GET https://ednsdomains.gitbook.io/edns-sdk-doc/readme.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.