Supported chains

Supported chains are provider-dependent and should be discovered from the running TEE rather than hard-coded in an integration.

curl $BASE_URL/api/relay/chains

The response contains chainId, name, displayName, an optional logoUrl, and an optional vmType.

Relay mode

Relay is the default bridge provider. The discovery endpoint returns chains that Relay marks as deposit-address-enabled and not disabled. It can include EVM and non-EVM VM families.

List the bridgeable currencies for a selected chain:

curl "$BASE_URL/api/relay/tokens?chainId=8453"
curl "$BASE_URL/api/relay/tokens?chainId=8453&search=USDC"

Each currency includes its authoritative address, symbol, decimals, and available display metadata. A successful end-to-end route still depends on liquidity and on the source, hub, and destination currencies all resolving at quote time.

CCTP mode

When BRIDGE_PROVIDER=cctp, discovery is restricted to the configured CCTP network class and returns USDC as the only token.

Configured mainnets:

Ethereum · 1Base · 8453Arbitrum · 42161

Configured testnets:

Ethereum Sepolia · 11155111Base Sepolia · 84532Arbitrum Sepolia · 421614OP Sepolia · 11155420Polygon Amoy · 80002Unichain Sepolia · 1301World Chain Sepolia · 4801Sei Atlantic-2 · 1328Arc Testnet · 5042002

SDK chain constants

The current @erebuz/sdk exports only localhost, sepolia, and mainnet from SUPPORTED_CHAINS. Those constants are shared configuration helpers, not the router's live coverage list. A typed SDK wrapper around dynamic routing coverage is Coming soon.