> 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/resources/faucets.md).

# Faucets

Test-token faucets for Rome and every chain the bridge supports.

Rome's test chains use test USDC; **Rubicon mainnet uses real USDC** — bring it in with the [Rome Bridge](https://bridge-api.mainnet.romeprotocol.xyz/) (see [Rubicon](/networks/rubicon.md)), there is no faucet. The faucets below are for the test chains.

## Fund a Rome wallet

Every Rome chain's gas token is **USDC** (Circle) — there is **no Rome faucet**. You fund a wallet by **bridging USDC into Rome** from a chain where you can get test USDC: an EVM testnet or Solana Devnet. That's the one manual step; after it, deploy and transact normally. Get the USDC and bridge it in using the sources below.

## From Solana Devnet

A tester who works from a Solana wallet needs two things on Solana Devnet, both from faucets:

* **Devnet USDC** for Hadrian: the [Circle faucet](https://faucet.circle.com/), with the network set to Solana Devnet. Hadrian uses the mint `4zMMC9srt5Ri5X14GAgXhaHii3GnPAEERYPJgZJDncDU`, so this is the same USDC the chain uses as its gas token.
* **Devnet SOL** for Solana transaction fees: the [Solana faucet](https://faucet.solana.com/). SOL is not the gas token; Rome chains charge gas in USDC.

What you do next depends on what you are testing.

* **Calling contracts from a Solana wallet (the Solana lane).** The USDC and SOL stay in that Solana wallet. The app's fund step moves the USDC into the call when it is needed, so there is nothing to bridge. See [Open your contract to Solana users](/developer-guides/open-to-solana-users.md).
* **Funding an EVM wallet from Solana.** Bridge the USDC with the [Rome Bridge](/apps-on-rome/bridge-api.md) using its Solana route, with the EVM wallet's address as the recipient. The bridge then asks that EVM wallet to sign a claim transaction on Rome, which turns the USDC into gas. The live routes are at [`/v1/routes`](https://bridge-api.devnet.romeprotocol.xyz/v1/routes).

## Bridge in from another chain

The [Rome Bridge](/apps-on-rome/bridge-api.md) moves **USDC** (via CCTP) and **ETH** (via Wormhole) into Rome from six EVM source chains, and USDC and SOL from Solana Devnet (above). Fund the source chain first, then bridge.

### USDC — all source chains

The [Circle faucet](https://faucet.circle.com/) mints test USDC on every CCTP source chain — select the chain in the faucet.

### Native gas — per source chain

You also need the source chain's native token to pay its own bridge transaction:

| Source chain     | Chain ID | Native | Faucet                                                                                   |
| ---------------- | -------- | ------ | ---------------------------------------------------------------------------------------- |
| Ethereum Sepolia | 11155111 | ETH    | [Google Cloud faucet](https://cloud.google.com/application/web3/faucet/ethereum/sepolia) |
| Arbitrum Sepolia | 421614   | ETH    | [Alchemy faucet](https://www.alchemy.com/faucets/arbitrum-sepolia)                       |
| Base Sepolia     | 84532    | ETH    | [Alchemy faucet](https://www.alchemy.com/faucets/base-sepolia)                           |
| Polygon Amoy     | 80002    | POL    | [Polygon faucet](https://faucet.polygon.technology/)                                     |
| Avalanche Fuji   | 43113    | AVAX   | [Avalanche faucet](https://faucet.avax.network/)                                         |
| Monad Testnet    | 10143    | MON    | [Monad faucet](https://faucet.monad.xyz/)                                                |

ETH bridged via Wormhole comes from Ethereum Sepolia (use the Sepolia ETH faucet above). These are third-party faucets and may rate-limit or change.

## What's Next

* [Networks](/networks/networks.md) — connect to Rubicon or Hadrian
* [Rome Bridge](/apps-on-rome/bridge-api.md) — the bridge and its API


---

# 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/resources/faucets.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.