# Getting Started with Pyth Network Pull-Oracles on Kaia

**URL:** <https://devforum.kaia.io/t/getting-started-with-pyth-network-pull-oracles-on-kaia/9053>\
**Category:** Kaia\
**Created:** [1월 15, 2026, 8:01오전 UTC](https://devforum.kaia.io/t/getting-started-with-pyth-network-pull-oracles-on-kaia/9053 "2026-01-15T08:01:08Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![sean.lin](https://yyz1.discourse-cdn.com/flex035/user_avatar/devforum.kaia.io/sean.lin/32/3173_2.png) [@sean.lin](https://devforum.kaia.io/u/sean.lin)\
**Post date:** [1월 15, 2026, 8:01오전 UTC](https://devforum.kaia.io/t/getting-started-with-pyth-network-pull-oracles-on-kaia/9053/1 "2026-01-15T08:01:08Z")

</div>

![20260112_Building Real-Time Price Feeds on Kaia (EN)](https://canada1.discourse-cdn.com/flex035/uploads/klaytn/original/2X/5/5bf2d00cc9ab7788f6f2b7dec8643f1a972cda80.jpeg)

### **TL;DR**

Pyth pull-oracles let your app fetch a fresh price update **on demand** (instead of relying on scheduled “push” updates). This thread links to the tutorial and highlights the core mental models to design around.  
Article: [https://blog.kaia.io/building-real-time-price-feeds-on-kaia/](https://blog.kaia.io/building-real-time-price-feeds-on-kaia/)

* * *

### Why this matters

Price feeds are often where UX and risk collide. The real question isn’t “do you have an oracle?” — it’s:

- Are you reading a value that’s fresh **at execution time** , and
- Are you paying for updates you actually use (as opposed to updates scheduled on a fixed schedule)?

Pull-oracles shift the model from “prices are always being pushed on-chain” to “your app pulls an update right before it needs to read.”

### What the article covers

- **Push vs pull mental model:** what changes when updates are fetched on-demand
- **Execution-time freshness:** how an update gets included before your contract reads the price
- **Integration flow (high-level):** where the update fits in your tx path and what your app should handle

### If you’re planning to integrate pull-oracles

Start with the article and map the “update → read” path into your own app flow.

If anything is unclear, drop your questions in this thread and include:

- your **use case** (lending/perps/payments /etc.)
- where you’re stuck ( **update timing** , integration assumptions, failure handling)
- whether you’re testing on **Kairos vs mainnet**

We’ll consolidate common edge cases + integration pain points into the next follow-up post.

---

<div class="post-metadata">

**Author:** ![sean.lin](https://yyz1.discourse-cdn.com/flex035/user_avatar/devforum.kaia.io/sean.lin/32/3173_2.png) [@sean.lin](https://devforum.kaia.io/u/sean.lin)\
**Post date:** [1월 19, 2026, 8:00오전 UTC](https://devforum.kaia.io/t/getting-started-with-pyth-network-pull-oracles-on-kaia/9053/2 "2026-01-19T08:00:59Z")

</div>

![Pyth Network Final Infographic](https://canada1.discourse-cdn.com/flex035/uploads/klaytn/original/2X/e/e8149739f90e9c889e3b856c8062a9853279a766.png)

**Concrete scenario:** you’re building lending/perps/liquidation logic, and you want the price your contract reads to be **fresh at execution time** —without paying for scheduled updates you don’t use.

Things to think about:

- Treat **“update → read”** as one intentional path in your app flow (don’t assume the latest price is already on-chain)
- Decide what happens when an update can’t be fetched/submitted in time (retry, fallback, or fail safely).
- Be explicit about where freshness matters (liquidations, pricing checks, risk limits) vs where “good enough” is okay.

Questions welcome—reply here with your use case + where you’re stuck, and we’ll consolidate common edge cases into a follow-up.