> For the complete documentation index, see [llms.txt](https://docs.bifrost.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.bifrost.io/for-the-community/governance/proposal-template/hrmp.md).

# HRMP

### **TL:DR**

This batched proposal is to Accept/Open an HRMP channel with \[SAMPLE NETWORK] *and Register Asset(s) \[TOKEN 3 SYMBOL], \[TOKEN 2 SYMBOL].* (optional)

### **Network Information:**

Brief description of Network such as “\[SAMPLE NETWORK] is a an scalable, non-custodial decentralized cross-chain liquidity staking specialized parachain (Omnichain LSD Layer1) built on Polkadot, currently supporting liquidity derivatives on over 9+ blockchains.”

* Website: \[PARACHAIN WEBSITE]
* Twitter: \[PARACHAIN TWITTER]
* Discord: \[PARACHAIN DISCORD]
* Telegram: \[PARACHAIN TELEGRAM]

### **Summary**

We propose to open a bi-directional channel between Bifrost and \[SAMPLE NETWORK]. Initially, the main use case will be …, but it can be further expanded to other use cases. The proposal also includes the \[SAMPLE TOKEN 1] asset registration on \[SAMPLE NETWORK] and \[SAMPLE TOKEN 2] asset registration on Bifrost , with the following details:

* Multilocation: *\[MULTILOCATION OF ASSET]*
* Decimals: *\[TOKEN DECIMALS]*
* Name: *\[TOKEN NAME]*
* Symbol: *\[TOKEN SYMBOL]*


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.bifrost.io/for-the-community/governance/proposal-template/hrmp.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.