Table · StrataPlanned

Chainlink Price Feed Addresses by Chain and Pair

What is the Chainlink price feed proxy address for a pair on each chain, and what are its decimals and heartbeat?

Chainlink feed addresses by pair and chain: the proxy to read, its aggregator, decimals, heartbeat and feed type, all checked on-chain.

ShareEmail itvoltfincrypto.com/apps/chainlink-price-feed-addresses
Blueprint

What the table will hold.

The table as it will open in Strata. Each figure is named here and arrives with its receipt; until its data is published, its place stays empty.

One row One row per Chainlink feed per chain, from the latest daily checkSorted by Pair, lowest first

PairChainProxy addressAggregatorDecimalsFeed typeAsset classVariantHeartbeatsecondsCategoryLatest answerReceipt
Pair pair Text
The feed's pair as description() reports it, such as ETH / USD.
Chain chain Chain
The chain the feed is deployed on.
Proxy address proxy Address
The proxy contract to read, which forwards to the current aggregator.
Aggregator aggregator Address
The aggregator the proxy forwards to at the latest check.
Decimals decimals Number
The decimals of the feed's answer.
Feed type feed_type Text
Price, exchange rate, proof of reserve or sequencer uptime, from Chainlink's listing.
Asset class asset_class Text
Crypto, stablecoin, forex, commodity, equity or other.
Variant variant Text
A standard feed or an SVR feed, from Chainlink's listing.
Heartbeat heartbeat Number
The longest the feed should go without an update, as published.
Category category Text
The market risk category Chainlink assigns the feed, as published.
Latest answer latest_answer Number
The answer from latestRoundData() at the latest check, scaled by decimals.
Receipt receipt Link
The block and calls behind the row.

Filter by Chain, Feed type, Asset class, Variant.

About

What it answers, and for whom.

Lending markets, perp DEXs and stablecoins read prices from Chainlink feeds, and a contract wired to the wrong address, or to a feed for the wrong pair or chain, can misprice everything it holds. This table is the address book: for each pair on each covered chain, the proxy contract to read, the aggregator behind it, the answer's decimals and the heartbeat to check freshness against.

Every address is checked on the chain rather than copied. The table reads description() and decimals() from each proxy to confirm the pair and its scale, then reads the aggregator the proxy forwards to and its latest answer, which shows the feed is live. How fresh each feed is right now, and why it last updated, is followed update by update on the Chainlink price feeds dashboard.

Method

How it will be measured.

Every figure will be read at a block, kept with its source and its exact read, and open a receipt anyone can re-check.

How receipts work →
  1. Each feed comes from Chainlink's published feed listing and is confirmed on-chain: description() must name the listed pair, and decimals() gives the scale of its answer.
  2. The aggregator each proxy forwards to is read from the proxy itself, so an upgrade to a new aggregator shows up in the row as soon as it happens.
  3. Heartbeat, feed type, asset class and category come from Chainlink's listing and are recorded with the date they were read, since they are not stored on-chain.
  4. The latest answer is read with latestRoundData() at the latest daily check, to show that the address is live; freshness over time belongs to the price feeds dashboard.

The data it needs

Chain data, with some off-chain sources

  • native_prices_dailyTo buildOracle prices by dayReference prices of major assets read from on-chain oracle feeds (Chainlink latestRoundData) at each day's last block, with each round's update time.
  • address_labelsTo buildAddress labelsLabels for known addresses: exchanges, bridges, protocols, funds, treasuries, sanctioned addresses and known attackers.
  • description(), decimals() and aggregator() read from each feed proxy
  • latestRoundData() on each proxy at the daily check
  • Chainlink's published feed listing: pair, heartbeat, feed type, asset class and category, with the date read
Questions

Questions people ask.

How do I find the right Chainlink feed address?

Match the chain, the pair and the contract type. Read description() on the address to confirm the pair and decimals() for its scale, and make sure it is the proxy Chainlink lists rather than an aggregator or a feed on another chain. Every row in the table has passed those reads.

Should I use the proxy or the aggregator address?

The proxy. Chainlink can point a proxy at a new aggregator when a feed is upgraded, and contracts that read the proxy keep working. Contracts that read an aggregator directly can end up reading one that no longer updates.

Are Chainlink feeds available on every chain?

No. Each chain has its own set of feeds, deployed separately, so a pair available on Ethereum may be missing on a layer 2 or have a different heartbeat there. Filter the table by pair to see the chains where it exists and its address on each.

What is the difference between price, exchange rate and reserve feeds?

Price feeds report a market price for a pair. Exchange rate feeds report a token's rate against its underlying, such as a liquid staking token against ETH, and proof of reserve feeds report the reserves behind an asset. The feed type column says which one each feed is.

What is a Chainlink SVR feed?

A variant of a price feed that lets the protocol reading it recapture part of the value its price updates create for liquidators, through an auction around each update. It has a proxy address of its own, listed in the table beside the standard feed.

Proxy
The stable contract address integrators read; it forwards calls to the aggregator that currently serves the feed.
Aggregator
The contract where oracle nodes' reports are combined into each new answer.
Proof of reserve feed
A feed that reports the reserves backing an asset, such as the coins held for a wrapped token, instead of a market price.

Build Chainlink Price Feed Addresses by Chain and Pair on verified data.

Start free in Voltfin Studio: boards, tables and reports where every number opens its receipt. Tell us which data you need first and we will build it next.