# Issue/Questions when using Pyth on NEAR

**URL:** <https://dev-forum.pyth.network/t/issue-questions-when-using-pyth-on-near/458>\
**Category:** Price Feeds\
**Created:** [October 28, 2025, 2:15pm UTC](https://dev-forum.pyth.network/t/issue-questions-when-using-pyth-on-near/458 "2025-10-28T14:15:19Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![KemarTiti](https://yyz2.discourse-cdn.com/flex034/user_avatar/dev-forum.pyth.network/kemartiti/32/6_2.png) [@KemarTiti](https://dev-forum.pyth.network/u/KemarTiti)\
**Post date:** [October 28, 2025, 2:15pm UTC](https://dev-forum.pyth.network/t/issue-questions-when-using-pyth-on-near/458/1 "2025-10-28T14:15:19Z")

</div>

gm!

We’re encountering a curious issue with the Pyth oracle on NEAR:

In this transaction [Near Transaction AMznXHJPHsKiZhegzieMm6aAA9goXPWJKtgE1D6GqzvZ | NearBlocks](https://nearblocks.io/txns/AMznXHJPHsKiZhegzieMm6aAA9goXPWJKtgE1D6GqzvZ), we send an update\_price\_feeds call 8:14:42 UTC, with the following payload (parsed):

```auto
PriceFeedMessage(
    PriceFeedMessage {
        feed_id: eaa020c61cc479712813461ce153894a96a6c00b21ed0cfc2798d1f9a9e9c94a,
        price: 99988178,
        conf: 68657,
        exponent: -8,
        publish_time: 1761293675,
        prev_publish_time: 1761293675,
        ema_price: 99987801,
        ema_conf: 56791,
    },
)

PriceFeedMessage(
    PriceFeedMessage {
        feed_id: b7a8eba68a997cd0210c2e1e4ee811ad2d174b3611c22d9ebf16f4cb7e9ba850,
        price: 31533148,
        conf: 27285,
        exponent: -8,
        publish_time: 1761293675,
        prev_publish_time: 1761293675,
        ema_price: 31561041,
        ema_conf: 30976,
    },
)

```

Both of those price feed updates have the same publish\_time of 2025-10-24T08:14:35.000Z, which is 7 seconds before the transaction lands on chain.

Despite this, when we call list\_ema\_prices\_no\_older\_than a little later in the transaction ([Near Transaction AMznXHJPHsKiZhegzieMm6aAA9goXPWJKtgE1D6GqzvZ | NearBlocks](https://nearblocks.io/txns/AMznXHJPHsKiZhegzieMm6aAA9goXPWJKtgE1D6GqzvZ?tab=execution#9mgEwoBvyD457Vk335Hhpq1kBZsxF5fcCnZuHmdP36go)), only one of the price feeds returns a price; `b7a8eba68a997cd0210c2e1e4ee811ad2d174b3611c22d9ebf16f4cb7e9ba850` resolves to null. This is despite the fact that we set age to be 60 (seconds).

I would appreciate any pointers if you have the chance to take a look!