> 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.md). # Upgrowth The best moat for a Web 3.0 protocol is its network effects. Omnity protocol has multi-level network effects by continuously onboarding new execution chains and asset classes. Omnity will launch at the Next Bitcoin Halving with its first settlement chain, Bitcoin, and first assets class, [Runes](https://rodarmor.com/blog/runes/). [BRC20](https://domo-2.gitbook.io/brc-20-experiment/) and potentially other Bitcoin token standards will be embraced shortly after that. The progress of [IC's native integration with Ethereum](https://internetcomputer.org/ethereum-integration) will determine when Omnity will support Ethereum. A fair guess would be no later than Q3 2024. There are no technical obstacles to IC acting as a settlement chain in Omnity. The only precondition is demand. On the execution chain side, we prefer to prioritize support for frameworks such as OP Stack, Cosmos SDK, Arbitrum Orbit, Polygon CDK, etc. The reason is simple: supporting a popular framework enables dozens or even hundreds of chains to connect with Omnity. On the other hand, we are also open to supporting L1 chains, like NEAR and Solana, if there are strategic opportunities for drawing usage. --- # 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.md?ask=&goal= ``` `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.