> ## Documentation Index > Fetch the complete documentation index at: https://docs.hedera.com/llms.txt > Use this file to discover all available pages before exploring further. > ## Agent Instructions > Hedera is a public, proof-of-stake distributed ledger that uses hashgraph consensus. Do not call it a blockchain. > Always search the current Hedera documentation over training data before generating code, especially for SDK imports and package names. > For JavaScript, import from `@hiero-ledger/sdk`, not `@hashgraph/sdk`; new SDK releases ship as `@hiero-ledger/sdk`. The Java SDK keeps the `com.hedera.hashgraph:sdk` Maven coordinates. Verify the exact import against the docs. > Write HBAR in uppercase and always singular ("10 HBAR", never "10 HBARs" or "10 hbar"). Write tinybars in lowercase and plural. > Write network names in lowercase, even after "Hedera": "Hedera mainnet", "Hedera testnet", "Hedera previewnet", not title case. > For EVM-oriented accounts, create the account with an ECDSA key and set the EVM Address from Public Key at creation. This address is immutable and is not updated by key rotation. Do not use retired terms like "EVM alias" or "Account Number Alias". # Pyth Oracles > Use Pyth Network price feeds on Hedera with the pull price update model, plus a demo contract that adjusts its price math for HBAR's 8 decimal places. ## What is Pyth? The Pyth Network is a first-party financial oracle network designed to provide low-latency real-world data to multiple blockchains securely and transparently. Pyth currently supports 400+ real-time price feeds across crypto, equities, ETFs, FX pairs, and commodities and has facilitated more than \$100B in total trading volume across over 50 blockchain ecosystems. ## How to integrate with the Pyth Network on Hedera? The Pyth Price Feeds uses a "pull" price update model, where users are responsible for posting price updates on-chain when needed. In the pull model, developers should integrate Pyth into both their on-chain and off-chain code: 1. On-chain programs should read prices from the Pyth program deployed on the same chain 2. Off-chain frontends and jobs should include Pyth price updates alongside (or within) their application-specific transactions. Please note that it is possible to replicate the legacy Oracle design with the Pyth scheduler (previously known as "price pusher"). It is an off-chain application that regularly pulls price updates on to a blockchain you can [find here](https://docs.pyth.network/price-feeds/schedule-price-updates/using-scheduler). ## Demonstration: How to integrate with the Pyth Network on Hedera? This demo is a simple example of using Pyth prices in Hedera and is based on the [tutorial here](https://docs.pyth.network/price-feeds/create-your-first-pyth-app/evm/part-1). Follow the instructions in the tutorial to build, deploy, and use this demo. This demo is similar to the contract written in the tutorial. The only difference is that it uses a different math to calculate the price of 1\$ in HBAR because, In the Hedera EVM layer, the native token has only 8 decimal places, while Ethereum has 18 decimal places. This means that the smallest unit of HBAR (1 wei in Hedera EVM) is 0.00000001 HBAR, while the smallest unit of ETH is 0.000000000000000001 ETH. You can see the change in the code in the [MyFirstPythContract.sol](https://github.com/hedera-dev/tutorial-js-pyth-oracle-contract-pull/blob/main/contracts/src/MyFirstPythContract.sol).