# \[PASSED\] OP-PIP-49: Upgrade the Pyth Contract on NEAR Mainnet

**URL:** <https://forum.pyth.network/t/passed-op-pip-49-upgrade-the-pyth-contract-on-near-mainnet/1941>\
**Category:** Proposals\
**Tags:** operational-pip\
**Created:** [February 17, 2025, 12:28pm UTC](https://forum.pyth.network/t/passed-op-pip-49-upgrade-the-pyth-contract-on-near-mainnet/1941 "2025-02-17T12:28:55Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![KemarTiti](https://sea1.discourse-cdn.com/flex001/user_avatar/forum.pyth.network/kemartiti/32/5_2.png) [@KemarTiti](https://forum.pyth.network/u/KemarTiti)\
**Post date:** [February 17, 2025, 12:28pm UTC](https://forum.pyth.network/t/passed-op-pip-49-upgrade-the-pyth-contract-on-near-mainnet/1941/1 "2025-02-17T12:28:55Z")

</div>

### **Abstract**

* * *

This proposal seeks to enhance the Pyth oracle program on NEAR by enabling price updaters to fetch prices for multiple price feeds in the same call which reduces to cost for users.

The contract upgrade was already performed and tested by end users on NEAR testnet following [OP-PIP-48](https://forum.pyth.network/t/passed-op-pip-48-upgrade-the-pyth-contract-on-near-testnet/1927).

### **Rationale**

* * *

Burrow Finance // Ref Finance are the predominant price updater on NEAR and do trigger a significant of onchain price updates ; therefore it is important to further improve the user experience and efficiency of the Pyth oracle on NEAR.

### **Implementation Plan**

* * *

Proposal ID: [https://proposals.pyth.network/?tab=proposals&cluster=mainnet-beta&proposal=DNpJJZB1fjiUqK1Gma9rsv88cvSyrbpUotStoPgDYvf9](https://proposals.pyth.network/?tab=proposals&cluster=mainnet-beta&proposal=DNpJJZB1fjiUqK1Gma9rsv88cvSyrbpUotStoPgDYvf9)

To verify the proposal, on an amd64 machine with docker, check out `pyth-crosschain` repo at `c3b0f71` revision, go to `target_chains/near/receiver` directory and run `cargo +stable install --locked cargo-near@0.13.3` and `cargo near build reproducible-wasm`.

Then compare the sha-256 hex hash in the final output against the code hash in the proposal.

Alternatively, you can check the CI output at [chore(target\_chains/near): save wasm as artifact in CI (#2344) · pyth-network/pyth-crosschain@c3b0f71 · GitHub](https://github.com/pyth-network/pyth-crosschain/actions/runs/13201472948/job/36854314215) and compare the sha-256 hex hash in the CI output against the code hash in the proposal.

---

<div class="post-metadata">

**Author:** ![Pyth-DAO](https://avatars.discourse-cdn.com/v4/letter/p/edb3f5/32.png) [@Pyth-DAO](https://forum.pyth.network/u/Pyth-DAO)\
**Post date:** [February 21, 2025, 9:24am UTC](https://forum.pyth.network/t/passed-op-pip-49-upgrade-the-pyth-contract-on-near-mainnet/1941/2 "2025-02-21T09:24:55Z")

</div>

Closed on February 21, 2025, 9:24am UTC