> For the complete documentation index, see [llms.txt](https://docs.rome.builders/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.rome.builders/networks/networks.md).

# Overview

Public Rome chains — chain IDs, RPC endpoints, explorers, and gas tokens.

Rome's public EVM chains on Solana are **Rubicon** (mainnet) and **Hadrian** (testnet), each executing inside a Solana program. **Ostia DevNet** is a ZK EVM on Canton (see below). Hadrian settles on Solana Devnet, so its USDC and SOL are not real money. Rubicon settles on Solana mainnet and its gas is real USDC. Build and test on Hadrian first.

| Network                                           | Chain ID | RPC                                         | Explorer                                                     | Gas token                   |
| ------------------------------------------------- | -------- | ------------------------------------------- | ------------------------------------------------------------ | --------------------------- |
| [Rubicon](/networks/rubicon.md) (mainnet)         | 7531     | `https://rubicon.mainnet.romeprotocol.xyz/` | [via-rubicon](https://via-rubicon.mainnet.romeprotocol.xyz/) | USDC (real)                 |
| [Hadrian](/networks/hadrian.md) (testnet)         | 200010   | `https://hadrian.testnet.romeprotocol.xyz/` | [via-hadrian](https://via-hadrian.testnet.romeprotocol.xyz/) | USDC (test)                 |
| [Ostia DevNet (Canton)](/canton-zk-evm/devnet.md) | 770101   | `https://ostia.devnet.romeprotocol.xyz/rpc` | [ostia.devnet](https://ostia.devnet.romeprotocol.xyz/)       | tROME (test coin, no value) |

Ostia DevNet is a different kind of chain. It is a ZK EVM that settles on Canton Network DevNet, not a program on Solana, and it has its own test coin and faucet. Its network details are on [Ostia DevNet](/canton-zk-evm/devnet.md). The Solana-chain notes on this page (USDC gas, the bridge, WebSocket subscriptions) apply to Rubicon and Hadrian.

Chain metadata — chain IDs, contract addresses, token mints, gas pools — is canonical in the [Rome registry](https://github.com/rome-protocol/rome-registry). Don't hardcode addresses; read them from there. Each contract lists its versions, and the one to use has `status` `live` — see [Reading the contracts list](/reference/contract-addresses.md#reading-the-contracts-list). The registry covers Hadrian. Rubicon is not in it yet, nor in `create-rome-app` or `rome-cli`, so take Rubicon's values from [its page](/networks/rubicon.md).

Operators run their own Rome ZK EVM chains on Solana devnet. Each chain posts its batches to Rome's shared inbox program and settles its proved roots through the shared settlement program. See [Run a rollup](/rome-zk-evm/run-a-rollup.md) to start one.

## Add a network to your wallet

Each network page lists the manual MetaMask values. On Rubicon and Hadrian, WebSocket subscriptions are served on the same host as the HTTPS RPC (swap `https://` for `wss://`).

## Fund a wallet

Gas on Rubicon and Hadrian is USDC, and there is no Rome faucet for them. On Hadrian, bring in test USDC with the [Rome Bridge](/apps-on-rome/bridge-api.md), either from a testnet such as Ethereum Sepolia or from Solana Devnet. A wallet that works from the Solana side also needs a little devnet SOL for Solana fees. On Rubicon the USDC is real; bridge it in with the Rome Bridge on mainnet. Where to get each token is in [Faucets](/resources/faucets.md). Ostia DevNet pays gas in its own test coin, tROME, from a faucet in its explorer.

## Local development

There is no public local stack for Rubicon or Hadrian. Develop against a public chain — see the [Quickstart](/getting-started/quickstart.md). Ostia can be run on your own machine; see [Run your own Ostia](/canton-zk-evm/run-it-locally.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.rome.builders/networks/networks.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.