> For the complete documentation index, see [llms.txt](https://docs.bloombot.app/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.bloombot.app/evm/basics/getting-started-new/chains.md).

# Chains

{% hint style="info" %}
The eight chains @BloomEVMbot trades on, and how to switch the chain a screen shows.
{% endhint %}

## The Chains

The bot shows each chain by a short name.

<div align="left"><figure><img src="https://4054888922-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FcxXsA1jjenOz2nZ4oZz9%2Fuploads%2FB5bflEQTeytCEu1S5BW0%2Fchains-settings-chain-list.png?alt=media&amp;token=5fd6fa77-ad2e-45ad-a98a-8d6a81048424" alt="The chain list with a button for each chain."><figcaption></figcaption></figure></div>

| In the bot  | Chain           | Coin for amounts and gas |
| ----------- | --------------- | ------------------------ |
| **🔶 BSC**  | BNB Smart Chain | BNB                      |
| **💎 ETH**  | Ethereum        | ETH                      |
| **🟦 BASE** | Base            | ETH                      |
| **🪶 RBH**  | Robinhood Chain | ETH                      |
| **🧪 HYPE** | HyperEVM        | HYPE                     |
| **🔵 ARC**  | Arc             | USDC                     |
| **🟣 INK**  | Ink             | ETH                      |
| **🌿 ELY**  | Elysium         | HYPE                     |

The coin of a chain is what buy amounts, balances and gas are counted in there, so 0.5 on BSC means 0.5 BNB. One wallet address works on all chains. A button appears only on the chains where its feature is offered.

{% hint style="warning" %}
Each chain keeps its own balance, so coins on Base can only be spent on Base. To move funds between chains, use [Bridge](https://docs.bloombot.app/evm/bot-features/wallets/bridge.md).
{% endhint %}

## Your Current Chain

Many screens show a row of three buttons: <kbd>⬅️</kbd>, the chain's name and <kbd>➡️</kbd>.

<div align="left"><figure><img src="https://4054888922-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FcxXsA1jjenOz2nZ4oZz9%2Fuploads%2FZ9G4eRnQBkkr2PK5hEQy%2Fchains-positions-chain-switch.png?alt=media&amp;token=22279f68-e78e-444a-be43-0d652a054792" alt="Positions with the chain switch row."><figcaption></figcaption></figure></div>

<kbd>➡️</kbd> moves to the next chain and <kbd>⬅️</kbd> to the previous one, and the chain is saved as your current chain. A new account starts on BSC.

These screens show your current chain and change it:

* <kbd>💼 Positions</kbd>
* <kbd>📝 Orders</kbd>
* <kbd>💸 Withdraw</kbd>
* <kbd>💰 Wallets</kbd>
* <kbd>🤖 Copy Trade</kbd>
* <kbd>🐤 Social</kbd>
* <kbd>💤 AFK Mode</kbd>

To switch to Base:

1. Open <kbd>💼 Positions</kbd> from Home.
2. Tap <kbd>➡️</kbd> until the middle button reads <kbd>Chain: BASE</kbd>.

## Screens With Their Own Chain

These screens choose their own chain.

* The token panel has its own <kbd>⬅️ Chain: BSC ➡️</kbd> row.
* A task's own screen has a <kbd>⬅️ ➡️</kbd> row that moves that task alone.
* In <kbd>⚙️ Settings</kbd>, you pick a chain from the list.
* <kbd>🗓️ PnL Calendar</kbd> opens on your current chain, and its arrows change only the calendar.
* <kbd>👥 Referrals</kbd> opens on **🌐 GLOBAL**, and its arrows step through the chains.
* <kbd>✈️ Bridge</kbd> has its own sender and receiver chain buttons.
* Home lists all eight balances at once.

None of them changes your current chain.


---

# 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://docs.bloombot.app/evm/basics/getting-started-new/chains.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.
