# Rome Protocol Docs ## πŸ‡ΊπŸ‡Έ English - [Getting Started](https://docs.rome.builders/readme.md): EVM execution on Solana via Cross-Program Invocation. - [What is Rome?](https://docs.rome.builders/getting-started/what-is-rome.md): Rome is an EVM execution environment inside Solana. Whatever you build is open to EVM users, Solana users, and users on other chains. Four ways to build. - [Why Rome?](https://docs.rome.builders/getting-started/why-rome.md): How Rome differs from other EVM-on-Solana approaches β€” atomic CPI composability, single shared state, and sovereign app chains with custom gas tokens. - [Architecture](https://docs.rome.builders/getting-started/architecture.md): How Rome's components fit together β€” EVM execution inside a Solana program. - [Ecosystem & repos](https://docs.rome.builders/getting-started/ecosystem.md): Every public Rome repo, what it is, and how they compose β€” the map for navigating the surface. - [Quickstart](https://docs.rome.builders/getting-started/quickstart.md): Deploy your first Solidity contract on Rome in under 5 minutes. - [Key Concepts](https://docs.rome.builders/getting-started/key-concepts.md): Essential Solana and Rome EVM terminology for developers β€” programs, accounts, PDAs, CPI, SPL tokens, and atomic vs. iterative execution. - [Overview](https://docs.rome.builders/networks/networks.md): Public Rome chains β€” chain IDs, RPC endpoints, explorers, and gas tokens. - [Martius (testnet)](https://docs.rome.builders/networks/martius.md): Rome Martius β€” the public testnet chain (chain ID 121214). - [Hadrian (devnet)](https://docs.rome.builders/networks/hadrian.md): Rome Hadrian β€” the public devnet chain (chain ID 200010). - [Overview](https://docs.rome.builders/apps-on-rome/apps.md): Live applications running on Rome β€” DeFi, explorers, bridges, and portals. - [Rome Bridge](https://docs.rome.builders/apps-on-rome/bridge-api.md): Rome Bridge β€” a standalone bridge and an integrable API, with no custody keys. - [Oracle Gateway portal](https://docs.rome.builders/apps-on-rome/oracle-gateway.md): The Oracle Gateway portal β€” register price feeds and configure consumers per chain. - [Via Explorer](https://docs.rome.builders/apps-on-rome/via.md): Via β€” the cross-VM block explorer for Rome chains. - [Execution Model](https://docs.rome.builders/core-concepts/execution-model.md): How Rome EVM processes Ethereum transactions on Solana β€” proxy emulation, atomic (VmAt) vs. iterative (VmIt) modes, and the full transaction lifecycle. - [Compute Budget](https://docs.rome.builders/core-concepts/compute-budget.md): Solana compute unit (CU) costs for Rome EVM operations β€” atomic vs. iterative budgets and how to design CU-efficient Solidity contracts. - [Constraints](https://docs.rome.builders/core-concepts/constraints.md): Limits when building on Rome EVM β€” Solana transaction size, ~1.4M CU budget, account caps, storage layout, and how Rome works around each. - [Token Interop](https://docs.rome.builders/core-concepts/token-interop.md): How ERC-20 and SPL tokens are the same underlying account on Rome. - [Choose your core](https://docs.rome.builders/core-concepts/choose-your-core.md): A dual-lane app can hold its core logic on the Solidity side or the native Solana side. It's a judgment call β€” weigh what matters for your app. - [Rome SDK](https://docs.rome.builders/products/rome-sdk.md): Typed Solidity interfaces for calling Solana programs from EVM contracts, plus the Rust SDK behind Rome's off-chain services. - [Rome CLI + MCP](https://docs.rome.builders/products/rome-cli.md): The Rome developer CLI and MCP server β€” grounded chain facts, the right build pattern, and the Rome-unique actions (fund, deploy, verify) for a human or an AI agent. - [App Sovereignty](https://docs.rome.builders/products/app-sovereignty.md): Launch your own sovereign EVM chain on Solana β€” custom chain ID, any SPL token as gas, and gas revenue that accrues to your app's treasury. - [Oracle Gateway](https://docs.rome.builders/products/oracle-gateway.md): Pyth and Switchboard price feeds behind Chainlink's AggregatorV3Interface. - [Deploy Solidity Contracts](https://docs.rome.builders/developer-guides/deploy-solidity.md): Deploy Solidity smart contracts on Solana with Hardhat or Foundry β€” Rome network configuration, funded accounts, and step-by-step deployment. - [Verify Contracts](https://docs.rome.builders/developer-guides/verify-contracts.md): Verify Solidity contract source on Rome via the hosted Sourcify service β€” standard forge verify-contract and hardhat-verify flows, badges on the Via explorer. - [WebSocket Subscriptions](https://docs.rome.builders/developer-guides/websocket-subscriptions.md): Subscribe to Rome EVM events over WebSocket β€” eth\_subscribe with newHeads and logs, working out of the box with ethers and viem providers. - [Call Solana from EVM](https://docs.rome.builders/developer-guides/call-solana-from-evm.md): Call Solana programs from Solidity via Rome's CPI and helper precompiles. - [Call EVM from Solana](https://docs.rome.builders/developer-guides/call-evm-from-solana.md): Let a Solana wallet drive EVM contracts on Rome β€” no Ethereum key. The wallet signs, and its transaction goes to Solana. - [Build a dual-lane app](https://docs.rome.builders/developer-guides/dual-lane-app.md): A step-by-step walkthrough of a dual-lane app β€” one Solidity contract used by both a MetaMask user and a Phantom (Solana) user, with exactly what happens at each step. - [From home: reach Rome from another chain](https://docs.rome.builders/developer-guides/from-home.md): Let users on another chain reach your Rome app without leaving home β€” bring assets in, act, take them back out. - [JSON-RPC Support](https://docs.rome.builders/reference/json-rpc.md): Ethereum JSON-RPC methods supported by Rome EVM endpoints, plus Rome-specific behaviors β€” for Foundry, Hardhat, ethers, viem, and MetaMask. - [Contract Addresses](https://docs.rome.builders/reference/contract-addresses.md): Precompiles, program IDs, and per-chain deployed contract addresses. - [Known Limitations](https://docs.rome.builders/security/known-limitations.md): Current Rome EVM constraints and their implications β€” unsupported opcodes, storage account layout, CU ceilings, CPI depth, and oracle limits. - [Responsible Disclosure](https://docs.rome.builders/security/responsible-disclosure.md): How to report a security vulnerability in Rome Protocol responsibly β€” contact channels, what to include, and disclosure guidelines. - [DeFi Protocols](https://docs.rome.builders/use-cases/defi-protocols.md): Integration patterns for EVM DeFi on Rome β€” lending with Solana oracles, composing Jupiter and Kamino from Solidity, and shared-liquidity pools. - [Faucets](https://docs.rome.builders/resources/faucets.md): Test-token faucets for Rome and every chain the bridge supports. - [FAQ](https://docs.rome.builders/resources/faq.md): Frequently asked questions about Rome Protocol β€” is Rome a bridge or a rollup, Solidity compatibility, oracles, gas tokens, and Solana interop. - [Glossary](https://docs.rome.builders/resources/glossary.md): Definitions of Rome and Solana terms used across these docs β€” ATA, CPI, PDA, VmAt/VmIt, holder accounts, SPL tokens, and more. - [Community](https://docs.rome.builders/resources/community.md): Where to get help building on Rome Protocol β€” Discord, Telegram, GitHub, Rome Academy courses, and the blog. --- # 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, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on a page URL with the `ask` query parameter: ``` GET https://docs.rome.builders/readme.md?ask= ``` The question should be specific, self-contained, and written in natural language. 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.