For the complete documentation index, see llms.txt. This page is also available as Markdown.

Rome Bridge

Rome Bridge — a standalone bridge and an integrable API, with no custody keys.

Rome Bridge is two things: a standalone bridge across six chains, and a Bridge API any app integrates to embed bridging in its own UX. It moves assets over CCTP v2 (USDC), Wormhole (ETH and generic assets), and Solana-native rails.

It holds no custody keys — settlement always requires the user's own signature, never the service's. The API orchestrates and can sponsor fees; the real bridge is on-chain.

Supported chains and assets

Inbound to Rome (Martius, Hadrian), across four rails — cctp, wormhole, spl-bridge, native:

Asset
Rail
Source chains

USDC

CCTP

Ethereum Sepolia, Arbitrum Sepolia, Base Sepolia, Polygon Amoy, Avalanche Fuji, Monad Testnet

ETH

Wormhole

Ethereum Sepolia

SPL / native

spl-bridge / native

Solana

The live set is always in /v1/chains. Need test tokens? See Faucets.

Use it standalone

Open the bridge UI: bridge-api.devnet.romeprotocol.xyz. The ?chain= parameter selects the destination Rome chain.

Integrate the API

The API is public. List supported chains and rails:

curl https://bridge-api.devnet.romeprotocol.xyz/v1/chains

Quote and route requests take a CAIP-2 sourceChain. See the endpoint responses for the current rail set and required fields.

How settlement works

The off-chain API is an orchestrator and fee sponsor only. Inbound transfers settle on-chain trustlessly via a user-signed authorization; outbound withdrawals go through the on-chain bridge contract. No step debits user funds without the user's signature.

Last updated

Was this helpful?