> For the complete documentation index, see [llms.txt](https://omen-protocol.gitbook.io/omen-protocol-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://omen-protocol.gitbook.io/omen-protocol-docs/roadmap/multichain-and-bridge-expansion.md).

# Multichain & Bridge Expansion

Explore the OMEN Protocol multichain roadmap, including live Robinhood Chain support and planned expansion across BNB Chain, NEAR, Ink, Arc, Base, and other blockchain ecosystems.

### Overview

OMEN Protocol is building a connected crypto intelligence ecosystem with plans to expand across multiple blockchain networks.

OMEN Utility is currently live on Robinhood Chain. Future development will focus on expanding network support, exploring cross-chain connectivity, and bringing OMEN Utility to additional blockchain ecosystems.

Multichain expansion is part of **Phase 3 — Multichain Expansion** on the OMEN Protocol roadmap.

### Current Network

#### Robinhood Chain

Robinhood Chain is the initial network supported by OMEN Utility and is currently live.

It provides the foundation for the current platform while OMEN Protocol develops its broader multichain strategy.

### Planned Network Expansion

OMEN Protocol plans to explore support for additional blockchain ecosystems, including:

* **BNB Chain**
* **NEAR**
* **Ink**
* **Arc**
* **Base**
* **Other networks** that align with the long-term direction of OMEN Protocol.

This list is not exhaustive. Additional networks may be considered as the ecosystem grows and new opportunities emerge.

Integration priorities will depend on technical feasibility, ecosystem relevance, infrastructure requirements, and security considerations.

### Bridge Integration

Bridge integration is part of the planned multichain expansion strategy.

Blockchain bridges can facilitate asset transfers or cross-chain interactions between networks. Suitable integrations may help improve accessibility across the wider OMEN ecosystem.

Key considerations include:

* **Security:** Evaluate bridge architecture, risks, and trust assumptions.
* **Compatibility:** Assess support for relevant networks and assets.
* **Transaction costs:** Consider bridge fees, network gas, and other applicable costs.
* **Reliability:** Evaluate provider availability and operational limitations.
* **User experience:** Make network selection, transaction status, and associated risks clear.

Specific bridge providers and supported routes have not yet been confirmed.

### Development Priorities

The multichain initiative may progress through the following steps:

1. Evaluate additional networks and their integration requirements.
2. Prioritize potential integrations based on utility and technical feasibility.
3. Assess suitable bridge providers and cross-chain infrastructure.
4. Review security risks and test integrations before release.
5. Announce new network support and bridge functionality when officially available.

The implementation order and scope may evolve as development progresses.

### Long Term Vision

The goal is to make OMEN Protocol accessible across a broader range of blockchain ecosystems while connecting market intelligence, AI-assisted analysis, and trading tools.

Expansion will focus on practical utility, interoperability, and careful evaluation of technical and security requirements.

Robinhood Chain is live today. Additional networks and bridge integrations remain planned until officially announced as available.


---

# 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://omen-protocol.gitbook.io/omen-protocol-docs/roadmap/multichain-and-bridge-expansion.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.