> 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/products/app-sovereignty.md).

# App Sovereignty

App Sovereignty lets any Solana application launch its own EVM environment with a custom chain ID, custom gas token, and gas revenue that flows to the application — not a shared protocol.

## Overview

Each application on Rome gets a sovereign EVM instance:

* **Own chain ID** — your app is its own chain
* **Own gas token** — any SPL token (your project token, USDC, SOL)
* **Gas revenue** — all transaction fees accrue to your treasury
* **Full EVM tooling** — your users connect MetaMask, your devs use Hardhat/Foundry
* **Single state** — EVM users and Solana users share the same application state and liquidity

## How It Works

1. **Register your chain** — submit a chain ID and gas token (any SPL mint, or native SOL) through the [registration portal](https://register.devnet.romeprotocol.xyz)
2. **Deploy infrastructure** — Rome Proxy + Hercules (single-state mode) or add OP-Geth for full Ethereum RPC compatibility
3. **Deploy contracts** — standard Solidity deployment with Hardhat or Foundry
4. **Users connect** — MetaMask with your chain ID, or any EVM wallet

## Gas Token Pricing

Custom gas tokens are priced via Meteora DAMM V1 pools. The Proxy configuration specifies a `price_manager` that reads the pool to convert between your gas token and SOL for underlying Solana transaction fees.

```yaml
# Proxy config for custom gas token
price_manager:
  type: "meteora_damm_v1_pool"
  pool_address: "YOUR_METEORA_POOL_ADDRESS"
```

## Deployment Modes

| Mode         | Components                        | Use Case                                                |
| ------------ | --------------------------------- | ------------------------------------------------------- |
| Single-state | Proxy + Hercules                  | Simpler, lower latency, direct Solana interaction       |
| OP-Geth      | Proxy + Hercules + OP-Geth + Rhea | Full Ethereum RPC compatibility, block explorer support |

## Use Case: Prediction Market Launches EVM Chain

```
Orra (Solana prediction market) wants EVM users:
  1. Rome deploys Orra's sovereign EVM with ORRA token as gas
  2. EVM users connect MetaMask, bridge USDC, buy prediction shares
  3. Under the hood: rUSDC (ERC-20) → unwrap to SPL → Orra CPI → buy shares
  4. Orra earns gas fees in ORRA token from every EVM transaction
  5. Single state: Solana users and EVM users see same markets, same liquidity
```

## Status

**Live** — active product with partners.

## What's Next

* [Architecture](/getting-started/architecture.md) — how Rome EVM works under the hood
* [Quickstart](/getting-started/quickstart.md) — deploy your first contract
* [Deploy Solidity](/developer-guides/deploy-solidity.md) — deployment guide for Hardhat and Foundry


---

# 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 current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.rome.builders/products/app-sovereignty.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.