Category

Bridges & Onramps on Arc · 10

Getting USDC onto Arc is the first thing almost everyone does, which makes this the category where accuracy matters most and where impersonation clusters hardest. Circle's own rails — CCTP, which moves USDC by burn-and-mint, and Gateway, which provides a chain-agnostic balance — are the canonical routes.

Third-party interoperability protocols have been named in ecosystem coverage, but as of 2 September 2026 Arc's own developer documentation lists no third-party bridging vendors, and the official mainnet RPC and explorer URLs had not been published. Entries record what each provider actually supports and at what scope. Step-by-step bridging instructions are not ours — those sit with Meme Central.

Filters
#ProjectWhat it builds on ArcRoleStatusLinksChecked

Questions

Is native USDC different from a bridged token?

Yes. Native issuance and canonical crosschain transfer avoid the wrapped-asset risk that a third-party bridge introduces. The entry sentence states which one a route uses.

Do you assess bridge security?

No. We record deployment, contract verification and published audits with dates and links. Read them yourself before moving funds.

How is status decided?

Status reflects what we observed on the date shown, not what a project announced. Every entry carries a dated source you can open and check yourself. Live can become Inactive if activity stops.