> 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/apps-on-rome/solgate.md).

# Solgate

Solgate — Rome's bridge page on Polygon's AggLayer. Move tokens between Solana wallets and Ethereum, X Layer, Katana and other AggLayer chains, in both directions.

Solgate is Rome's bridge page on Polygon's AggLayer. It moves tokens between Solana wallets and AggLayer EVM chains, in both directions. A token from an EVM chain arrives in a Solana wallet as a real SPL token. A Solana token arrives on an EVM chain as an ERC-20. Solana and the other chain are one market.

Solgate is live on mainnet and on testnet.

| Network | App                                                                          | Rome chain                                                | Chains connected                                  |
| ------- | ---------------------------------------------------------------------------- | --------------------------------------------------------- | ------------------------------------------------- |
| Mainnet | [solgate.romeprotocol.xyz](https://solgate.romeprotocol.xyz)                 | [Rubicon](https://docs.rome.builders/networks/rubicon.md) | Ethereum, X Layer, Katana                         |
| Testnet | [solgate.testnet.romeprotocol.xyz](https://solgate.testnet.romeprotocol.xyz) | [Hadrian](https://docs.rome.builders/networks/hadrian.md) | Ethereum Sepolia, Katana Bokuto, Billions Testnet |

## How a token moves

```
EVM chain to Solana
  token on its chain ──► settles on AggLayer ──► Claim ──► SPL token in your Solana wallet

Solana to EVM chain
  SPL token in your Solana wallet ──► send ──► settles on AggLayer ──► Claim ──► ERC-20 on the chain
```

On the Solana side Solgate works with the Rome chain, which runs inside Solana. The app's chain list names it Rome Rubicon on mainnet and Rome Hadrian on testnet.

* **From an EVM chain to Solana.** The transfer settles on AggLayer. It then waits under Claim, and Claim puts it in your Solana wallet, usually with one approval.
* **From Solana to an EVM chain.** You send from your Solana wallet. The transfer settles on AggLayer, then waits under Claim. You claim on the destination chain with your EVM wallet.
* **A token born on another chain has to be made bridgeable to Solana first.** On mainnet Rome lists the tokens. On testnet anyone can do it. See [Tokens](https://docs.rome.builders/apps-on-rome/solgate/tokens.md).

## Chains and times

Solana · via Rome is the Solana side. The live list is `GET /v1/chains` on the app's address: [mainnet](https://solgate.romeprotocol.xyz/v1/chains) · [testnet](https://solgate.testnet.romeprotocol.xyz/v1/chains).

| Chain (mainnet) | Time to Solana    | Time from Solana |
| --------------- | ----------------- | ---------------- |
| Ethereum        | about 120 seconds | about 6 minutes  |
| X Layer         | not estimated     | about 18 minutes |
| Katana          | about 65 minutes  | about 4 minutes  |

| Chain (testnet)  | Time to Solana    | Time from Solana |
| ---------------- | ----------------- | ---------------- |
| Ethereum Sepolia | about 130 seconds | about 5 minutes  |
| Katana Bokuto    | about 39 minutes  | about 8 minutes  |
| Billions Testnet | not estimated     | not estimated    |

A transfer waits for the source chain's next update on AggLayer, so a time is a typical value and moves with each chain's schedule. Where a chain shows "not estimated", the app shows no countdown.

ETH sent from Ethereum to an EVM wallet on the Rome chain above a small minimum value arrives on its own, on mainnet and on testnet. See [Auto-claim](https://docs.rome.builders/apps-on-rome/solgate/using.md#auto-claim).

## The pages

* [**Using Solgate**](https://docs.rome.builders/apps-on-rome/solgate/using.md) — connect, send, claim, the Tokens tab, Activity filters, the Arrived card, wallets, fees and times.
* [**Tokens**](https://docs.rome.builders/apps-on-rome/solgate/tokens.md) — which tokens can move, how they are named, tokens that move by their issuer's own bridge, tokens that cannot move.
* [**Building on Solgate**](https://docs.rome.builders/apps-on-rome/solgate/builders.md) — what crosses, make your token bridgeable to Solana, Verified and Unverified, Add to wallet, the public API.
* [**Messaging on Solgate**](https://docs.rome.builders/apps-on-rome/solgate/messaging.md) — not yet available on mainnet.
* [**Solgate ideas**](https://docs.rome.builders/apps-on-rome/solgate/ideas.md) — ten things to build.
* [**Build on Solgate**](https://docs.rome.builders/rome-academy/13-build-on-solgate.md) — the Academy lesson that teaches the whole route.
* [**FAQ**](https://docs.rome.builders/apps-on-rome/solgate/faq.md)

Enabled by Rome.


---

# 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/apps-on-rome/solgate.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.
