Arc ecosystem map: the ten categories on Circle's Arc and who is in each

The ecosystem around Circle's Arc sorts cleanly into ten categories, and knowing which one your question belongs to is most of the work. A treasurer choosing a payout provider, a developer choosing an RPC endpoint and a compliance officer choosing a screening vendor are asking three unrelated questions that "the Arc ecosystem" flattens into one. This page is the map: what each category covers, three to five named examples, and where the full list for that category lives. It is deliberately not a directory.

Two numbers, and the difference between them. Circle's own ecosystem page lists 100-plus projects with no status and no dates. Counts on this page are drawn from the independent Arc directory, checked 9 September 2026, which carries 178 projects with a dated status and a source on each. The second number is smaller and more useful, because a name in an ecosystem listing tells you a company has a relationship with Circle, not that anything runs.

Every name below is sourced to a primary document — Circle's 5 August 2026 founding-validator and integrations press release, Circle's own Arc developer documentation, or a company's own published statement. Nothing is live on Arc mainnet before 16 September 2026, so read every entry here as announced, on testnet, or exploratory.

Payments and payouts

Payment service providers, remittance operators, payout and payroll platforms, merchant acceptance and card programmes. Almost all of these are existing businesses adding Arc as a settlement rail for customers they already have, rather than protocols deploying contracts.

Named examples: MoneyGram (remittance; also a founding validator), Rain and Wirex (card issuing), Thunes (cross-border network), PhotonPay (multi-currency accounts, confirmed testnet participation in November 2025).

This is the category with the most companies and the least crypto in it, which is also why it is the one where "does this actually work on Arc" is hardest to eyeball from the outside — the full list, with the evidence behind each provider's status, is at payments and payouts on Circle's Arc.

Banks and enterprises

Banks, asset managers, card networks and large corporates with a named Arc relationship. This is where the founding-validator distinction lives, and it is the single easiest thing to get wrong about Arc: eleven institutions were named as founding validators on 5 August 2026, and running a validator is a mark on top of whatever the institution's actual role is, not a role in itself.

Named examples: BlackRock, DTCC, Visa, Mastercard, Standard Chartered. BNY is named in the same release as "exploring integrations", which is softer language and should be read as such.

Full list: banks and enterprises on Arc.

Stablecoins and tokenized assets

Whoever issues a token natively on the chain, plus the platforms that structure and administer tokenized instruments. Circle issues both native stablecoins, operates the chain and denominates gas in USDC, which is a concentration worth understanding before you build a business on top of it.

Named examples: USDC and EURC (Circle), BlackRock's BUIDL fund, which Circle's release says is expected to deploy on Arc, and DTCC's tokenization of DTC-custodied assets, which the same release dates to the second half of 2027.

Full list: stablecoins and tokenized assets on the Arc blockchain.

Exchanges and trading

Three different businesses sit here: exchanges enabling Arc deposits and withdrawals, on-chain venues running their own contracts, and market makers routing flow without holding it.

Named examples: Kraken, Upbit and Binance Wallet (exchange-side USDC access), Uniswap and Aerodrome (on-chain venues), plus market makers Galaxy, FalconX, GSR and Keyrock.

Full list: exchanges and trading on Circle's Arc.

DeFi and credit

Lending markets, private credit and structured products. This is a thinner category than the coverage suggests: Circle's release names four protocols collectively for providing "liquid markets for borrowing, trading, and onchain capital deployment" and gives no per-protocol detail.

Named examples: Aave and Morpho on the lending side; Uniswap and Aerodrome are named in the same group but sit under exchanges and trading here.

Full list: DeFi and credit on Circle's Arc.

Wallets and custody

Consumer wallets, embedded-wallet infrastructure sold to developers, and institutional custodians — three product classes that share a category and almost nothing else.

Named examples: MetaMask, Ledger and Binance Wallet (consumer), Fireblocks (institutional custody), Blockradar (wallet infrastructure, named in Circle's own Arc account-abstraction documentation).

"Supports Arc" is a spectrum rather than a checkbox, and the thing that separates a wallet that technically connects from one that works is whether it renders a USDC-denominated gas fee correctly — see wallets and custody on the Arc blockchain for where each wallet actually sits.

Bridges and on-ramps

Getting USDC onto Arc, and getting fiat into USDC in the first place. Circle's own rails are the canonical routes and the only ones with published Arc-specific technical detail.

Named examples: CCTP, Circle's burn-and-mint transfer protocol, with Arc assigned its own domain; Circle Gateway, a unified cross-chain USDC balance rather than a bridge; Crossmint, which announced an Arc partnership covering on-ramps; Axelar, whose core development team Circle acquired.

Full list: bridges and on-ramps on the Arc blockchain.

Developer infrastructure

RPC endpoints, oracles, indexers, account abstraction and developer tooling. The best-documented category on Arc, because Circle publishes named vendor lists in its own developer documentation — which means "listed in Arc's docs" is a real, primary source, and also means only that Circle names the vendor, not that a mainnet deployment exists.

Named examples: Alchemy, QuickNode, dRPC and Blockdaemon (RPC), Chainlink and RedStone (oracles), Privy and Dynamic (embedded wallets and account abstraction).

Full list: developer infrastructure on the Arc blockchain.

Compliance and analytics

Transaction monitoring, sanctions and wallet screening, blockchain intelligence and risk data — what a regulated business needs in place before it moves money on a new chain. A permissioned validator set is not a compliance control, and a vendor listing is not an attestation that any obligation is met.

Named examples: Chainalysis, Elliptic and TRM Labs, all three named directly in Circle's own Arc compliance-vendors documentation.

Full list: compliance and analytics on Circle's Arc.

Launchpads, NFT and meme

The thinnest-evidenced category on the chain, and the gap is the point: Circle's own Arc ecosystem taxonomy has no bucket for launchpads, NFT, meme, gaming or consumer projects at all, so nothing here carries any form of Circle acknowledgement.

Named examples: ArcLaunch, AstraPump, uArc, ArcPunks. Several of these have a landing page and a large volume of syndicated coverage and very little else.

Because nothing in this category is Circle-acknowledged, it is the one where checking before you connect a wallet actually matters — the per-project record of what could and could not be verified is at launchpads, NFT and meme projects on Arc.

What this map deliberately leaves out

Counts per category, status per project and anything resembling a ranking. Those change weekly and belong on pages built to be maintained weekly; this one is built to be right for a month at a time. If you need the current state of a single category, follow its link. If you need the state of a single project, search its name plus "Arc" and check what the project itself has published, not what a listing says about it.