> For the complete documentation index, see [llms.txt](https://omega-6.gitbook.io/omega/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://omega-6.gitbook.io/omega/omega-terminal-1/networks.md).

# Networks

Omega Terminal is designed to be multi-chain. While it runs natively on the **Omega Network**, it interacts seamlessly with other major blockchains.

## Primary Network

### Omega Network (Testnet/Mainnet)

* **Chain ID**: Configured in system settings.
* **Currency**: OMEGA
* **Features**: Mining, Faucet, Native Deployments.

## Integrated Chains via Adapters

{% tabs %}
{% tab title="🔷 Ethereum (EVM)" %}

* Full support via `ethers.js`.
* Connect with MetaMask.
* Features: Send ETH, interact with contracts, Uniswap integration.
  {% endtab %}

{% tab title="🟣 Solana" %}

* Support via `@solana/web3.js`.
* Connect with Phantom.
* Features: Jupiter Aggregator swaps, token transfers, SPL token management.
  {% endtab %}

{% tab title="🟡 Binance Smart Chain (BSC)" %}

* EVM compatible support.
* PancakeSwap integration for trading.
  {% endtab %}

{% tab title="🔵 Base / Arbitrum / Optimism" %}

* Full L2 support for faster and cheaper transactions.
  {% endtab %}
  {% endtabs %}

{% stepper %}
{% step %}

### Switching Networks

You can usually switch networks using your wallet provider (MetaMask/Phantom). The terminal detects the network change and adapts the available commands accordingly.
{% endstep %}

{% step %}

### Example behavior after switching

* Some commands adapt to the active network.
  * For example, `swap` might route through Uniswap when connected to Ethereum.
  * The same `swap` command might route through Jupiter when connected to Solana.
    {% endstep %}
    {% endstepper %}


---

# 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://omega-6.gitbook.io/omega/omega-terminal-1/networks.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.