Blockchain · Explainer
How Do Pyth Price Feeds Work on Hedera?
Pyth Network supplies market-price data that applications on Hedera can request through a pull-oracle design. Learn what the feeds do, how developers use them, and which freshness, accuracy, and contract risks to check.
By the HelpfulCoin editorial team · Updated

What are Pyth price feeds on Hedera?
Pyth Network is an oracle service that supplies market-price data to blockchain applications, and its Hedera integration lets apps request those updates on Hedera. An oracle is a system that brings information from outside a blockchain into a smart contract, which cannot normally fetch external data on its own.
A Pyth feed may represent a market price such as a crypto pair. The application decides how to use that value—for example, as an input to a lending or trading rule. Pyth does not set the market price, execute a trade, or guarantee that an app uses the data correctly.
Pyth announced its Hedera integration on February 26, 2024. The announcement described access to more than 400 price feeds, but that was a historical figure, not a guarantee that every feed remains available on Hedera today. Feed availability can vary by network and asset, so developers should check the current feed catalog before building around a particular price.
How does Pyth’s pull oracle work?
Pyth’s Hedera integration uses a pull-oracle design: an application requests a price update when it needs one and brings that update on-chain. This differs from a push oracle, which writes updates to a blockchain on a schedule whether or not an application needs them at that moment.
In broad terms, the process works like this:
- Data providers contribute market information to Pyth.
- Pyth makes a price update available to an application.
- The application or its user requests the update and submits it to Hedera.
- A smart contract reads the price and applies its own rules.
Pulling an update can help an app use recent data when it needs it, rather than relying only on the last value written to the chain. It does not mean the data is automatically live, free, or correct for every purpose. An update may have a timestamp and confidence range, and the app must decide whether those meet its requirements. Submitting updates may also involve network or service costs; developers should check the current integration terms and transaction behavior before deployment.
Why do Hedera apps use Pyth price feeds?
Pyth price feeds matter because many smart contracts need a market price to make a decision, while blockchains cannot independently read prices from exchanges or other off-chain sources. A feed gives the contract an external data input that it can use under defined rules.
On Hedera, a developer might use a supported feed in an application that needs to value an asset or compare a price with a threshold. The price itself does not make the app safe: the contract must check whether the update is fresh and appropriate, and handle missing or unsuitable data safely.
For someone using an app, the oracle is usually infrastructure operating behind the interface. It can still affect the outcome. If an app reads a stale price, applies the wrong asset pair, or fails to handle uncertainty, a transaction could behave differently than expected. Users should therefore evaluate the application as well as its data provider. Pyth’s presence does not certify an app, guarantee a particular market price, or protect users from losses caused by market moves, bugs, or contract exploits.
Which Pyth feeds can developers use on Hedera?
A developer should confirm that the required asset feed is supported on Hedera now, rather than assume that every Pyth feed is available on every chain. The 2024 Hedera announcement referred to more than 400 feeds, but feed coverage can change and the current catalog is the practical reference for building.
Before writing code, check:
- The exact asset pair and feed identifier expected by the application.
- Whether that feed is available on Hedera and suitable for the intended use.
- The update format, timestamp behavior, and confidence data exposed by the integration.
- The current update and transaction costs, including who submits the update.
- Whether the application’s contract has a safe response if an update is missing or too old.
Do not treat similar-looking symbols as interchangeable. A contract expecting one quote currency or asset can produce incorrect results if connected to another feed. Test with the exact network and feed configuration intended for production, and confirm that the deployment uses the right contract addresses and feed identifiers. Keep those details in deployment records so they can be checked after upgrades or configuration changes.
How do developers integrate Pyth on Hedera safely?
A developer can integrate a Pyth feed by selecting the right asset, wiring the Hedera update flow into a contract, and testing the checks that protect against unsuitable data. The exact code and interfaces depend on the current Pyth integration and the application’s design, so use its current Hedera developer documentation for implementation details.
A careful integration process is:
- Choose the feed. Verify the asset pair and that the feed is available on Hedera.
- Review the interface. Confirm how updates are obtained, submitted, and read, including any update fee or transaction costs.
- Add data checks. Reject updates that are too old, have an unacceptable confidence interval, or do not match the expected feed.
- Define safe failure behavior. Decide what the contract does if the update is missing, invalid, or outside limits. Avoid silently using an old value.
- Test on a non-production environment. Exercise normal, delayed, missing, and unusual price conditions before deploying.
- Monitor after deployment. Watch feed availability, contract behavior, and integration changes, and have a response plan for problems.
Treat feed selection and validation as part of the application’s security design, not as a setup task to do once and forget.
How should you check a Pyth price and its freshness?
A Pyth price is more useful when it is read together with its timestamp and confidence interval. The timestamp indicates when the update relates to; the confidence interval describes uncertainty around the reported price. Neither field is a guarantee that the value matches a price on every exchange.
Before relying on a feed, developers should define limits for how old an update can be and how much uncertainty is acceptable for the application. A threshold suitable for one use may be inappropriate for another. A contract handling collateral, for instance, may need stricter safeguards than a display-only widget.
Watch for these warning signs:
- The application ignores the update timestamp.
- A wide confidence interval is treated as an exact price.
- A failed update causes the contract to reuse an old value without a clear rule.
- The feed’s asset or quote currency does not match the application’s expectations.
Users may not be able to inspect every contract check from an app screen. If the price source or the app’s handling of it is unclear, avoid assuming that a displayed price is guaranteed to be current or executable. A displayed oracle value is an input, not a promise of the price available for a trade.
Is Pyth on Hedera safe to use?
Pyth can reduce the difficulty of supplying external prices to Hedera apps, but using an oracle does not remove smart-contract, data, or market risk. A feed can be unavailable or unsuitable at a critical moment, while a bug in the app can misuse even a valid update.
Key risks include:
- Stale data: The app may act on an update that is too old for the situation.
- Uncertainty: The reported price may have a confidence interval that is too wide for the app’s limits.
- Integration errors: A wrong feed identifier, asset pair, or update-handling rule can lead to incorrect results.
- Contract risk: The app may contain bugs, weak access controls, or unsafe failure behavior.
- Network and service costs: Update submissions and Hedera transactions may have costs or availability constraints.
For users, the practical question is not only “Does this app use Pyth?” but also “How does the app validate and act on the feed?” For developers, review the current integration and contract code, test failure cases, and consider an independent security review. An oracle integration is one component of an application’s risk profile, not a safety certification.
What mistakes should you avoid with Pyth price feeds?
The most common mistakes are assuming every feed is available, treating an oracle value as exact, and relying on a price without checking how the application handles bad or missing updates. These errors can affect both developers and people using apps built on the feed.
Watch out for these mistakes:
- Assuming the 2024 feed count is current. Check today’s Hedera feed catalog for the exact asset you need.
- Using a price without checking age. A recent-looking value in an interface may not prove that the contract received a fresh update.
- Ignoring confidence data. A price estimate is not necessarily a precise or executable market quote.
- Skipping failure tests. Test what happens when an update is delayed, absent, or outside acceptable limits.
- Confusing the oracle with the app. Pyth supplies data; the app’s contracts determine how that data affects transactions.
- Overlooking costs and permissions. Confirm who submits updates, what transactions are required, and what permissions a contract or wallet request involves.
For everyday users, avoid approving a transaction solely because an app displays a Pyth price. Check the transaction details, understand the app’s purpose, and use only funds you can afford to lose in an application whose risks you have assessed.
Frequently asked questions
Does Pyth set the price of HBAR or other crypto?
Pyth Network provides price data to blockchain applications; it does not set or guarantee market prices. A feed is an input an app can use, and the app’s own rules determine what happens with it.
Are all Pyth price feeds available on Hedera?
No. Pyth’s Hedera integration was announced in February 2024, with access to more than 400 feeds described at the time. That historical figure does not guarantee every feed is available on Hedera today, so developers should check the current feed catalog.
What does “pull oracle” mean?
A pull oracle makes a price update available for an application to request and bring on-chain when needed, rather than continuously writing every update to the blockchain. The app still needs to check that the update is suitable for its use.
Can a Pyth price feed be wrong or unsafe?
No. Pyth supplies data, but a feed can be delayed, unsuitable for a particular use, or incorrectly handled by an application. Check the feed’s timestamp and confidence interval, and review the app’s contract and safeguards before relying on it.
Can I trade crypto directly through Pyth on Hedera?
Not by itself. A price feed is infrastructure for apps, not a trading service or a guarantee of returns. A consumer app may use it for lending, swaps, or other functions, each with separate risks.
Mentioned in this guide
dApps in this guide
Pyth Network supplies market prices to blockchain apps and institutions; useful infrastructure, but check each feed and integration carefully.
Keep reading
Related guides
Blockchain · Explainer
What Is a Blockchain and How Does It Work?
A blockchain is a shared digital record that a network maintains according to agreed rules. Learn how blocks, consensus and crypto fit together, what blockchains can and cannot do, and how to avoid common risks.
Blockchain · Explainer
What Is Polkadot and How Does It Work?
Polkadot is a network designed to connect specialized blockchains and coordinate some of their security. Learn how its chains, XCM and DOT fit together, and what to check before using the network.
Blockchain · Explainer
What Is VeChainThor and How Does It Work?
VeChainThor is a public blockchain designed to support business records as well as smart-contract apps. Its two native tokens have different jobs: VET carries value, while VTHO pays transaction costs.
Blockchain · Explainer
What Is a zkEVM and How Does It Work?
A zkEVM combines Ethereum-style smart-contract execution with cryptographic proofs that let another system check the execution was correct. It can help scale Ethereum, but it does not automatically make transactions private or every network equally secure.
Blockchain · Explainer
Is Radar Voting on BNB Chain, Polygon or Avalanche?
The name Radar alone does not identify a crypto project or prove that a chain vote is active. Before voting, verify the proposal and its rules through Radar’s official channels, then compare the practical trade-offs among BNB Chain, Polygon, Avalanche and any other option.
Blockchain · Explainer
What Is Project GYRI? GalaChain Explained
Project GYRI is the earlier name for GalaChain, Gala’s blockchain for its games and other entertainment products. Learn what the chain does, how it relates to GALA, and what to check before using a wallet, NFT or bridge.
Blockchain · Explainer
What Is Radix Babylon and Could It Help DeFi Adoption?
Radix Babylon was a major upgrade to the Radix blockchain, adding smart-contract tools designed around digital assets and decentralized finance. It may make DeFi easier to build on Radix, but an upgrade alone cannot guarantee mainstream use.
Blockchain · Comparison
Why Do DeFi Users Stay on Polygon When Ethereum Gas Falls?
Lower Ethereum gas fees can narrow Polygon’s cost advantage, but fees are only one reason people choose a DeFi network. Liquidity, familiar apps, existing assets and the risks of moving funds can all make staying put more practical.