> For the complete documentation index, see [llms.txt](https://docs.nomad.xyz/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.nomad.xyz/token-bridge/asset-issuers.md).

# Asset Issuers

One common use case of the Nomad token bridge is to instantly take single-chain assets multi-chain.

Examples:

* [Covalent took $CQT, their network staking token, from Ethereum to Moonbeam.](https://www.covalenthq.com/blog/cqt-staking-live/)
* [Elasticswap took $TIC, their rebasing token, from Avalanche to Ethereum.](https://twitter.com/ElasticSwap/status/1523811687354159106)
* [Hummingbot took $HBOT, their governance token, from Ethereum to Avalanche](https://twitter.com/hummingbot_io/status/1535316005777448974), and more chains soon™.

{% embed url="<https://hummingbot.io/en/blog/2022-06-hbot-tokens-now-on-avalanche-nomad/>" %}
Learn more about why Hummingbot chose Nomad to take HBOT cross-chain
{% endembed %}

If you are an asset issuer interested in taking an existing token multi-chain or deploying your token for the first time on multiple chains, please [fill out this form](https://forms.clickup.com/14205595/f/dhgmv-13960/GQOZTT48N80YE9ELN3). Once you have filled it out, we will get back to you within a week.


---

# 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.nomad.xyz/token-bridge/asset-issuers.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.