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

# Protocol Revenue

Omnity will charge a reasonable fee for cross-chain transactions constituting a protocol revenue stream. Considering that the operational cost (cycles paid by all Omnity canisters) of the Omnity protocol is meager, we believe that the cross-chain fee charged by Omnity could remain at the lowest level in the industry. The SNS will determine the fee standard in the future, while the initial setting upon launch is planned to be as follows:&#x20;

* Settlement chains to execution chains — free.
* Execution chains to execution chains — 0.2 USD per transfer.
* Execution chains to settlement chains — 2.0 USD per redemption.


---

# 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://omnity.gitbook.io/litepaper/upgrowth/protocol-revenue.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.
