> 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/readme.md).

# Getting Started

Build EVM apps that serve Solana wallets, call Solana programs from Solidity, and move assets between both sides.

Rome makes EVM and Solana one market.

Rome runs EVM chains inside Solana, so any EVM protocol can deploy once and open itself to Solana wallets. A Solidity contract on Rome calls Solana programs directly, so EVM users reach Kamino and Solana DEXes. Solgate makes Solana a chain on the AggLayer, so assets move permissionlessly between Solana and every AggLayer EVM chain. EVM users and Solana users are equal parties in one market, and Canton is the next extension. Read [One market](/getting-started/one-market.md) for the full picture.

## What Makes Rome Different

* **Single State** — EVM contracts and Solana programs share the same state. No bridging, no sync delays.
* **CPI Access** — Solidity contracts call any Solana program directly, from SPL Token to Meteora.
* **Standard Tooling** — Deploy with Hardhat or Foundry. Interact with MetaMask. Write Solidity.
* **App Sovereignty** — Each app gets its own EVM chain with custom gas token and fee revenue.

## For Developers

* [What is Rome?](/getting-started/what-is-rome.md) — How EVM execution works on Solana
* [Quickstart](/getting-started/quickstart.md) — Deploy your first contract in under 5 minutes
* [Deploy Solidity](/developer-guides/deploy-solidity.md) — Hardhat and Foundry deployment guides
* [Call Solana from EVM](/developer-guides/call-solana-from-evm.md) — CPI from Solidity to Solana programs
* [Rome SDK](/products/rome-sdk.md) — Build against Rome from Solidity and Rust

## Apps on Rome

Rome is live software. See what's running today — DEX, lending, bridge, explorer, and more — in [Apps on Rome](/apps-on-rome/apps.md).

## Products

* [App Sovereignty](/products/app-sovereignty.md) — Launch your own EVM chain on Solana
* [Oracle Gateway](/products/oracle-gateway.md) — Pyth/Switchboard as Chainlink AggregatorV3Interface
* [Rome SDK](/products/rome-sdk.md) — Build against Rome from Solidity and Rust

## Core Concepts

* [Architecture](/getting-started/architecture.md) — System overview and component diagram
* [Execution Model](/core-concepts/execution-model.md) — Atomic vs iterative execution
* [Token Interop](/core-concepts/token-interop.md) — How ERC-20 and SPL tokens work together
* [Constraints](/core-concepts/constraints.md) — Important limits and boundaries

## Reference

* [Contract Addresses](/reference/contract-addresses.md) — Deployed addresses per chain
* [Glossary](/resources/glossary.md) — Rome-specific terminology
* [FAQ](/resources/faq.md) — Common questions answered

## Networks

Build against **Hadrian** (testnet) and ship to **Rubicon** (mainnet, real USDC). Ostia DevNet is a separate chain on Canton, with its own test coin. Full details, wallet setup, and funding are on the [Networks](/networks/networks.md) page.

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

## Ostia, a ZK EVM on Canton (DevNet)

Ostia is an EVM chain that settles on Canton, not Solana. Each block is proven with ZisK and then committed on Canton Network in one transaction. It is open on Canton DevNet.

* Chain ID `770101`, test coin tROME. Get some from the faucet in the explorer.
* RPC: `https://ostia.devnet.romeprotocol.xyz/rpc`
* Explorer: [ostia.devnet.romeprotocol.xyz](https://ostia.devnet.romeprotocol.xyz/)
* [Overview](/canton-zk-evm/canton-zk-evm.md) — what Ostia is, and how it differs from the Rome ZK EVM rollups on Solana

## Need Help?

* [Discord](https://discord.gg/vZ9rnCdNSB) — Developer community and support
* [Telegram](https://t.me/+tdnr-M6kcngxYzhk) — Updates and announcements
* [GitHub](https://github.com/rome-protocol) — Source code and issues


---

# 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/readme.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.