> 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/goals.md).

# Goals

Omnity's ultimate goal is to connect thousands of blockchains, facilitate millions of cross-chain transactions per day, gain significant protocol income from the volume, and make itself and IC the indispensable infrastructure of the blockchain world.

For Web 3.0 communities, Omnity can be seen as a white-labeled, trustless, and permissionless version of [Circle’s Cross-Chain Transfer Protocol (CCTP](https://www.circle.com/en/cross-chain-transfer-protocol)). By leveraging Omnity, any community can have its own CCTP for its tokens without bothering to write a line of code. What’s more, Omnity has an embedded mechanism for sharing fees with any entities, like information portals and wallets, that brings usage to the protocol.

Omnity will start from a fungible token transfer protocol with basic extensibility imitating [IBC Hooks](https://github.com/cosmos/ibc-apps/tree/main/modules/ibc-hooks). But the whole infrastructure is quite asset-type neutral. Adding new anchor points (Export and Port) to connected blockchains allows Omnity to support NFT assets without too much trouble. We expect Bitcoin Ordinals NFTs will go multi-chain via Omnity in Q4 2024, followed by Ethereum NFTs.

[Arbitrary Messaging Bridges(AMB)](https://li.fi/knowledge-hub/navigating-arbitrary-messaging-bridges-a-comparison-framework/) are a different beast. Although we haven’t figured out exactly how to overlay AMB on the Omnity network, we don’t see any outstanding roadblocks to do that. For now, we will leave Omnity AMB design and elaboration to future works.


---

# 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/goals.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.