Arc infrastructure providers: RPC, indexers, oracles, and wallet infra compared

Infrastructure is the least glamorous and most load-bearing layer of any new chain, and Arc's picture as of 2 September 2026 is uneven by design: some providers have shipped public Arc docs you can read today, some have announced partnerships with no technical detail attached, and most of the biggest names in general-purpose Web3 infrastructure have said nothing about Arc at all. This guide separates those three tiers.

What counts as "infrastructure" here, and why it splits into four different trust questions

This category bundles four genuinely different services that happen to sit under one heading:

RPC and node providers — the endpoints an application actually talks to in order to read chain state or submit a transaction. The trust question is uptime, rate limits, and whether the endpoint is pointed at testnet or (eventually) mainnet.

Indexers and data infrastructure — services that turn raw chain state into queryable data. The trust question is coverage and lag: does the indexer actually track Arc's contracts, and how current is it.

Oracles — services that bring off-chain data (most importantly, price data) on-chain. The trust question is which specific feeds are live where, because "an oracle network supports Arc" and "a specific price feed you need is live on Arc" are different claims.

Account-abstraction and embedded-wallet infrastructure — SDKs that let an application spin up or manage user wallets without every user running their own MetaMask. The trust question is whether the SDK has published Arc-specific chain support or whether Arc simply works because it's EVM-compatible and the SDK is chain-agnostic by default.

Compliance and analytics tooling — the transaction-monitoring layer institutions and exchanges rely on — is not part of this category under Built on Arc's taxonomy; see Compliance & Analytics for that coverage, including Chainalysis, Elliptic and TRM Labs.

The reason this split matters for verification: "supports Arc" can mean anything from "we published Arc-specific documentation with contract addresses" down to "our product is EVM-compatible so it technically works, and we haven't said anything about it publicly." Both get marketed the same way. Only the first is something Built on Arc will call confirmed.

The directory

Use the table's status column against these read-throughs, category by category.

RPC: Circle's own node-providers documentation (docs.arc.io/arc/tools/node-providers) names four vendors directly: Alchemy, Blockdaemon, dRPC, and QuickNode, alongside the Arc-operated public testnet endpoint. QuickNode, Alchemy, and dRPC each also publish independent Arc-specific documentation beyond that listing (quicknode.com/docs/arc, a dedicated Arc Testnet RPC page, and a testnet endpoint with archive-node support respectively). GetBlock and Chainstack publish their own Arc documentation without appearing on Circle's official list. All six — Alchemy, Blockdaemon, dRPC, QuickNode, GetBlock, and Chainstack — hold the Serves role (Developer Infrastructure → RPC), and all are testnet-scoped as of 2 September 2026; none publish a mainnet endpoint, because Arc has not published one itself yet. See Built on Arc's dedicated RPC providers comparison for the full breakdown, including Ankr and Infura's absence.

Oracles: Circle's oracle documentation (docs.arc.io/arc/tools/oracles) names five vendors: Chainlink, Chronicle, Pyth, RedStone, and Stork — all five Serves (Developer Infrastructure → Oracles). Chainlink has the strongest confirmation, carrying two further independent sources beyond the documentation listing — a named integration partner in Circle's own founding-validator announcement, and its own ecosystem partner directory listing Arc. Pyth has an additional dated confirmation (July 2026 coverage) that its price feeds are live on Arc's testnet, explicitly scoped to testnet, not mainnet. Chronicle, RedStone, and Stork are confirmed through Circle's documentation listing alone, with no independent corroboration found as of 2 Sep 2026 — see Built on Arc's oracle comparison guide for the full rundown.

Account-abstraction infrastructure: Circle's account-abstraction documentation (docs.arc.io/arc/tools/account-abstraction) names eleven wallet-infrastructure providers, including Crossmint, Privy, Dynamic, and thirdweb — all Serves (Developer Infrastructure → Account abstraction). That listing corrects earlier reporting on this category, which had found no Arc-specific material for Privy or Dynamic and leaned on generic EVM-compatibility instead. Crossmint has separately announced a partnership with Arc covering wallets, onramps, checkout, and compliance tooling, though without a published launch date or technical spec as of 2 Sep 2026. Dynamic and thirdweb each carry a second, independent confirmation beyond the list (a Circle-authored integration tutorial for Dynamic, and thirdweb's own published Arc Testnet documentation); the remaining providers on Circle's list, Privy included, are confirmed through the documentation listing alone as of 2 Sep 2026. See Built on Arc's account abstraction guide for the full eleven-provider breakdown.

Fireblocks, MetaMask, and Ledger are named in the same founding-validator-and-integrations release but sit outside this category under v2: Fireblocks is Serves (Wallets & Custody → Custodians); MetaMask and Ledger are Integrates (Wallets & Custody → Consumer wallets). See Built on Arc's wallet support status guide and custody providers comparison for that half of the picture.

Cloudflare's Web3 Gateway product supports a set of EVM chains through its Ethereum Gateway service; as of 2 Sep 2026 no Arc-specific listing has surfaced in its public documentation or announcements — not yet confirmed (would be Serves — Developer Infrastructure, if an Arc-specific listing is confirmed).

What "confirmed" actually requires here

Three tiers, worth holding apart:

A published, Arc-specific doc page with real endpoints, chain IDs, or contract addresses (QuickNode, GetBlock, Alchemy, dRPC) is the strongest signal — it is something a developer can act on today.

A named partnership with no technical detail (Crossmint, and several names in Circle's own integration list) confirms intent and a relationship, not a shipped integration a builder can point their app at yet.

Silence — a provider that is a major player in general Web3 infrastructure but has said nothing about Arc — is not evidence of anything either way. It means "not yet confirmed," not "won't happen" and not "already works because EVM."

What to watch for at mainnet

The single biggest open question across this entire category is the same one Arc itself hasn't answered: official mainnet RPC and explorer URLs were not published as of 2 Sep 2026. Every provider currently listing a testnet-only endpoint will need to publish a mainnet equivalent, and until Arc's own canonical mainnet RPC exists, no third-party provider's "Arc mainnet support" claim can be verified against anything.

Built on Arc is an independent directory. Arc is a Circle product; we are not affiliated with, endorsed by, or operated by Circle.

Sources: - Arc node providers documentation - Arc oracles documentation - Arc account abstraction providers - Circle Announces Founding Validator Cohort and Major Integrations for Arc - Arc RPC | QuickNode Docs - ARC | GetBlock Docs - Arc Testnet RPC URL & devtools | Alchemy - Arc RPC Endpoints | dRPC - Chainstack introduces Arc testnet support - Arc on Chainlink Ecosystem - Arc Leverages Pyth Network's Price Feeds - Crossmint and Circle's Arc Blockchain Forge Partnership