Oracles on Arc compared: what's actually live, feed by feed

An oracle network "supporting" a chain and a specific price feed being live on that chain are two different claims, and this category is where that gap matters most — a lending protocol or derivatives venue that assumes a feed exists because the network name is associated with Arc can build on a false premise. This guide reports what's confirmed at the network level and, where available, at the feed level, as of 2 September 2026.

Why oracle verification has to be more specific than "does the network support Arc"

An oracle network is not a single monolithic deployment — it's a protocol plus a set of individually maintained data feeds, each requiring its own configuration, data sourcing, and (for push-based oracles) its own on-chain update cadence. A network can be technically deployed to a chain while the specific feed a builder needs — say, a particular FX pair or a specific tokenized-asset price — has not been configured yet. This guide draws the line where the evidence draws it: "the network has a confirmed relationship with Arc" is one claim, "a specific feed is live and usable" is a stronger, separate claim, and this guide will not upgrade the former into the latter without direct evidence.

What's confirmed, network by network

Circle's own Arc developer documentation publishes a dedicated oracles reference page (docs.arc.io/arc/tools/oracles) naming five vendors: Chainlink, Chronicle, Pyth, RedStone, and Stork. That documentation listing is itself a primary-sourced confirmation for all five — Circle naming a vendor in its own developer reference, not a secondary aggregator's claim. It does not state mainnet-versus-testnet scope for any of the five, and it does not confirm which specific feeds are configured; those remain separate, checkable claims this guide treats individually below.

Chainlink has the strongest confirmation in this category, on top of the documentation listing: it is named directly in Circle's founding-validator-and-integrations press release (5 Aug 2026) as an Arc integration partner, and it maintains its own public ecosystem partner page listing Arc (chainlinkecosystem.com/ecosystem/arc) — independent confirmation from Chainlink itself. Three sourced confirmations pointing the same direction is the clearest signal available pre-mainnet for any provider in this entire cluster.

Builds on Arc: Provides price feeds and reserve attestations for Arc; also a named founding-validator integration partner. · Role: Serves · Category: Developer Infrastructure → Oracles

Pyth Network has a dated, sourced confirmation beyond the documentation listing, scoped explicitly to testnet: coverage from July 2026 states Pyth's price feeds are live for developers building on Arc's public testnet, framed around delivering high-frequency financial data for real-time DeFi, trading, and financial-infrastructure use cases. This is a genuine, verifiable confirmation — but it is a testnet confirmation, not a mainnet one, and this guide will not extend it past what the source actually states.

Builds on Arc: Provides low-latency price feeds for Arc via push and pull delivery, confirmed on testnet. · Role: Serves · Category: Developer Infrastructure → Oracles

Chronicle — named on Circle's oracle documentation page, described there as onchain data infrastructure for high-integrity price feeds and tokenized-asset verification, originally built as the oracle for Sky (MakerDAO), with proof-of-asset attestation capability. No independent confirmation beyond Circle's listing was found as of 2 Sep 2026.

Builds on Arc: Provides oracle price feeds for Arc contracts. · Role: Serves · Category: Developer Infrastructure → Oracles

RedStone — named on Circle's oracle documentation page as a modular oracle network supporting push, pull, and hybrid delivery models across crypto, LSTs, LRTs, RWAs, and custom feeds. This corrects earlier reporting on this guide, which found no dated RedStone-Arc source and treated the relationship as unconfirmed; Circle's own documentation is the primary source for this correction. No independent confirmation beyond Circle's listing was found as of 2 Sep 2026 — see Built on Arc's RedStone on Arc page for the full readout.

Builds on Arc: Provides modular price-feed oracles for Arc contracts. · Role: Serves · Category: Developer Infrastructure → Oracles

Stork — named on Circle's oracle documentation page, described there as an ultra-low-latency, pull-based oracle protocol emphasizing cryptographic verification. No independent confirmation beyond Circle's listing was found as of 2 Sep 2026.

Builds on Arc: Provides low-latency market-data feeds for Arc. · Role: Serves · Category: Developer Infrastructure → Oracles

API3 — does not appear on Circle's oracle documentation page, and no independently verifiable Arc-specific integration or announcement was found as of 2 Sep 2026. Not yet confirmed.

Push vs. pull oracles, and why the distinction matters more on a settlement-focused chain

Oracle networks broadly split into two delivery models, and the difference affects both cost and staleness risk. A push oracle updates an on-chain price feed continuously or on a schedule, whether or not anyone is using it at that moment — the data is always current when you read it, but someone pays the gas for those updates whether or not a transaction needs them. A pull oracle instead publishes signed price data off-chain and lets an application pull the latest value on-demand, paying only when it's actually needed, at the cost of the application having to explicitly fetch fresh data rather than assuming an on-chain value is current. Pyth is generally associated with the pull model; Chainlink has historically been push-model-first but has expanded into on-demand delivery as well. For a chain like Arc, positioned around settlement, FX, and capital-markets use cases where staleness in a price feed has direct financial consequences, this is not a minor implementation detail — it affects both the cost profile of running an oracle-dependent application and the specific failure modes to design around (a push feed that stops updating during network congestion behaves differently than a pull feed an application forgot to refresh).

What a builder should actually check before depending on a feed

Confirming that a network "supports Arc" is the first step, not the last one. Before building a lending market, derivatives venue, or FX application against any oracle feed on Arc, the concrete things worth verifying directly against the provider's own documentation are: which specific asset pairs are configured for Arc (not just "the network is deployed"), the update frequency or heartbeat for push feeds, and — once mainnet exists — whether the feed has been re-verified against mainnet rather than carried over assumption from testnet behavior. This guide tracks network-level and, where available, feed-level confirmation; it does not substitute for checking a provider's live feed list before shipping code that depends on it.

The directory

Read the status column with the network-vs-feed distinction in mind: a "testnet" status for an oracle network in this table means the network has a confirmed presence on Arc's testnet, not that every feed a given application might need is necessarily configured and live. For any application actually building against a specific feed, verify that feed's live status directly against the oracle provider's own documentation rather than relying on network-level status alone.

What "live at mainnet" will require, specifically

Two things have to both be true before an oracle claim should be treated as mainnet-confirmed for this category: the network itself needs a deployment on Arc mainnet (once mainnet exists, after 16 September), and the specific feed in question needs to actually be configured and updating on that deployment. A general statement like "Chainlink is live on Arc" after mainnet launches should be checked against which specific feeds are actually available, not treated as a blanket guarantee that every feed exists.

What this guide won't cover

This is a status comparison of oracle infrastructure, not a guide to using price feeds for yield strategies, lending collateral decisions, or trading — any earn, yield, or protocol-strategy angle involving an oracle-fed application on Arc belongs to ArcYield, not this directory. For the RPC and node layer an oracle-dependent application also needs, see Built on Arc's RPC providers comparison.

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 oracles documentation - Circle Announces Founding Validator Cohort and Major Integrations for Arc - Arc on Chainlink Ecosystem - Arc Leverages Pyth Network's Price Feeds - Arc | The Economic OS — official site