Supported chains

The short version: 14 EVM chains, 4 of them Ophis-operated (Optimism, Unichain, Robinhood Chain, and Arc), plus Solana, Bitcoin, Monad, Hyperliquid, X Layer, Sui, Tron, Starknet, and Zcash as NEAR sources and destinations in the standalone app. The full table with chain IDs and settlement mode:

Chain	Chain ID	Settlement
Arbitrum One	42161	Batch-auction settlement
Arc	5042	Ophis-operated
Avalanche	43114	Batch-auction settlement
Base	8453	Batch-auction settlement
BNB Smart Chain	56	Batch-auction settlement
Ethereum	1	Batch-auction settlement
Gnosis Chain	100	Batch-auction settlement
Ink	57073	Batch-auction settlement
Linea	59144	Batch-auction settlement
Optimism	10	Ophis-operated
Plasma	9745	Batch-auction settlement
Polygon	137	Batch-auction settlement
Robinhood Chain	4663	Ophis-operated
Unichain	130	Ophis-operated
Solana	n/a	NEAR source deposit or destination; route-dependent
Bitcoin	n/a	NEAR source deposit or destination; route-dependent
Monad	n/a	NEAR source deposit or destination; route-dependent
Hyperliquid	n/a	NEAR source deposit or destination; route-dependent
X Layer	n/a	NEAR source deposit or destination; route-dependent
Sui	n/a	NEAR source deposit or destination; route-dependent
Tron	n/a	NEAR source deposit or destination; route-dependent
Starknet	n/a	NEAR source deposit or destination; route-dependent
Zcash	n/a	NEAR source deposit or destination; route-dependent

Which chains does Ophis support?

Ophis covers 14 EVM chains, with Optimism, Unichain, Robinhood Chain, and Arc as its operated sovereign networks, and supports Solana, Bitcoin, Monad, Hyperliquid, X Layer, Sui, Tron, Starknet, and Zcash as additional sources and destinations through NEAR Intents in the standalone app. External-source routes use a deposit flow, not an EVM orderbook.

What does Ophis-operated mean?

On Optimism, Unichain, Robinhood Chain, and Arc, batch-auction swaps use Ophis's own settlement contracts with chain-specific fee handling. Arc uses the same capped backend improvement policy for in-market orders; see the pricing page. Resolve supported signing domains and orderbook hosts through @ophis/sdk or MCP list_chains. SDK v0.4.5 and hosted MCP include Arc (5042); do not reuse another chain's address. Bridge routes have separate costs.

How do external-source and cross-chain swaps work?

Select a source and destination in the same token pickers. For an additional NEAR source, review the quote and source-chain refund address, then send the specified deposit from your source wallet, including any required memo. Keep the transfer record until delivery or refund. Asset and provider availability gate every route; the list does not promise every pair in both directions. Hyperliquid means Hypercore spot balances, and Zcash requires a transparent t1/t3 address. Arc uses separate Circle routes.

Is there a testnet?

Yes. The Sepolia testnet is available for integration testing. This page lists production chains only.

For Arc, see how to swap on Arc. For Stock Token markets, see swapping on Robinhood Chain. Token support and executable liquidity must be checked in the live quote.

For agents and integrators

SDK v0.4.5 and the hosted MCP server cover the EVM chains above, including Arc (5042). External NEAR deposits are a separate app flow, not orders built by these SDK/MCP tools. Bridge coverage remains route-specific; settled Arc trades are indexed for routed volume and referral attribution.

SDK v0.4.3 already supports Arc trading. Upgrade to v0.4.4 to include referral codes on Arc orders.

npm install @ophis/sdk@0.4.5

Before every order submission, register the actual order owner for trade indexing and the USDG trade-rewards campaign. Registering only when the wallet connects is not sufficient. If a Safe owns the order, register the Safe address, not its curator's or signer's wallet.

await enrollOphisTrader(orderOwner, { blocking: true })

If registration fails, retry registration before submitting the order. Do not submit an already accepted order again just to fix registration. Registration alone does not establish partner affiliation: keep appCode set to 'ophis' and include your valid referral code separately in the order's metadata. See the partner integration guide for the complete flow.

Create referral codes in the swap app. MCP clients pass referrerCode to build_order. Track routed volume by appCode in the earnings report at rebates.ophis.fi/earnings/<appCode>. View the USDG campaign on the trade rewards page.

The machine-readable per-chain contract-pinning policy (settlement addresses, vault relayers, EIP-712 domains, orderbook hosts) ships in the Ophis agent skill for the chains listed in that policy. For all supported EVM chains, including Arc, the @ophis/sdk v0.4.5 helpers resolve the correct settlement domain per chain, and the MCP server exposes the same data through the list_chains tool. Fee detail per chain lives on the pricing page.

Arc bridges and liquidity venues

Arc uses USDC for gas. The app includes Circle routes where both networks and assets have configured mappings; consult the linked coverage guide and the live quote. Eligible routes are exact-input, same-wallet transfers from an EOA without smart-account code. Ethereum WBTC conversion follows Ethereum WBTC → Ethereum cirBTC → Arc cirBTC; it is not a native Bitcoin bridge or a single atomic swap.

Arc routing lanes are configured for Uniswap v3, KyberSwap, Archery, Aero, Uniswap v4 and SushiSwap v3. A venue name identifies liquidity used by a lane; the operator can still be Ophis. Configuration does not guarantee a live quote or fill for every pair. See networks, assets and feature availability for bridge recovery, confidentiality and institutional-feature boundaries.