> 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/rubicon.md). # Rubicon (mainnet) Rome Rubicon — the public mainnet chain (chain ID 7531). Settles on Solana mainnet, gas is real USDC. Rubicon is Rome's public mainnet chain. It is an EVM chain that executes inside the Rome program on Solana mainnet and settles there. Gas is paid in USDC, and that USDC is real money. There is no faucet. Rubicon is in the public [Rome registry](https://github.com/rome-protocol/rome-registry) from v0.3.0. `create-rome-app` and `rome-cli` still pin registry v0.2.0, which has no Rubicon entry, so they cannot target it. For those tools, fill the values by hand from this page. ## Network details | Field | Value | | --------------------- | --------------------------------------------------------------------------------------------------------- | | Chain ID | `7531` | | RPC URL | `https://rubicon.mainnet.romeprotocol.xyz/` | | WebSocket | `wss://rubicon.mainnet.romeprotocol.xyz/` | | Explorer | [via-rubicon.mainnet.romeprotocol.xyz](https://via-rubicon.mainnet.romeprotocol.xyz/) | | Contract verification | `https://verify.mainnet.romeprotocol.xyz` (see [Verify Contracts](/developer-guides/verify-contracts.md)) | | Settles on | Solana mainnet | | Rome program ID | `RomePq9X3iAoTr813HR7uRarafFDUJty6GdiEceYpzX` | | Gas token | USDC, 18 decimals on the EVM side | | Solana USDC mint | `EPjFWdd5AufqSSqeM2qN1xzybapC8G4wEGGkZwyTDt1v` (6 decimals) | Add it to a wallet by entering the values above manually (Settings → Networks → Add network), with the currency symbol `USDC`. WebSocket subscriptions are served on the same host as the HTTPS RPC. ## Gas Gas is USDC. The price is read the usual way, with `eth_gasPrice`. Rubicon's price is higher than on Hadrian and it varies, so do not copy a number from this page. As a comparison, a read of `eth_gasPrice` on Rubicon returned about 104.6 gwei while Hadrian returned about 10.4 gwei, roughly ten times less. The quickstart contract, built without the optimizer as `npx hardhat run` builds it, estimates about 14 million gas on Rubicon, so a first deploy costs about 1.5 USDC at that price (about 9.7 million gas and 1 USDC with the optimizer on). Use `eth_estimateGas` for every write and never hardcode 21,000. Most of a write's cost is creating Solana accounts (a never-used recipient, a new token account, a deployed contract), and the estimate includes it. For calls into Solana programs, add a margin, as the SDK's 1.3x pad does, and set a gas ceiling yourself if the estimate itself reverts. See [JSON-RPC Support](/reference/json-rpc.md) for the measured numbers. ## Fund a wallet Bring USDC in with the [Rome Bridge on mainnet](https://bridge-api.mainnet.romeprotocol.xyz/). At the time of writing its route list for Rubicon has USDC over CCTP with Ethereum, Base, Arbitrum, Polygon, Avalanche, Monad and OP, and SOL and USDC from a Solana wallet. There is no ETH route. The live list is at [`/v1/routes`](https://bridge-api.mainnet.romeprotocol.xyz/v1/routes). By default, USDC that arrives through the bridge lands as gas. The bridge page can deliver it as the wUSDC token instead. Details of the bridge are on the [Rome Bridge](/apps-on-rome/bridge-api.md) page, and [Faucets](/resources/faucets.md) says what applies on mainnet. ## Contracts and wrappers Rubicon's wrapper addresses are listed in [Per-network wrapper addresses](https://docs.rome.builders/networks/pages/QQmOT5sDIQcUnRUM4fU6#id-4.-per-network-wrapper-addresses) and on [Contract Addresses](/reference/contract-addresses.md). They are not copied here so that there is one place to keep current. ## Calling Rubicon from a Solana wallet The Solana lane (a Solana wallet calling your EVM contract) needs two things on mainnet. * **A Solana mainnet RPC.** The SDK sends the signed Solana transaction to the Solana RPC you give it, not to the Rome proxy. Use an RPC for Solana mainnet from a provider you have an account with. * **A wallet that signs Solana v1 transactions.** Every Solana-lane call is a v1 transaction. Check that your wallet signs them before you build on it. On Hadrian, Solflare signs them and Phantom does not yet. Whether a given wallet signs them against Rubicon is not covered here, so test yours first. The registry has Rubicon from v0.3.0, so you can read the SDK's `deps` from it, or fill them by hand with the values from the table above. The field-by-field map is in [Open your contract to Solana users](https://docs.rome.builders/networks/pages/QQmOT5sDIQcUnRUM4fU6#id-3.-let-a-solana-wallet-call-it). ## Before you deploy * Develop and test on [Hadrian](/networks/hadrian.md). Rubicon runs the same EVM, so the same artifacts deploy, with the chain ID and the wrapper addresses swapped. * Every transaction on Rubicon spends real USDC. Run the full round trip once with a small amount before you announce anything. * A user who moves wrapper tokens needs the one-time wrapper grant described in [Token Interop](/core-concepts/token-interop.md#one-time-grant-per-wallet), on Rubicon as on every other chain. --- # 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/rubicon.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.