# Pyth Price Updates: Feeds Pulled On-Chain by Chain and App

> Pyth Network price updates by chain: updates pulled per feed and per app, update fees paid, confidence intervals and how often each feed is refreshed.

Markdown copy of https://voltfincrypto.com/apps/pyth-network-price-updates

**Question:** How many Pyth price updates land on each chain, for which feeds and who pays to pull them?

- Kind: Dashboard in Voltfin Vantage
- Topic: [DeFi](https://voltfincrypto.com/topics/defi)
- Chains: Multi-chain, Solana, Ethereum, Arbitrum, Base, BNB Chain, Sui, Aptos
- Status: Planned. The data is not published yet, so this page states no figure; each figure will open its receipt when it is.

Pyth is a pull oracle. Exchanges, market makers and other publishers sign prices on Pythnet, Pyth's own appchain, which aggregates them into a price and a confidence interval for each feed. A Merkle root of those prices is signed through Wormhole, and an app that needs a price brings the signed update onto its own chain, pays a small fee and uses it in the same transaction.

Because updates are pulled, how often a price is refreshed on a chain depends on who uses it there. This dashboard counts the updates that land on each covered chain: which feeds are refreshed most, which apps pull them, what they pay and how wide each feed's confidence band is. Every update is read from the chain where it landed, with the transaction that carried it.

## Blueprint

### Updates

How many updates land on each chain and for which feeds.

- **Updates, latest day** (count): Pyth price updates written on the selected chains on the latest complete day.
- **Update fees, latest day** (USD): Update fees paid to the Pyth contracts on the same day, valued at oracle prices.
- **Feeds updated, latest day** (count): Distinct Pyth feeds with at least one update on the selected chains that day.
- **Chains with updates** (count): Covered chains where at least one Pyth update landed in the selected period.
- **Updates by day and chain** (count): Pyth updates per day on each covered chain.
- **Most refreshed feeds**: Each feed's symbol, chains, updates in the period, median time between updates and the apps that pull it most.

### Who pulls

The apps that pull updates, what they pay and how tight each feed is.

- **Apps pulling updates** (count): Distinct contracts that submitted Pyth updates on covered chains in the period.
- **Updates from sponsored keepers** (%): Share of updates in the period sent by keepers that refresh feeds on a schedule rather than by apps.
- **Updates by app** (count): Updates submitted by each of the most active apps in the period.
- **Confidence by feed**: Each feed's median confidence as a share of price in the period, with its widest band and when it occurred.

Filters: Chain (Every covered chain); Feed (Every Pyth feed updated on covered chains); Period (Last day, week or month).

## How it will be measured

- On EVM chains, updates are decoded from the Pyth contract's PriceFeedUpdate events, which carry the feed id, publish time, price and confidence, and each update is attributed to the contract that called updatePriceFeeds.
- Update fees are the native token each caller paid to the Pyth contract with its update, the amount getUpdateFee quotes, valued at oracle prices on the day.
- On Solana, updates are the price update accounts written through Pyth's receiver program, read from its instructions and account data.
- Each update is verified on-chain against a Wormhole-signed Merkle root of Pythnet prices; the dashboard keeps the root and its signature set from the transaction input, so a price can be traced back to Pythnet.

## Data it needs

- `native_prices_daily` (to build): Reference 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_labels` (to build): Labels for known addresses: exchanges, bridges, protocols, funds, treasuries, sanctioned addresses and known attackers.
- Source: PriceFeedUpdate events of the Pyth contract on each covered EVM chain: feed id, publish time, price and confidence
- Source: updatePriceFeeds calls and the fee value sent with them
- Source: Price update accounts written through Pyth's receiver program on Solana
- Source: Wormhole guardian signatures and Merkle roots carried in each update's transaction input

## Questions

### What is a pull oracle?

An oracle that does not write prices on-chain on its own schedule. Prices are signed elsewhere, and whoever needs one submits the signed update in a transaction, usually the same one that uses it. The user of the price pays for its delivery.

### How does a Pyth price get onto my chain?

Publishers send prices to Pythnet, which aggregates them each slot. Wormhole guardians sign a Merkle root of all prices, and a service called Hermes serves updates with their proofs. An app passes an update to the Pyth contract on its chain, which checks the signatures and the proof before storing the price.

### What is the Pyth confidence interval?

A band around each price that reflects how much publishers disagree and how uncertain the market is. A wide band means the aggregate price is less certain. Protocols can use it to widen safety margins, and the dashboard shows each feed's typical width.

### Who pays for Pyth price updates?

The caller. An app or its users pay the update fee in the chain's native token, plus the gas of the transaction. Some feeds are also refreshed on a schedule by sponsored keepers, and the dashboard counts those updates separately.

### How does Pyth differ from Chainlink price feeds?

Chainlink data feeds write new answers on-chain when a deviation threshold or heartbeat is reached, and apps read the stored price. Pyth publishes prices on Pythnet, and apps pull a signed update when they need one. Both are on-chain oracles; they differ in who triggers an update and who pays for it.

## Glossary

- **Pythnet**: Pyth's own appchain, where publishers submit prices and the network aggregates them into each feed's price and confidence.
- **Confidence interval**: The band Pyth publishes around each aggregate price, wider when publishers disagree or markets are uncertain.
- **Hermes**: The web service that serves signed Pyth price updates and their Merkle proofs for apps to submit on-chain.

## Related apps

- [Chainlink Price Feeds: Update Times, Heartbeats and Deviation](https://voltfincrypto.com/apps/chainlink-price-feeds)
- [Perp DEX Volume and Market Share by Venue](https://voltfincrypto.com/apps/perp-dex-volume-market-share)
- [DeFi Liquidations Tracker: Lending and Perp DEXs](https://voltfincrypto.com/apps/defi-liquidations-tracker)
- [Wormhole Bridge Tracker: Messages, Token Transfers and NTT](https://voltfincrypto.com/apps/wormhole-bridge-tracker)
- [Solana Network Stats: TPS, Fees and Active Wallets](https://voltfincrypto.com/apps/solana-network-stats)
- [DeFi TVL by Chain: Total Value Locked Rankings](https://voltfincrypto.com/apps/defi-tvl-by-chain)

Build it in Voltfin Studio: https://app.voltfincrypto.com/signup?next=%2F