> For the complete documentation index, see [llms.txt](https://docs.bloxchain.app/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.bloxchain.app/introduction/supported-networks.md). # Supported networks Official deployments are live on the 15 supported networks, in the Platform and in the Protocol. **Alpha ยท Local-first.** The Platform is alpha software. Your account list lives on this device unless you join an organization. Glamsterdam increases the gas cost of deploying an account. ## Networks | Network | Chain ID | Status | Notes | | ----------------------- | -------- | ------------ | --------------------------------------------------------------------------------------------------------------------------- | | **Sepolia** | 11155111 | Supported | Official deployment | | **Base Sepolia** | 84532 | Supported | Official deployment | | **Optimism Sepolia** | 11155420 | Supported | Official deployment | | **Arbitrum Sepolia** | 421614 | Supported | Official deployment | | **Arc testnet** | 5042002 | Supported | Official deployment | | **Robinhood testnet** | 46630 | Supported | Official deployment | | **Ethereum** | 1 | Supported | Official deployment | | **Base** | 8453 | Supported | Official deployment | | **Arbitrum One** | 42161 | Supported | Official deployment | | **Optimism** | 10 | Supported | Official deployment | | **Polygon** | 137 | Supported | Official deployment | | **BNB Smart Chain** | 56 | Supported | Official deployment | | **Avalanche C-Chain** | 43114 | Supported | Official deployment | | **Arc** | 5042 | Supported | Official deployment | | **Robinhood** | 4663 | Supported | Official deployment | | **Custom EVM networks** | Any | You add them | Stored on this device (or shared by an organization). No official deployment is provided; you supply the contract addresses | To get Sepolia test ETH, use any public Sepolia faucet. Most faucets ask you to sign in with a wallet or an account and rate-limit requests. You need enough for a deployment and a handful of transactions. ## Adding a custom network Go to **Settings โ†’ Networks** and choose **Add network**. Provide the network name, chain ID, RPC URL, an optional block explorer URL, the currency name, symbol and decimals, and whether it is a testnet or your default network. Networks you add are stored in this browser and used for reads and wallet switching. Clearing site data removes them, so export a backup from **Settings โ†’ Backup**. See [Networks](/platform-guide/settings/networks.md). ## How the Platform talks to a network The Platform prefers the RPC endpoint of your connected wallet for both reads and writes. A public RPC is used as a fallback when no wallet is connected, so reads still work signed out. You pay gas from your own wallet for every transaction you submit; there is no hidden relay unless you opt into the optional Bloxchain broadcaster where it is available. If your wallet is on a network the Platform does not recognise, the top bar shows **Wrong network**. Switch your wallet to one of the supported networks, or add the network under **Settings โ†’ Networks**. ## Official addresses The Platform deploys accounts with the official factory, BasicFactory, which mints a BasicAccount. Their addresses, with EngineBlox and the definition libraries, are printed once, with every other number and default the Platform enforces, on [Limits and defaults](/resources/limits-and-defaults.md#networks-and-official-addresses). The factory and template also appear under **Technical** in a preset's details drawer on Discover, and in the **Advanced** section of the deploy dialog. Sepolia also carries the developer toolkit (the CopyBlox factory and the AccountBlox template) for experiments. It is Sepolia only and is not the default Platform path. See [Deploy the Protocol](/developers/deployment.md#sepolia-developer-toolkit). ## Published address catalog The official addresses ship in the `@bloxchain/contracts` npm package as `official-deployed-addresses.json`. The catalog contracts have the same address on every network it lists. This catalog is the list of networks with official deployments. The Platform and the Protocol both use it. | Catalog network | Chain ID | | ------------------- | -------- | | `sepolia` | 11155111 | | `base-sepolia` | 84532 | | `optimism-sepolia` | 11155420 | | `arbitrum-sepolia` | 421614 | | `arc-testnet` | 5042002 | | `robinhood-testnet` | 46630 | | `mainnet` | 1 | | `base` | 8453 | | `arbitrum` | 42161 | | `optimism` | 10 | | `polygon` | 137 | | `bsc` | 56 | | `avalanche` | 43114 | | `arc` | 5042 | | `robinhood` | 4663 | A chain that is not in the catalog, such as a local test chain, has no official addresses; use the `deployed-addresses.json` from your own deploy. ## Reference prices The **Value** column on **Assets** shows a reference price from CoinGecko. Prices resolve on Ethereum and Arbitrum One only. Every other network, Sepolia included, shows a dash: the price map is fail-closed, so a chain that is not one of those two is never quoted. Reference prices are indicative only. ## Related * [Connect a wallet](/platform-guide/connect-wallet.md) * [Deployment](/developers/deployment.md) * [Releases](/resources/releases.md) --- # 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.bloxchain.app/introduction/supported-networks.md?ask=&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.