Chainlink on Stellar: Data Feeds, What's Live and Who Uses It

Chainlink on Stellar by the numbers (October 2026)

Nine feeds, one mainnet proxy, a 24-hour heartbeat and 18-decimal answers. On 8 October the proxy returned XLM at $0.1924. The market that could use it is real but modest: Stellar DeFi held $249.1M on DefiLlama that day, of which Blend Pools V2 was $144.3M.

We read every feed from the mainnet proxy (CDQBHEUG…S32ZLZ) by simulation on 8 October 2026, at about 20:30 UTC:

Feed	Answer	Last update (UTC, 8 Oct)	Deviation threshold
XLM / USD	$0.1924	20:12	0.5%
BTC / USD	$81,555.76	19:04	0.5%
ETH / USD	$2,470.11	20:12	0.5%
LINK / USD	$12.60	20:12	0.5%
USDC / USD	$0.99985	17:58	0.5%
USDT / USD	$0.99912	17:58	0.5%
EURC / USD	$1.1191	07:21	0.5%
FLHY / USD	$23.35	13:30	0.5%
XAUM reference rate	$4,151.68	20:00	0.1%

Every feed has a 24-hour heartbeat. The round counters show how differently they behave: on 8 October XAUM stood at round 1,721 and XLM at 1,295, while USDC and USDT were at 28 and EURC at 21. Stablecoins rarely move 0.5%, so they mostly update on the heartbeat.

How to choose

• You need XLM, BTC, ETH or stablecoin prices from a source independent of Stellar's own markets: Chainlink is now an option, best used as a second source alongside Reflector or RedStone.
• You need prices for AQUA, BLND, tokenised funds or other Stellar-native assets: Chainlink has no feed for them; see the other providers.
• You need sub-second prices for trading or perps: look at Data Streams, which is pull-based and paid, rather than Data Feeds.
• You are a depositor: ask which oracle prices each collateral asset in your pool. A feed being "live on Stellar" does not mean your pool uses it.

Data Feeds — what went live on 29 September

Chainlink's documentation added Stellar on 29 September 2026. Unlike EVM chains, where each feed has its own contract, Stellar has one proxy per network serving every feed; you choose a feed by its 32-byte data_id, the same value Chainlink shows as the Feed ID.

The proxy exposes five read functions: latest_round(data_id, decimals), get_round(data_id, round_id, decimals), decimals, description and get_min_decimals. A round carries a round ID, an answer as a 256-bit integer, and the observation timestamp. Every feed is stored at 18 decimals and truncated, not rounded, if you ask for fewer. Some feeds refuse lower precision entirely: asking XAUM for 8 decimals returns InvalidDecimals, because its minimum is 18.

Other details matter for integrators. Rounds are kept for 3,110,400 ledgers, roughly 180 days at five-second ledgers, after which get_round fails with NoDataPresent. A feed can be frozen (FeedFrozen), and a contract must handle that rather than treat it as a zero price. Reads cost nothing off-chain: Chainlink's guide reads a feed by simulating the call with the Stellar CLI, without submitting a transaction.

Chainlink labels all nine Stellar feeds "low" market risk in its catalogue. FLHY shares its ticker with Franklin Templeton's high-yield corporate bond ETF; Chainlink's catalogue does not describe the token behind the feed further, so check before relying on it. XAUM is listed as a gold reference rate rather than a market price.

How the update rules work in practice

A push feed writes a new price when the market moves past a threshold or a timer runs out. On Stellar that means 0.5% (0.1% for gold) or 24 hours. A consumer must check the timestamp itself; the proxy will happily return a price that is a day old.

The heartbeat is the number to design around. A stablecoin feed that has not moved 0.5% can legitimately be almost 24 hours old, as EURC was at 13 hours when we read it. A lending pool that rejects prices older than an hour would reject it; one that accepts anything would accept a stale XLM price after an outage. The usual approach is to set a per-asset staleness limit just above the heartbeat and cross-check against a second provider. XOXNO's lending markets, for example, already compare Reflector with RedStone and refuse prices that diverge, as described in our XOXNO write-up.

Data Streams and CCIP — what is and isn't live

Chainlink's network table lists a Data Streams verifier proxy on Stellar mainnet and testnet, and a tutorial for verifying reports in a Soroban contract. CCIP, which moves tokens and messages between chains, has Stellar chain selectors defined but no Stellar entry in its mainnet or testnet directory.

Data Streams works the other way round from Data Feeds. Prices are not written on-chain on a schedule. An application fetches a signed report from Chainlink's API, which needs an account and API credentials, and submits it to the on-chain verifier, which checks the oracle network's signatures before the price is used. The result is fresher prices at the moment of use, paid for by subscription. Chainlink's Stellar tutorial notes that the verifier accepts only reports produced for its own configuration; reports signed for EVM or Solana fail.

CCIP is the piece the October 2025 announcement emphasised. Stellar said then that it would join the Chainlink Scale programme and integrate Data Feeds, Data Streams and CCIP, with CCIP bringing cross-chain token transfers and programmable messages "once completed". As of 8 October 2026, Chainlink's CCIP chain and lane lists for both mainnet and testnet contain no Stellar entry. For moving USDC onto Stellar today, Circle's CCTP is the route; see how to bridge USDC to Stellar.

How Chainlink differs from Reflector, RedStone and Pyth

Chainlink adds a widely used, independent source for majors and stablecoins, through a non-standard interface. Reflector covers Stellar-native markets through SEP-40; RedStone covers tokenised funds with NAV-style feeds; Pyth is pull-based. Chainlink's Stellar catalogue is nine feeds, all majors, stablecoins or gold.

Provider	Model	Interface	Coverage strength on Stellar
Chainlink Data Feeds	Push, 0.5% / 24h	Own (data_id)	Majors, XLM, USDC, USDT, EURC, gold
Reflector	Push, 5-minute Pulse	SEP-40	Stellar DEX and external markets, FX
RedStone	Push, deviation plus daily	SEP-40 for part of its feeds	Tokenised funds and RWAs
Pyth	Pull, verified on demand	Own (verifier)	Pulled on demand; data needs a subscription

The full comparison, including Band and the update details for each, is in oracles on Stellar; we won't repeat it here. The practical point is that Chainlink's prices come from its own oracle network, not Reflector's node cluster, so the two make a natural independent pair for XLM.

Who uses it

We found no live Stellar protocol using Chainlink as of 8 October 2026. DefiLlama's oracle data names RedStone and Reflector for Blend Pools V2 and Pyth for Templar Protocol; no Stellar protocol lists Chainlink.

That is unsurprising nine days after launch, and integration takes work. Blend pools choose their oracle when they are created and cannot change it, so Chainlink would reach Blend through new pools or through an aggregator contract that already sits behind a pool, not by switching an existing one. Any SEP-40 consumer needs an adapter that maps assets to data_ids, converts the 18-decimal integer and enforces a staleness rule. For an overview of the lending venues that could adopt it, see lending protocols on Stellar.

What it means for lending

For Stellar lending, Chainlink's value is a second, independent price for the assets most often borrowed: XLM, USDC, EURC and USDT. It does not help with the thin, Stellar-native collateral that caused February's YieldBlox loss.

The February 2026 exploit, covered in Blend's 2026 incidents, came from a feed reading a nearly empty DEX market for one collateral token. An independent Chainlink XLM price, used to cross-check Reflector's, makes it much harder for one manipulated market to pass unnoticed. But Chainlink has no feed for USTRY, AQUA or BLND, so pools that accept those still depend on other providers and on their own limits.

Three design rules follow. Use Chainlink where it has a feed and treat it as one source, not the source. Set staleness limits per feed with the 24-hour heartbeat in mind. And handle FeedFrozen and NoDataPresent explicitly, because a revert at the wrong moment can block liquidations.

How these fit together

The Scale announcement promised three products. One, Data Feeds, is fully live with a small catalogue. Another, Data Streams, has a mainnet verifier and suits applications willing to pay for low-latency prices. The third, CCIP, is not live. Around them, Stellar's existing providers still cover most of what Stellar DeFi prices, and the first protocol to wire Chainlink into a live market has yet to appear.

The takeaway

Chainlink on Stellar is real, small and new: nine dependable reference prices, one non-standard interface, no users yet. Builders should treat it as a welcome second source for XLM and stablecoins. Depositors should keep asking the question that matters more than the brand: which feed prices each collateral asset in this pool, and what happens when that feed is late?

Sources: Chainlink documentation repo (PR #4162, merged 29 Sep 2026; data-feeds/stellar guides; feeds-stellar-mainnet.json; StreamsNetworksData.ts; Data Streams Stellar tutorial; CCIP v1_2_0 chains and lanes; selectors_stellar.yml); read-only simulation of the Stellar mainnet proxy, 8 Oct 2026; SDF, "Stellar to join Chainlink Scale" (31 Oct 2025); DefiLlama API, protocols and chains (8 Oct 2026).