Smart contracts cannot see outside the blockchain. Lending protocols cannot calculate collateral value, derivatives platforms cannot mark positions to market, and tokenized funds cannot report net asset value without external data arriving onchain. Delivering that data is the job of price feeds.
Without reliable feeds, applications operate blind. They become vulnerable to manipulation, mispricing, and cascading failures that affect everyone holding positions in the system. This guide covers what price feeds are, the types of data feeds used across DeFi and tokenized assets, and how to choose the right one.
What Are Price Feeds?
A price feed is a data service that delivers external market data to a smart contract. Oracles provide these feeds, bridging offchain data sources and onchain applications. Without them, smart contracts cannot access current market prices, exchange rates, or valuations of crypto and traditional financial instruments.
The data a protocol uses directly affects its security. Choosing the wrong feed category introduces risks that often surface during market stress.
Types of Data Feeds
Oracle infrastructure has evolved into two top-level categories. Market feeds derive prices from live trading. Fundamental feeds estimate fair value from underlying structure: a smart contract ratio, an institutional benchmark, or verified reserves. Fundamental feeds split into three subtypes, documented in RedStone’s data taxonomy.
Market Data Feeds
Market feeds are the most widely used feeds in crypto. They derive prices from trading activity across centralized and decentralized exchanges, aggregating trades into a single reference point weighted toward larger orders to reflect where real liquidity sits.
For assets with deep, active markets, market feeds set the reliability bar. They update in real time and respond immediately to supply and demand. Lending markets, perpetual exchanges, and options protocols rely on them for core pricing.
RedStone aggregates from centralized and decentralized exchanges, with independent data providers signing each observation before aggregation. The full pipeline stays verifiable, and DEX liquidity becomes a first-class source, extending coverage to assets with limited centralized exchange history.
Fundamental Data Feeds
Fundamental feeds track underlying structure. They produce less volatile prices than market feeds, with different trust assumptions depending on the source: a smart contract, an institutional API, or verified reserve data. The category fits assets whose economic reality diverges from spot price, such as liquid staking tokens accruing yield or tokenized funds backed by offchain portfolios.
Contract Rate Feeds
A contract rate feed pulls a ratio directly from a protocol’s smart contract, defining the relationship between an asset and its derivative. Common examples are the wstETH/stETH rate derived from the Lido contract and weETH/eETH from Ether.fi.
These feeds serve liquid staking and liquid restaking tokens (LSTs and LRTs). Redemption rates stored in the contract are more accurate than any exchange price and update automatically as yield accrues. Sourcing from exchanges would introduce basis risk.
NAV (Net Asset Value) Feeds
NAV feeds draw from institutional sources such as CESR (composite ether staking rate) and SOFR, the benchmark rate used across traditional fixed income markets. They can also read from offchain systems reporting the value of assets backing a token. BlackRock’s BUIDL fund is a real-world example: BUIDL tokens represent shares in a fund backed by US Treasury bills, cash, and repurchase agreements, with the portfolio’s yield distributed daily to token holders.
Tokenized real-world assets (RWAs) such as equities, bonds, and money market funds create new demand for onchain data, making NAV feeds a critical product category. Platforms integrating tokenized securities increasingly require oracle support for this feed type.
Proof of Reserve Feeds
As tokenized assets and cross-chain collateral have grown, a direct question emerges: how do you verify that an asset is backed by what it claims? Proof of Reserves (PoR) feeds deliver that verification onchain.
PoR feeds do not track market prices. They run custom logic that verifies an asset’s real backing using onchain data. Lombard’s LBTC is a concrete example: the feed derives the LBTC/BTC ratio from LBTC tokens minted against the total BTC held in Lombard’s system on Bitcoin. Protocols integrating LBTC as collateral can verify backing without relying on opaque data providers.
PoR feeds require bespoke implementation per asset. RedStone’s Proof of Reserves services support the category across multiple chains, delivering verifiable reserve data at scale.
Choosing the Right Data Feed
Each feed type has distinct attributes, summarized below.
| Feed | Denomination | Data Source |
|---|---|---|
| Market Feed | USD or other currency | Exchange trading, real time |
| Contract Rate Feed | Underlying asset (e.g. ETH) | Smart contract ratio, onchain |
| NAV Feed | Custom (% yield, USD) | Institutional source, daily |
| Proof of Reserve Feed | Custom (e.g. BTC) | Custom logic, stored balances |
As DeFi expands into RWAs, liquid staking, and cross-chain collateral, feed breadth matters more than raw performance on any single category. RedStone supports all four feed types.
Key Takeaways:
- Price feeds deliver external market data to smart contracts through oracles, forming core infrastructure for DeFi and tokenized assets.
- Data feeds split into two categories: market feeds (sourced from live trading) and fundamental feeds (based on underlying structure). Fundamental feeds include contract rate feeds for LSTs and LRTs, NAV feeds for RWAs, and Proof of Reserve feeds for backing verification.
- Choosing the wrong feed introduces risks that often surface during market stress.
- The correct feed depends on asset and use case. Coverage breadth matters more than headline performance on any single category.
FAQ section
What is the difference between a price feed and an oracle?
An oracle is the service that delivers external data onchain. A price feed is one specific type of data feed that oracles provide, focused on market prices and asset valuations. A single oracle provider typically operates many feeds across assets and categories.
Do all DeFi protocols use the same type of price feed?
No, but it depends on the DeFi team’s choice. Mostly Lending protocols for stablecoin markets use market feeds. Protocols integrating liquid staking tokens use contract rate feeds. Tokenized fund platforms use NAV feeds. Protocols accepting wrapped or cross-chain assets use Proof of Reserve feeds.
Why does price feed selection matter for protocol security?
Feed choice determines what a smart contract sees. A poorly selected feed can misprice an asset, trigger wrongful liquidations, or fail to detect that a wrapped asset has lost its backing. Matching feed type to asset type is core risk management.
