> 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/rome-academy/12-launch-your-own-chain.md).

# 12. Launch your own chain

What App Sovereignty gives you (your own chain id, any SPL token as gas, gas revenue to your app), when it fits, what stays the same and how you start.

Everything so far ran on a shared chain: Hadrian for testing, Rubicon for production. Rome also lets one application run its own chain. This lesson is an overview of that step, and the last lesson of the course.

## What you'll learn

* What App Sovereignty gives your application.
* When your own chain fits, and when an app on Rubicon is enough.
* What stays the same for your developers and users, how you start, and how the gas token is priced.

## Before you start

* Finish [11. Ship to Rubicon](https://docs.rome.builders/rome-academy/11-ship-to-rubicon.md). Ship an app on the shared chain before you consider a chain of your own.
* Skim [4. How Rome runs your code](https://docs.rome.builders/rome-academy/04-how-rome-runs-your-code.md). Your chain runs the same way.

## What you get

App Sovereignty lets a Solana application launch its own EVM environment:

* **Your own chain id.** Your app is its own chain.
* **Your own gas token.** Any SPL token: your project token, USDC or SOL.
* **Gas revenue.** Transaction fees accrue to your treasury, not to a shared protocol.
* **Full EVM tooling.** Users connect MetaMask with your chain id. Developers use Hardhat or Foundry.
* **Shared state.** EVM users and Solana users share the same application state and liquidity.

The product page, [App Sovereignty](https://docs.rome.builders/products/app-sovereignty.md), gives an example: a Solana prediction market that wants EVM users. Its own token pays gas, EVM users reach the market through a contract that calls the Solana program, and the market earns the gas fees.

## When it fits

Most apps do not need their own chain. An app on Rubicon already reaches EVM wallets and Solana wallets, shares liquidity and uses the tools from this course. Your own chain fits when one of these matters to you:

* Your users should pay gas in your token, not in USDC.
* The gas fees your app generates should come to you.
* You want your own chain id, with your app as the whole chain.

## What stays the same

* You deploy Solidity with the same tools.
* Contracts call Solana through the same precompiles, and your Solana program is reached as lesson 8 showed.
* Tokens are the same SPL tokens. Your chain has its own wrapper contracts, so take their addresses from its registry entry, as lesson 11 did for Rubicon.
* The limits are the same, because they come from Solana: the atomic budget, the account cap and the transaction size. See [Constraints](https://docs.rome.builders/core-concepts/constraints.md).

The chain is recorded in the public [Rome registry](https://github.com/rome-protocol/rome-registry) with its chain id, RPC and contract addresses, as [Hadrian](https://docs.rome.builders/networks/hadrian.md) is. What changes is the chain id, the gas token and who earns the fees. Your users hold your token for gas instead of USDC, so plan how they get it.

## How you start

1. **Onboard through the Sovereign Portal.** Rome gives you access to the portal, where you set your chain id and gas token, any SPL mint. The [App Sovereignty](https://docs.rome.builders/products/app-sovereignty.md) page links it.
2. **Rome brings up the chain.** The Rome team provisions and operates the chain's infrastructure. You do not run it.
3. **Deploy contracts.** Standard Solidity deployment, as in [lesson 3](https://docs.rome.builders/rome-academy/03-first-contract-on-hadrian.md).
4. **Users connect.** MetaMask with your chain id, or any EVM wallet.

## How the gas token is priced

Solana charges its fees in SOL, and Rome counts each gas unit as one lamport of Solana cost. Your users pay in your token, so the chain needs a price that converts between your token and SOL. The usual source is a Meteora liquidity pool: the proxy reads the pool to convert between your gas token and SOL. A price feed and a fixed price are other sources. See [Gas and pricing](https://docs.rome.builders/getting-started-1/architecture.md#gas-and-pricing) and [Gas token pricing](https://docs.rome.builders/products/app-sovereignty.md#gas-token-pricing).

## Status

App Sovereignty is live: an active product with partners.

## Check yourself

<details>

<summary>1. Your Solana app wants EVM users and nothing else. Do you need your own chain?</summary>

No. An app on Rubicon reaches EVM wallets and Solana wallets. Choose your own chain for your own gas token, the gas revenue or your own chain id.

</details>

<details>

<summary>2. Why does the chain need a price for your token?</summary>

Solana fees are paid in SOL. Rome converts the cost of each transaction from SOL into your gas token, and the price source supplies that conversion.

</details>

## Next

That is the course, with [13. Build on Solgate](https://docs.rome.builders/rome-academy/13-build-on-solgate.md) as an extra lesson on the bridge. For your next project, use these guides and reference apps:

* Put your app in the [Arena](https://arena.mainnet.romeprotocol.xyz), where the Rome team reviews apps for grants.
* Return to the guides for the code behind each lesson. [Build a dual-lane app](https://docs.rome.builders/developer-guides/dual-lane-app.md) and [Integrate a Solana program](https://docs.rome.builders/developer-guides/integrate-solana-program.md) are the two you will reopen most.
* Look up exact values in [Precompiles](https://docs.rome.builders/reference/precompiles.md), [Contract addresses](https://docs.rome.builders/reference/contract-addresses.md) and [Rubicon](https://docs.rome.builders/networks/rubicon.md).
* Read the reference apps in the [rome-protocol](https://github.com/rome-protocol) GitHub organization: rome-dex, aerarium and cardo.
* Ask questions and report problems through the channels on the [Community](https://docs.rome.builders/resources/community.md) page.

[Back to the course map](https://docs.rome.builders/rome-academy/academy.md)


---

# 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/rome-academy/12-launch-your-own-chain.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.
