> 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

EVM execution on Solana via Cross-Program Invocation.

Rome Protocol is an EVM execution environment running natively inside the Solana runtime. Deploy Solidity smart contracts on Solana with atomic CPI access to Solana programs and liquidity.

## 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 **Martius** (testnet) or **Hadrian** (devnet). Full details, wallet setup, and funding are on the [Networks](/networks/networks.md) page.

| Network                                   | Chain ID | RPC URL                                     |
| ----------------------------------------- | -------- | ------------------------------------------- |
| [Martius](/networks/martius.md) (testnet) | 121214   | `https://martius.testnet.romeprotocol.xyz/` |
| [Hadrian](/networks/hadrian.md) (devnet)  | 200010   | `https://hadrian.testnet.romeprotocol.xyz/` |
| Local                                     | 1001     | `http://localhost:9090`                     |

## 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 dynamically 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 `build a script that syncs our docs to a CMS` 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.