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

# Resolution

## Forward Resolution

Forwards resolution is the process of going **from name to address**. As well as to load the text records associated to a name. Users can set up to two text records with any `key:value` pair, and more will be supported in the future. 

Implementing forwards resolution in a dApp can be as simple as using a single line of code! To learn more about how to implement forwards resolution, check out our [dApp integration](/hyperliquid-names/dapp-integration/dapp-integration.md) page.

### Coin Types

By default, names resolve to the Hyper EVM address. Hyperliquid Names also supports resolving to other coin addresses based on [SLIP-0044](https://github.com/satoshilabs/slips/blob/master/slip-0044.md). Currently, we support the following coin types:

| Coin type | Symbol | Coin     |
| --------- | ------ | -------- |
| 0         | BTC    | Bitcoin  |
| 60        | ETH    | Ethereum |
| 501       | SOL    | Solana   |

## Reverse Resolution (Primary Name)

Reverse resolution is the process of going **from address to name**. This allows for any address to be resolved into a human readable name. Instead of pages filled with addresses, you can now show the names of the people behind the addresses.

Implementing forwards resolution in a dApp can be as simple as using a single line of code! To learn more about how to implement forwards resolution, check out our [dApp integration](/hyperliquid-names/dapp-integration/dapp-integration.md) page.


---

# 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://hyperliquid-names.gitbook.io/hyperliquid-names/resolution.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.