# Q1 2026 — Pyth Core Onchain Fees **URL:** \ **Category:** Ideas Bank\ **Created:** [January 7, 2026, 2:19pm UTC](https://forum.pyth.network/t/q1-2026-pyth-core-onchain-fees/2319 "2026-01-07T14:19:05Z")\ **Posts on this page:** 13\ **Page:** 1

**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:** [January 7, 2026, 2:19pm UTC](https://forum.pyth.network/t/q1-2026-pyth-core-onchain-fees/2319/1 "2026-01-07T14:19:05Z")

### **Background** On December 9th, 2025, the Pyth DAO, via the [OP-PIP-87](https://forum.pyth.network/t/passed-op-pip-86-pyth-token-phase-2-pyth-strategic-reserve/2293/2) and [The Pyth Token Phase 2 discussion](https://forum.pyth.network/t/pyth-token-phase-2/2284), mandated the Pythian Council to (1) design a pricing matrix, and (2) apply pricing changes on-chain via OP-PIPs on a quarterly basis for all Pyth Products (excluding Pyth Pro). This post will solely focus on Pyth Core fees. Onchain fees for other products like Entropy or Express Relay have their dedicated posts. Until this vote and decision, there had been some prior work but limited in scope that were performed for the Pyth Core products ([1](https://forum.pyth.network/t/implement-fees-on-pyth-core-across-networks/1899), [2](https://forum.pyth.network/t/implement-fees-on-pyth-core-across-networks-2/2114)). And, as of today, only 11 chains (out of 100+ deployments) have non-negligible fees applied for onchain usage. All are listed [here](https://docs.pyth.network/price-feeds/core/current-fees). ### Implementation Strategy **Fee Structure Considerations** Fees will be based on three core principles: - **Per-feed model** : Fees apply to each individual price feed - **Per-update charges** : Each feed update incurs a fee - **Proportionality** : Fees should stay reasonable relative to overall transaction costs Another important factor behind the fee increase for certain chains—especially non-EVM chains such as Solana, Sui, Aptos, Injective (CosmWasm), TON, and NEAR—is the significantly higher technical effort required to upgrade smart contracts compared with EVM chains. For EVMs, the upgrade template (used to adjust the protocol fee) has already been developed and deployed on some networks, whereas no technical work has yet been completed for non-EVM chains. As a result, initial fee increases are expected to be implemented on EVM chains first and, once the required work has been done and tested, fess will be progressively rolled out to non-EVM chains. ### Proposed Fee Structure The table below is a recap of all suggested change (or not) for all chains supported by Pyth. If you want to review the process behind such numbers, please refer to the subsequent post below. | **Blockchain** | Existing Price Update Fee | **New Price Update Fee** | **Token** | **Note** | | --- | --- | --- | --- | --- | | 0G | 0.000000000000000001 | 0.2 | 0G | Fees increased | | Abstract | 0.000000000000000001 | 0.000003 | ETH | Fees increased | | Apechain | 0.000000000000000001 | 0.2 | APE | Fees increased | | Arbitrum | 0.000000000000000001 | 0.000003 | ETH | Fees increased | | Aurora | 0.000003 | 0.000003 | ETH | Fees unchanged | | Avalanche | 0.00025 | 0.0005 | AVAX | Fees increased | | Berachain | 0.000000000000000001 | 0.003 | BERA | Fees increased | | Bittensor | 0.000000000000000001 | 0.00005 | TAO | Fees increased | | Blast | 0.000000000000000001 | 0.000003 | ETH | Fees increased | | BNB | 0.000000000000000001 | 0.0000125 | BNB | Fees increased | | BTTC | 0.000000000000000001 | 25,000 | BTT | Fees increased | | Base | 0.000000000000000001 | 0.0000015 | ETH | Fees increased | | Boba | 0.000000000000000001 | 0.000003 | ETH | Fees increased | | Camp | 0.000000000000000001 | 2 | CAMP | Fees increased | | Celo | 0.000000000000000001 | 0.1 | CELO | Fees increased | | Chilliz | 0.000000000000000001 | 0.33 | CHZ | Fees increased | | Conflux | 0.1 | 0.1 | CFX | Fees unchanged | | Core DAO | 0.000000000000000001 | 0.02 | CORE | Fees increased | | Cronos | 0.06 | 0.06 | CRO | Fees unchanged | | Cronos zkEVM | 0.000000000000000001 | 0.06 | CRO | Fees increased | | Ethereum | 0.000000000000000001 | 0.000003 | ETH | Fees increased | | Etherlink | 0.000000000000000001 | 0.01 | XTZ | Fees increased | | Eventum | 0.000000000000000001 | 0.000003 | ETH | Fees increased | | Filecoin | 0.000000000000000001 | 0.01 | FIL | Fees increased | | Flow | 0.000000000000000001 | 0.1 | FLOW | Fees increased | | Gnosis | 0.000000000000000001 | 0.01 | XDAI | Fees increased | | Gravity | 0.000000000000000001 | 1 | G | Fees increased | | Hedera | 0.000000000000000001 | 0.01 | HBAR | Fees increased | | Hemi | 0.000000000000000001 | 0.000003 | ETH | Fees increased | | HyperEVM | 0.000000000000000001 | 0.0001 | HYPE | Fees increased | | Injective EVM | 0.000000000000000001 | 0.001 | INJ | Fees increased | | Ink | 0.000000000000000001 | 0.000003 | ETH | Fees increased | | Iota (EVM) | 0.000000000000000001 | 0.1 | IOTA | Fees increased | | Kava | 0.000000000000000001 | 0.15 | KAVA | Fees increased | | KCC | 0.000000000000000001 | 0.001 | KCS | Fees increased | | Kaia | 0.000000000000000001 | 0.2 | KAIA | Fees increased | | Lightlink | 0.000000000000000001 | 1 | LL | Fees increased | | Linea | 0.000000000000000001 | 0.000003 | ETH | Fees increased | | Manta | 0.000000000000000001 | 0.000003 | ETH | Fees increased | | Mantle | 0.000000000000000001 | 0.01 | MNT | Fees increased | | Merlin | 0.000000000000000001 | 0.0000001 | BTC | Fees increased | | Meter | 0.02 | 0.04 | MTR | Fees increased | | Mezo | 0.000000000000000001 | 0.0000001 | BTC | Fees increased | | Mode | 0.000000000000000001 | 0.000003 | ETH | Fees increased | | Monad | 0.000000000000000001 | 0.005 | MON | Fees increased | | Morph | 0.000000000000000001 | 0.000003 | ETH | Fees increased | | Neon | 0.000000000000000001 | 0.15 | NEON | Fees increased | | opBNB | 0.000186 | 0.0000125 | BNB | Fees decreased | | Optimism | 0.000000000000000001 | 0.000003 | ETH | Fees increased | | Plasma | 0.000000000000000001 | 0.05 | XPL | Fees increased | | Polygon | 0.000000000000000001 | 0.1 | POL | Fees increased | | Polygon zkEVM | 0.000000000000000001 | 0.000003 | ETH | Fees increased | | Polynomial | 0.000000000000000001 | 0.0000015 | ETH | Fees increased | | Ronin | 0.001 | 0.1 | RON | Fees increased | | Scroll | 0.000000000000000001 | 0.000003 | ETH | Fees increased | | Superseed | 0.000000000000000001 | 0.000003 | ETH | Fees increased | | Sei EVM | 0.01 | 0.1 | SEI | Fees increased | | Shimmer | 1 | 100 | SMR | Fees increased | | Skate | 0.000000000000000001 | 0.000003 | ETH | Fees increased | | Sonic (EVM) | 0.000000000000000001 | 0.000000000000000001 | S | Fees unchanged | | Soneium | 0.000000000000000001 | 0.000003 | ETH | Fees increased | | Story Protocol | 0.000000000000000001 | 0.006 | IP | Fees increased | | Swellchain | 0.00005 | 0.000003 | ETH | Fees decreased | | Taiko | 0.000000000000000001 | 0.000003 | ETH | Fees increased | | Unichain | 0.000000000000000001 | 0.000003 | ETH | Fees increased | | Viction | 0.000000000000000001 | 0.1 | VIC | Fees increased | | WEMIX | 0.000000000000000001 | 0.03 | WEMIX | Fees increased | | Worldchain | 0.00001 | 0.000003 | ETH | Fees decreased | | zkSync Era | 0.000000000000000001 | 0.000003 | ETH | Fees increased | | Zetachain | 0.000000000000000001 | 0.1 | ZETA | Fees increased | | Solana | 0.000000001 | 0.00001 | SOL | Fees increased | | Eclipse | 0.000000001 | 0.000003 | ETH | Fees increased | | Sonic (SVM) | 0.000000001 | 0.3 | SONIC | Fees increased | | Fogo | 0.000000001 | 0.000000001 | FOGO | Fess unchanged | | Aptos | 0.00000001 | 0.005 | APT | Fees increased | | Sui | 0.000000001 | 0.004 | SUI | Fees increased | | IOTA (Sui) | 0.000000001 | 0.1 | IOTA | Fees increased | | Movement | 0.00000001 | 0.25 | MOVE | Fees increased | | TON | 0.000000001 | 0.005 | TON | Fees increased | | Fuel | 0.000000000000000001 | 0.000003 | ETH | Fees increased | | Injective (Cosmwasm) | 0.000000000000000001 | 0.0001 | INJ | Fees increased | | Osmosis | 0.000001 | 0.1 | OSMO | Fees increased | | Neutron | 0.000001 | 0.25 | NTRN | Fees increased | | XION | 0.000001 | 0.05 | XION | Fees increased | | NEAR | 0.000000000000000000000001 | 0.005 | NEAR | Fees increased | | Starknet | 0.000000000000000001 | 0.125 | STRK | Fees increased | ### Next Steps This proposal focuses exclusively on fee implementation strategy. We welcome input from all stakeholders: - Publishers - Oracle users - Committed Pythians Your insights will be valuable in refining this proposal and guiding the DAO’s decision-making process. ---

**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:** [January 7, 2026, 2:31pm UTC](https://forum.pyth.network/t/q1-2026-pyth-core-onchain-fees/2319/2 "2026-01-07T14:31:35Z")

Below data is as of end of November, 2025, sourced from this Dune Dashboard [here](https://dune.com/bats4/pyth-price-feed) and internal data. Shown below are the monthly averages of price updates per chains. You can find the table [here](https://docs.google.com/spreadsheets/d/1a8rNShCt4d0W7u1AgWU9A7MOhomo_2k_hmxLxcZjvII/edit?usp=sharing). **0G → 0.02 0G** 0G has recently launched and Pyth usage seems to already be stable at 4,000 monthly updates. Transactions are rare and usually [update 5 feeds altogether](https://chainscan.0g.ai/tx/0x541e73c3fe12a454b9effd6e50d07f5557d7bee348d47fe3fb106b2b378a2a94). Usual cost per tx is around $0.001, and about 800 are triggered monthly as of now for a total monthly cost of sub $1. Charging 0.02 $0G per price update would mean 0.1 $0G per tx, which would amount to 800 $0G monthly ($650 / month). ![Chart from Google Docs (86) (1)](https://us1.discourse-cdn.com/flex001/uploads/pyth_dao/original/1X/9a6e15315041b89c79f6d43efe3f373ffc4fffed.png) **Abstract → 0.000003 ETH** Pyth usage on Abstract has been relatively stable throughout the year, ranging around 3,500 monthly price updates. [Most updates](https://abscan.org/address/0x8739d5024B5143278E2b15Bd9e7C26f6CEc658F1) come from the Push Feeds [here](https://docs.pyth.network/price-feeds/core/push-feeds/evm#abstract-mainnet) where 4 feeds are updated in a single tx. Usual cost per tx is around $0.06, and about 900 txs are triggered per month for an average monthly cost of $50. Charging 0.000003 ETH per price update would mean 0.000012 ETH / transaction, which would amount to 0.01-0.015 $ETH monthly. ![Chart from Google Docs (87) (1)](https://us1.discourse-cdn.com/flex001/uploads/pyth_dao/original/1X/fc367c362187baa225942abb3f8e2cf7aaec9e07.png) **Apechain → 0.2 APE** Pyth usage on Apechain has been relatively stable from 1,500 to 3,500 monthly price updates triggered. [Most updates](https://apechain.calderaexplorer.xyz/tx/0x0cabd03e8b83105b8a46df223fa7549ed279720c688c71452afde042c1fe3981) trigger only 1 price update. Usual cost per tx is around $0.004 (0.02 APE), and about 1,500 to 3,500 txs are triggered monthly. Charging 0.02 APE per update would amount to 60 APE monthly. ![Chart from Google Docs (88) (1)](https://us1.discourse-cdn.com/flex001/uploads/pyth_dao/original/1X/5f2a2d78a6476c28f8a58b519447151fb07ebf01.png) **Arbitrum → 0.000003 ETH** Pyth usage on Arbitrum has been drastically reducing throughout 2025 and seems to now range from 25,000 to 50,000 monthly price updates. Most txs [only update one price feed](https://arbiscan.io/tx/0x102539a277a9cd3e522204a8d99615af65055d689f4b5f70515b5d826d58e7d6) and spend $0.005 doing so. Charging 0.000003 ETH per update would approx. amount to 0.1 ETH monthly, assuming recent usage numbers. ![chart (1) (1)](https://us1.discourse-cdn.com/flex001/uploads/pyth_dao/original/1X/61d593701d11fb3d387634bc08cb76f01734d937.png) **Aurora → 0.000003 ETH** The fees for Aurora were actually established early in 2025, it was part of the 1st cohort of chains seeing their fees increased—0.810117 ETH ($2,392.74) has been generated so far. Despite the fee increasing, usage has remained sustained. I’d suggest keeping the 0.000003 ETH per feed updated, which should average 0.1 ETH per month. ![Chart from Google Docs (89) (1)](https://us1.discourse-cdn.com/flex001/uploads/pyth_dao/original/1X/3f504e07d5598b44c04e1527316a7ff19c830f85.png) **Avalanche → 0.0005 AVAX** Similar to Aurora above, the fees for Avalanche were actually established early in 2025, it was part of the 1st cohort of chains seeing their fees increased—177.163250001 AVAX ($2,161.35) has been generated so far. With the AVAX price action, I’d suggest doubling the AVAX cost from 0.00025 to 0.0005 AVAX, which would amount to 20+ AVAX collected per month. ![Chart from Google Docs (90) (1)](https://us1.discourse-cdn.com/flex001/uploads/pyth_dao/original/1X/f8e920161010f09861ef073277ab0bacb3dd1c3c.png) **Berachain → 0.003 BERA** Pyth usage on Berachain has been one of the biggest across the 100+ chains the oracle is deployed on. A single team has been triggering most of the price updates, and there are [Push Feeds](https://docs.pyth.network/price-feeds/core/push-feeds/evm#berachain-mainnet) on this chain as well as. This usage is significantly driven by a chain with barely no onchain gas cost incurred, as a [single tx](https://berascan.com/tx/0x50d63273a27b1d4fe0fce9bca19c0fe20e2990d665eb2454afd8bf8933b7d99f) updating 49 feeds and only paid 0\*\*.\*\*000057825389390384 BERA ($0.000037) for it. Increasing fees, even only slightly will very likely reduce significantly the onchain activity. Nonetheless, I’d suggest charging 0.003 BERA ($0.002) per feed updated on Berachain, which would amount to 12,000 BERA collected monthly. ![Chart from Google Docs (91) (1)](https://us1.discourse-cdn.com/flex001/uploads/pyth_dao/original/1X/0205de4355540bbcc6ae18a42c9b71dd35555698.png) **Bittensor → 0.00005 TAO** Pyth Price Feeds finally started being used on Bittensor with a steady number of price updates triggered. Most txs update 2 feeds, and are rather not cheap as the updater [pays about $0.5 (0.002553092 TAO)](https://evm.taostats.io/tx/0x9fa203e608ab71a619734bc49be36c9dd1fcb10506e68bef8440b7ec857e208d) every time. Based on the above, I’d suggest charging 0.00005 TAO (0.01$) per price feed updated, which would amount to approx. 0.15 TAO per month. ![Chart from Google Docs (92) (1)](https://us1.discourse-cdn.com/flex001/uploads/pyth_dao/original/1X/efe6cb2aa53bbe5e16447be7c6cddb49f3f7eda2.png) **Blast → 0.000003 ETH** Both Blast and the Pyth Core usage on Blast seen a gradual but steady decline in activity throughout the year. Still, there are some updates of Pyth feeds on Blast and they usually update 7 feeds altogether and for now pays about $0.02 in gas cost ([tx](https://blastscan.io/tx/0xa649b0c775f09b237b278768a1dea0f8114b912575b2561097b5c08fda4cfb77)). Given the relatively low usage and low chain gas cost, I would suggest charing 0.000003 ETH for each feed updated — in line with other EVM L2s. ![Chart from Google Docs (85) (1)](https://us1.discourse-cdn.com/flex001/uploads/pyth_dao/original/1X/b13515d5d22a58b94f379580a8379f5860d8a22d.png) **BNB → 0.0000125 BNB** Pyth usage on BNB Chain has been steadily growing throughout 2025, now reaching all time highs. There are two types of users on BNB, a money market [updating 8 feeds simultaneously](https://bscscan.com/tx/0x7fd621cfb1ea4abf5fa1dd3c4c3acdba5807e8e3f8e11e50dfd5d37a6941bab1) and usually paying up to $0.30 in gas cost ; derivatives protocol updating a single price feed and paying close to [$0.15](https://bscscan.com/tx/0xec57f92008be69224b732832fb250a7aa3a507a42e5419ad3357ac9612f3561d). Based on the above, I would suggest charging 0.0000125 BNB (about $0.01) per feed updated— this would amount to 1-1.5 BNB monthly. ![Chart from Google Docs (93) (1)](https://us1.discourse-cdn.com/flex001/uploads/pyth_dao/original/1X/b61f51c60bfdcf56904882c20295238a9cf6324f.png) **BTTC → 25,000 BTT** There is literally no usage for Pyth Core on BTTC ; this can also be explained by the rather poor activity on the chain itself. Just to keep things aligned in between chains, I would suggest applying a fee of 25,000 BTT (approx $0.01) per feed updated. **Base → 0.0000015 ETH** Pyth Price Feeds on Base have steadily grown throughout the year. Base remains one of the top/most active ecosystems in DeFi therefore it is important to be mindful of pricing there. Most transactions update only 1 price feed but some do update as much as 6 feeds together and still pay less than [$0.01 in gas fees](https://basescan.org/tx/0x842b5c2d7746530117c3faeb8ddb28fc0e700960344a500d6acd31acb2742a65). Based on the above, I would recommend charging 0.0000015 ETH per feed — half of the fees on other EVM chains ; which at current usage would bring in 1 ETH monthly. ![Chart from Google Docs (94) (1)](https://us1.discourse-cdn.com/flex001/uploads/pyth_dao/original/1X/7a68241c15289a9294bca7ff34d57cdb361b6d2d.png) **Boba → 0.000003 ETH** Pyth usage on Boba has seen some swings throughout 2025 but seems to have found its plateau recently. Most of the update txs update only 1 price feed and this [costs about $0.01](https://bobascan.com/tx/0xf7358228fb9eb4440bb1e92eca540db164fa06832a40c937c7a40a8ebbd98464?chainid=288) to the updater. In line with other EVM L2s, I would also suggest charging 0.000003 ETH per update ; which should lead to approx 0.02 ETH collected monthly. ![Chart from Google Docs (95) (1)](https://us1.discourse-cdn.com/flex001/uploads/pyth_dao/original/1X/74f243341f7d0d7461d99bc20090886e6adaeb0e.png) ---

**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:** [January 7, 2026, 2:38pm UTC](https://forum.pyth.network/t/q1-2026-pyth-core-onchain-fees/2319/3 "2026-01-07T14:38:18Z")

Below data is as of end of November, 2025, sourced from this Dune Dashboard [here](https://dune.com/bats4/pyth-price-feed) and internal data. Shown below are the monthly averages of price updates per chains. You can find the table [here](https://docs.google.com/spreadsheets/d/1a8rNShCt4d0W7u1AgWU9A7MOhomo_2k_hmxLxcZjvII/edit?usp=sharing). **Camp → 2 CAMP** Similar to BTTC, Pyth usage on Camp Network is small if not non-existent recently. Costs to update Pyth feeds on Camp [are very low](https://camp.cloud.blockscout.com/tx/0x0d683f83986c42e8bde7bce221eca1053758c1df1765bb439b002afe5bafe5f7) and any fee applied will be much greater than the base gas cost. Given the above, I would suggest charging 2 CAMP per feed updated ($0.01). ![Chart from Google Docs (96) (1)](https://us1.discourse-cdn.com/flex001/uploads/pyth_dao/original/1X/d6869ef4f6b1503d96d13578f352cdee3b5c7044.png) **Celo → 0.1 CELO** As Celo migrated to become an Ethereum L2, Pyth usage has slowed down, if not disappeared. Updating Pyth price feeds on Celo is significantly cheap as 5 feeds updated in a single [transaction costs less than $0.001](https://celoscan.io/tx/0xc6aa17c94ce7cff87bb4ba62e081a7a012fdb035720b25f655d12f0b6fe99a1f). To keep pricing in line with other L2s, I would suggest charging 0.1 CELO per feed updated. ![Chart from Google Docs (97) (2)](https://us1.discourse-cdn.com/flex001/uploads/pyth_dao/original/1X/5f2328481d5940ecff2e9a5cdea830a12d6599fc.png) **Chilliz → 0.33 CHZ** As for BTTC, there is no usage of Pyth Core on Chilliz. Just to keep things aligned in between chains, I would suggest applying a fee of 0.33 CHZ (approx $0.01) per feed updated. **Conflux → 0.1 CFX** As Aurora, and Avalanche, Conflux had fees established to 0.1 CFX early in 2025. Until now, there has been slightly over 2,000 CFX tokens accrued by [the contract](https://evm.confluxscan.org/address/0xe9d69cdd6fe41e7b621b4a688c5d1a68cb5c8adc). As fees increased in Q1, usage dropped to a new equilibrium of 1,500—4,000 monthly updates. The current CFX fee is already rather aligned with other suggestions in terms of $, therefore I would suggest keeping the fees as is for now (0.1 CFX). ![Chart from Google Docs (98) (1)](https://us1.discourse-cdn.com/flex001/uploads/pyth_dao/original/1X/f67282a7c21f76b62323787047771439b02e8ea9.png) **CoreDAO → 0.02 CORE** Core is one of the chains with the most activity for Pyth Core with updates being in the millions every month. Most of the updates are done 7 by 7 and this costs about [$0.002 per transaction](https://scan.coredao.org/tx/0x29cfbd4e44661087860e22d77b6085d561494d069fa1b5787e246fe72d3996d7). As for Berachain, an increase in fees, even small, should have great impact on the underlying activity. I estimate the cost to perform all these price updates to be around $500 / month. Based on the above, I would suggest charging 0.02 CORE per feed updated. This might lead to a reduction in usage but given the low cost, activity should remain sustained. ![Chart from Google Docs (99) (1)](https://us1.discourse-cdn.com/flex001/uploads/pyth_dao/original/1X/c9fdcfadb7a0f159ed53792450248a747b261b67.png) **Cronos → 0.06 CRO** As for Aurora, Avalanche and Conflux, Cronos was among the first batch of chains seeing their fees increased and this might have been one of the best decision so far. The fees were applied to 0.06 CRO (approx 0.006$) per price update. As of today, over [130,000 CRO tokens have been collected](https://explorer.cronos.org/address/0xe0d0e68297772dd5a1f1d99897c581e2082dba5b), and downstream usage has seemingly not been impacted by such decisions. Based on the above, I would suggest keeping the fees as is: 0.06 CRO. ![Chart from Google Docs (100) (1)](https://us1.discourse-cdn.com/flex001/uploads/pyth_dao/original/1X/bea53ef18eaf73c67d51ad8332f56ea58232bee5.png) **Cronos zkEVM → 0.06 CRO** Cronos zkEVM has also been a good chain for Pyth Core usage. Transactions cost on Cronos zkEVM are not insignificant as we can regularly see [txs cost above 0.05$](https://explorer.zkevm.cronos.org/tx/0x30243600517466fe7127b8062f394befceb6ae85d97485a025afa9ca347273af). Continuing on the success 0.06 CRO had on the general Cronos chain, I would suggest applying the same amount of fees on Cronos zkEVM. ![chart (2) (1)](https://us1.discourse-cdn.com/flex001/uploads/pyth_dao/original/1X/f47a29b39c01aa7ac2e522afcf1e372a0b3244ef.png) **Eclipse → 0.000003 ETH** Despite some recent turmoil, Pyth activity on Eclipse has been quite sustained and significant. It is important to note that using Pyth on Eclipse is among the cheapest of all chains mentioned here. It [costs sub $0.00001 to update a price feed](https://eclipsescan.xyz/tx/66sxkXFFQ8jqdqyYfSm8cuqx3JB8DYGsY7Ka96Nb4RuiBuDW6KN9fXg1hsg8edzxY25xzTZEeSabUpCWFkAxgKRe) on Eclipse. Being an Ethereum L2, I would again recommend to apply the 0.000003 ETH fee per feed updated. ![chart (49) (1)](https://us1.discourse-cdn.com/flex001/uploads/pyth_dao/original/1X/12641a9ad3e5a9f60c79796ca1da0423a6049d57.png) **Ethereum → 0.000003 ETH** Pyth Core footprint on Ethereum has been steadily growing throughout 2025. It is important to note that most updates are originating from the Push Feeds [here](https://docs.pyth.network/price-feeds/core/push-feeds/evm#ethereum-mainnet). Gas fees on Ethereum are widely varying as a single tx updating 6 feeds can cost as little as [$0.03](https://etherscan.io/tx/0xa028974e9d0651154541ed104c78a281a73f32a53adf67d00def3cdc6a7fe872) or over $1,000 (during 10/10 crash). While updaters on Ethereum mainnet should be less cost-sensitive, I would still suggest applying the same protocol fee of 0.000003 ETH per feed. ![chart (3) (1)](https://us1.discourse-cdn.com/flex001/uploads/pyth_dao/original/1X/7f1ee600f84076a3b9b053574e24656aed3177c7.png) **Etherlink → 0.01 XTZ** Etherlink is one of the chain with the most activity for the Pyth Core price feeds. This is likely due to a chain that has low gas cost: updating 6 feeds simultaneously costs [less than $0.01](https://explorer.etherlink.com/tx/0x0129599296a16b72f4741a62ba82b92ed3635bf2da50fe758bab3bb18173270c). Similarly to Berachain and other chains with significant number of price updates, a slight increase in fees will likely have a great impact on the downstream usage. I would suggest charging 0.01 XTZ per feed updated—this is still sub $0.01 per feed updated. ![chart (4) (1)](https://us1.discourse-cdn.com/flex001/uploads/pyth_dao/original/1X/948364aa938d32d39ff08b35cbfbf6dbe25dc5bb.png) **Eventum → 0.000003 ETH** Updates are triggered every 10min for this specific appchain and protocol, where 2 price feeds are updated regularly. Transaction [costs about $0.01](https://explorer.evedex.com/tx/0x52f3ccc4aec992231efedca51f7e1efd56af8550862c65baeffdb3af400493f6) on Eventum. As for most chains with ETH as the underlying gas fees, I would suggest applying 0.000003 ETH. ![chart (5) (2)](https://us1.discourse-cdn.com/flex001/uploads/pyth_dao/original/1X/07964cc36b050ee50b5da43a2d6bf62979a67ab4.png) **Flow → 0.1 FLOW** Pyth’s activity on Flow is steady with couple price updates txs triggered every hour. The cost to use Pyth on Flow EVM is very low, as one [tx updating 7 feeds cost less than $0.001](https://evm.flowscan.io/tx/0xefc6e86becae7afd4eef2bfae48d91ab7b12b87b75f0c829d409084d2a4599b5). Overall the user triggers 4,000 transactions monthly incurring a total cost of less than couple dozens of dollars. Therefore I’d suggest applying a 0.1 FLOW fee per price feed updated. ![chart (7) (1)](https://us1.discourse-cdn.com/flex001/uploads/pyth_dao/original/1X/f48b7dbeb5c7c3e93d896506119b79d2f26ee09c.png) **Gnosis → 0.01 xDAI** Sadly, the single user of Pyth price feeds on Gnosis wound down in March 2025. Since no usage has been recorded on Gnosis. Using Pyth on Gnosis is very cheap as 10 feeds updated in a [single tx costs less 0.001$](https://gnosisscan.io/tx/0x54f3f9963d651d9e2a3ce4935e44ad234d0387a1d55a46fe2693aa681970b701). I would suggest applying the base oracle fee at 0.01 xDAI (0.01$) per feed updated. ![chart (8) (1)](https://us1.discourse-cdn.com/flex001/uploads/pyth_dao/original/1X/2a77e3b5fa2c91925905da09763defb9b053560e.png) **Gravity → 1 G** Pyth usage on Gravity has been very stable and sustained. This is led from the Ecosystem itself. As for other chains with significant usage, even a little fee increase should quite significantly impact the usage. Updates are triggered almost every minute, and [update 5 feeds altogether for 0.002$](https://explorer.gravity.xyz/tx/0x19d56252dc3f9ddd4f5f3c94d6d0ac0f7291dc4e2d9d8a120cb30d847781cd5d). I would suggest applying 1 G as fee per price feed updated. ![chart (9) (1)](https://us1.discourse-cdn.com/flex001/uploads/pyth_dao/original/1X/18dbf2be95bcb1d87b867a05fc24d4f7dd2cafc4.png) ---

**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:** [January 7, 2026, 2:43pm UTC](https://forum.pyth.network/t/q1-2026-pyth-core-onchain-fees/2319/4 "2026-01-07T14:43:57Z")

**Hedera → 0.01 HBAR** With no more active usage on this chain, and a limited DeFi ecosystem, I would simply suggest applying the $0.01 baseline fee to update a price feed onchain, which is 0.01 HBAR. ![chart (10) (1)](https://us1.discourse-cdn.com/flex001/uploads/pyth_dao/original/1X/4ae048e8087b7d601b50cfc090cbde4cda93990e.png) **Hemi → 0.000003 ETH** Using of Pyth Price Feeds on Hemi has been growing. Updating Pyth price feeds on Hemi is very cheap as it costs much [less than $0.001](https://explorer.hemi.xyz/tx/0x21aca1ce87edb067dfd442df4d0222d34588eb3097c39ae266820b89e6471461). Transactions usually update a single price feed. As most chain with ETH as the gas token, I would suggest applying 0.000003 ETH as the base oracle fee. ![chart (11) (1)](https://us1.discourse-cdn.com/flex001/uploads/pyth_dao/original/1X/004d892f88c5ccffaa3608194b4b577ac69d9082.png) **HyperEVM → 0.0001 HYPE** Pyth footprint on HyperEVM has been steadily growing throughout 2025, however it is important to note that majority of updates are coming from the Push feeds [here](https://docs.pyth.network/price-feeds/core/push-feeds/evm#hyperevm-mainnet). On average, txs to update Pyth feeds on HyperEVM cost about [$0.01-$0.02](https://hyperevmscan.io/tx/0xaeb604c4907529008742adf8317f5e1b431f6034e5bdefbeee42f186f7e2615e). There are couple addresses updating a large number of price feeds at the same time, respectively 15 and 46. With this in mind, I would suggest charing 0.0001 HYPE per price feed, which slightly below the usual targeted $0.01. ![chart (12) (2)](https://us1.discourse-cdn.com/flex001/uploads/pyth_dao/original/1X/65ade5f424fee7d4693566233d08dfdb05616f39.png) **Injective EVM → 0.001 INJ** Injective native EVM has only launched recently and the first updates of Pyth feeds have started only in December. It is therefore impossible to determine and review existing metrics, apart from the cost to update a single asset on Injective EVM. Updating 1 feed on Injective EVM is very cheap with a cost sub $0.001. I would suggest charging 0.001 INJ per price updated—this is slightly below the usual $0.01 mark but we should expect significant usage of Pyth feeds on Injective so being slightly cheaper should not impact this too much. **Ink → 0.000003 ETH** Initial usage of the Pyth feeds on Ink were coming from the Push Feeds operated by the Pyth Data Association—these [were discontinued during Q3](https://dev-forum.pyth.network/t/upcoming-changes-to-pyth-sponsored-feeds-effective-august-31-2025/360). Since usage has been sparse, akin to the underlying chain activity. Ink is a very cheap chain as it [costs sub $0.001](https://explorer.inkonchain.com/tx/0xdf2423f4c92725ad036e46dd1f0d7a5d3ed1756a9cea7f9197d1abf52b38554d) to update 2 Pyth feeds. I would simply suggest to apply the now traditional 0.000003 ETH per feed updated on Ink. ![chart (13) (1)](https://us1.discourse-cdn.com/flex001/uploads/pyth_dao/original/1X/f4e2d0b6b7d619f64da6a4824a823a6adc2dddc6.png) **Iota → 0.1 IOTA** While Pyth was deployed prior to September 2025, the data collected is quite different from the recent months so it will be discarded in this analysis to rely on more trusted data. Nowadays, there are, on average, one tx to update 5 price feed every 2 minutes. These [txs cost $0.0002](https://explorer.evm.iota.org/tx/0x864ed9ceead981c6b4581ecaef0bd9f204f94b4b564d1eed71d694db1ec75772) which is very cheap. Extrapolating, the user triggers just north of 20,000 txs per month—amounting to less than coupe dozens of dollars cost. I would suggest applying 0.1 IOTA, which remains sub $0.01 per feed updated. ![chart (14) (1)](https://us1.discourse-cdn.com/flex001/uploads/pyth_dao/original/1X/6f5d2daf5ec7f0ec40219fa64c792258d63e5fea.png) **Kava → 0.15 KAVA** Sadly usage of Pyth on Kava has been, akin to the chain itself, slowing down, now to almost 0 usage. Updating a Pyth price feed on [Kava is very cheap](https://kavascan.com/tx/0xfdd16c7f585afed12ece8b5433b7bb8c4af41959d4d0af662a6354475cf41ec6). I would simply suggest to apply the $0.01 baseline fee, or 0.15 KAVA per feed updated. ![chart (15) (1)](https://us1.discourse-cdn.com/flex001/uploads/pyth_dao/original/1X/c2ac69dc7b21e5c4ecd3c68f6dd3ccddc402feee.png) **KCC → 0.001 KCS** As for Gnosis, sadly, the Pyth usage went to 0 on the Kucoin chain: KCC. I would simply suggest to apply the $0.01 per feed fee, meaning 0.001 KCC. ![chart (17) (1)](https://us1.discourse-cdn.com/flex001/uploads/pyth_dao/original/1X/940fee063a1306cbb83645f0e42059a58ff99c06.png) **Kaia → 0.02 KAIA** Pyth activity on Kaia has been very stable and sustained in 2025, which 150,000 to 200,000 price updates monthly. The cost to update Pyth feeds on Kaia is also very low: [0.0002$](https://kaiascan.io/tx/0x16d8d6aa49228d5e72b30bf5d29c8c3c3388c154a12f01a6326da6921cc69f2d?tabId=internalTx&page=1). Given the low cost currently incurred by the end-user, I would also recommend applying the baseline $0.01 fee per feed updated: 0.2 KAIA. ![chart (16) (1)](https://us1.discourse-cdn.com/flex001/uploads/pyth_dao/original/1X/71d500cc22cddaf8468c554358959102d29b9468.png) **LightLink → 1 LL** Pyth activity on LightLink is significant and has sustained throughout 2025. On average, there are txs to udapte 11 price feeds every 20 seconds. These txs cost incur no gas fees, in other words, it is currently free for the user to trigger price update onchain. With this in mind, I would suggest applying 1 LL as onchain fee for every single price update triggered. ![chart (18) (1)](https://us1.discourse-cdn.com/flex001/uploads/pyth_dao/original/1X/fe47e6ce2656adbcf41effb1cc5f699245e9bfac.png) **Linea → 0.000003 ETH** Pyth footprint on Linea has been very stable throughout most of 2025, and recently experienced a quite significant growth. It is important to note that most of the price updates are triggered from the Pyth Data Association Push Feeds [here](https://docs.pyth.network/price-feeds/core/push-feeds/evm#linea-mainnet). Transactions on Linea are rather cheap as they [cost on average $0.02](https://explorer.linea.build/tx/0xeb84c1464f21a2ef0efd17adcdc090e80e2deef6d17bfd2bde33023e0bbeaab4). As for all other L2s, I would suggest applying 0.000003 ETH as onchain fee per price feed. ![chart (19) (1)](https://us1.discourse-cdn.com/flex001/uploads/pyth_dao/original/1X/7be71fbc8d6c3cc47d10c8e22bd8011fdbc074e5.png) **Manta → 0.000003 ETH** Over the past few months, Pyth activity on Manta has been pretty stable though not very significant. Updating a single Pyth price feed on Manta is very cheap as it [costs sub $0.005](https://pacific-explorer.manta.network/tx/0xde7a9eb438773bf777f7ce6d9f16b8e08dd971b37635280b3c49acca01b784ab). Given the above, I would, again, recommend charging 0.000003 ETH per feed updated on Manta. ![chart (20) (1)](https://us1.discourse-cdn.com/flex001/uploads/pyth_dao/original/1X/da43ba8eb78ff4e0c31f7e4753d58a196d99a958.png) **Mantle → 0.01 MNT** Removing the June data, significant outlier, Pyth usage on Mantle has been relatively stable but not significant either. Updating feeds on Mantle is relatively cheap as updaters [pay about $0.01](https://mantlescan.xyz/tx/0x0be5bf933dc4cb25b862c211f0d71dc3486cafc21c3ae9f25af32fc2098a9e00). I would suggest applying the fee baseline of $0.01 per feed update on Mantle: 0.01 MNT. ![chart (21) (1)](https://us1.discourse-cdn.com/flex001/uploads/pyth_dao/original/1X/b04343c7b6e5199be68ffcfae8a8cc2984c6a9ce.png) **Merlin → 0.0000001 BTC** There has been a single (1) price update triggered on Merlin in 2025. The cost to update price feeds on Merlin is quite significant as the [sole price update costs $0.35](https://scan.merlinchain.io/tx/0x3d182bfb84c1704298bf1f59990fb40677d58386a9cb1241cdcf5009409e07a8). I would suggest charging 0.0000001 BTC per price feed update. **Meter → 0.04 MTR** As for other chains like Avalanche, Aurora and a few others, Meter saw its fees already increased early in 2025 to [0.02 MTR](https://docs.pyth.network/price-feeds/core/current-fees) ($0.005). Only [260 MTR](https://scan.meter.io/address/0xbfe3f445653f2136b2fd1e6dddb5676392e3af16) has been generated so far. We can clearly see that the increase in fees has had a significant impact on the number of price updates. Nonetheless, I would suggest further increasing the fee from 0.02 MTR to 0.04 MTR to match the $0.01 baseline fee applied on other chains. ![chart (22) (1)](https://us1.discourse-cdn.com/flex001/uploads/pyth_dao/original/1X/af756001a04f1b05acddda4633a3d6e3847862a0.png) **Mezo → 0.0000001** **BTC** Mezo is a relatively new chain for the Pyth Network and usage seems already relatively stable. On average, we can see a single transaction every hour updating 7 feeds altogether. These txs costs are quite steep as they [are just below $0.05](https://explorer.mezo.org/tx/0xfc9ba44137270eff2a42c62c1942c5c74c33f40446f08b4d5d7f510d34ec524a). Applying the same fee as on Merlin of 0.0000001 BTC, would only double the cost incurred by the updater. ![chart (23) (1)](https://us1.discourse-cdn.com/flex001/uploads/pyth_dao/original/1X/c13c79776f3fadf44e0926016df05da5bec825d4.png) **Mode → 0.000003 ETH** Pyth usage on Mode has been quite strong and stable throughout 2025. Mode is a rather cheap chain to use as Pyth price updates [costs about $0.001](https://explorer.mode.network/tx/0xe6ee2a578640fbb89887eb97761e06f7ade06723ca40ea488ec65451b1c3ac77). Applying 0.000003 ETH as per update fee, would only amount to 0.1-0.2 ETH of new monthly cost for the users. Therefore, I would suggest to apply the new 0.000003 ETH baseline. ![chart (24) (1)](https://us1.discourse-cdn.com/flex001/uploads/pyth_dao/original/1X/f5d231b9548caafff297191626489f2517596908.png) **Monad → 0.005 MON** Monad only launched in November 2025, therefore data will be shortlived. However, there has been 5,000,000 price updates performed in November. Extrapolating [December data](https://dune.com/bats4/pyth-price-feed?granularity_e8eb6e=month), it is expected that there’ll be about 10,000,000 price updates triggered. It is important to note that most of the price updates triggered are coming from the [Pyth Data Association Pusher](https://docs.pyth.network/price-feeds/core/push-feeds/evm#monad-mainnet), which should be kept in mind as fees are set. Overall, I would still suggest to apply a 0.005 MON fee per feed updated. At current prices and metrics, this would mean about $1,000 of fees generated. **Morph → 0.000003 ETH** Pyth usage on Morph has been quite stable since Q2 of 2025. Overall, 4 feeds have been updated in a single tx that [costs sub $0.01](https://explorer.morph.network/tx/0x83d7ce5353ca940c13d63e5e77ad47f571c0fab18992c2185cff9dfe56526382). I would, again, apply the standard 0.000003 ETH fee (akin to other L2s) for Morph. ---

**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:** [January 7, 2026, 2:48pm UTC](https://forum.pyth.network/t/q1-2026-pyth-core-onchain-fees/2319/5 "2026-01-07T14:48:43Z")

Below data is as of end of November, 2025, sourced from this Dune Dashboard [here](https://dune.com/bats4/pyth-price-feed) and internal data. Shown below are the monthly averages of price updates per chains. You can find the table [here](https://docs.google.com/spreadsheets/d/1a8rNShCt4d0W7u1AgWU9A7MOhomo_2k_hmxLxcZjvII/edit?usp=sharing). **Neon → 0.15 NEON** Pyth usage on Neon has been rather stable but quite low—as DeFi activity on Neon is still in its infancy. Updating 6 price feeds on Neon is actually not that cheap as [txs cost on average $0.02](https://neonscan.org/tx/0x9b481faceeedb4ffd4f15d21af32e39a4ae460fbb96a89efad4509df70c1ea20) (0.3 NEON). Based on the above, I’d recommend the same baseline of $0.01 per feed update: 0.15 NEON. ![chart (26) (1)](https://us1.discourse-cdn.com/flex001/uploads/pyth_dao/original/1X/0951a90322a04a09d9651b41c1e794758f2de56b.png) **opBNB → 0.0000125 BNB** Pyth deployment on opBNB was the 1st ever requested via the DAO forum and it was agreed upon that the onchain fee to be 0.000186 BNB (currently $0.15). Despite a rather ‘significant fee’, Pyth price feeds found usage onchain and collected over 15 BNB (close to $15,000) since being deployed. Now usage is constant with one price feed updated every hour — [explorer](https://opbnbscan.com/address/0x2880aB155794e7179c9eE2e38200202908C17B43?tab=internal&p=1). opBNB DeFi ecosystem is still quite similar to a year ago with little relevant DeFi apps. Nonetheless. I would recommend lowering the fees charged as using Pyth for non-derivatives protocols would likely be not possible. I’d suggest the fees to be similar to those proposed on BNB Chain of 0.0000125 BNB. ![chart (27) (1)](https://us1.discourse-cdn.com/flex001/uploads/pyth_dao/original/1X/79a91e1df783e48ec5f114e7a0dba5a2352769d2.png) **Optimism → 0.000003 ETH** Pyth usage on Optimism is rather stable and sustained throughout 2025. Using Pyth on Optimism is very cheap as it currently costs sub [$0.001 to update up to 4 price feeds](https://optimistic.etherscan.io/tx/0x3ef6f7fa9c63c320a5471cce65e8dcc7514486fcffffa9e93285d81216fafbaf) altogether. Given the current low cost, I would again, suggest applying the 0.000003 ETH fee per price feed. ![chart (28) (1)](https://us1.discourse-cdn.com/flex001/uploads/pyth_dao/original/1X/263d45d45e2245cc4bb5b35248b32704207dfdbb.png) **Plasma → 0.05 XPL** Pyth usage on Plasma recently stopped (in December) after a correct 2 months start. Using Pyth on Plasma is incredibly cheap as a transaction to [update a Pyth price feed costs \< $0.000001](https://plasmascan.to/tx/0xffd8c055ba632b729bec9a9e71111d74920ff8de870bda745a3f4f438ea03141). ![chart (29) (1)](https://us1.discourse-cdn.com/flex001/uploads/pyth_dao/original/1X/ace61a20101c71521c48121214129910191a0104.png) **Polygon → 0.1 POL** Pyth Price Feeds have seen their activity constantly decline on Polygon—most of the DeFi activity on Polygon remains isolated in a handful of applications that most do not need an oracle. Using Pyth on Polygon is super cheap as a [single price update costs about $0.001](https://polygonscan.com/tx/0x1891815bbdf5c7d38bef45d510dafa0fc4484192f31a8daf0644cb84b1d592b2). I would suggest applying the basic $0.01 per feed fee to be in line with the other chains (0.1 POL). ![chart (31) (1)](https://us1.discourse-cdn.com/flex001/uploads/pyth_dao/original/1X/b6f63d701ccc2b0a3b2eca74fd2fe3f903a604a1.png) **Polygon zkEVM → 0.000003 ETH** Similar to Polygon above, Pyth and oracle based DeFi activity has been low to non-existant on Polygon zkEVM. It is also important to note that using Pyth on Polygon zkEVM is already quite expensive as txs to update feeds [costs on average $0.15](https://www.oklink.com/polygon-zkevm/tx/0x822f395a43c7ad12859e2a601dc2a9fe042c2ea1263cfffa46d33b6e519dc55a). I would suggest applying the baseline 0.000003 ETH fee per update on Polygon zkEVM. ![chart (32) (1)](https://us1.discourse-cdn.com/flex001/uploads/pyth_dao/original/1X/a20aa7bdc14e5d5bb91cb382944edcf9b9ab0c2c.png) **Polynomial → 0.0000015 ETH** Polynomial is a derivatives protocol on its own appchain with a Pyth deployment. The activity (updates of Pyth feeds) has been significant and quite sustainable throughout 2025. There are usually 9 feeds updated altogether on Polynomial and this [tx costs is super low ($0.001)](https://polynomialscan.io/tx/0x3882f9ddf56fd8582609c76d26ab27461f4a3d8c4f8853624d9726e1342b3412). Based on the above, I would suggest applying the same fee as Base (0.0000015 ETH), which is a slight discount when compared to most other L2s or EVM L1s. ![chart (33) (1)](https://us1.discourse-cdn.com/flex001/uploads/pyth_dao/original/1X/ef6d7fa64cc5c54a681b6fd9927a889ffab10022.png) **Ronin → 0.1 RON** As for Avalanche, Aurora, Conflux, and others, Ronin saw its fees increased early in 2025 to 0.001 RON. With this, the DAO collected just above 1,000 RON as usage dramatically slowed down as the main user switched oracle, [though usage started again](https://app.roninchain.com/address/0x2880ab155794e7179c9ee2e38200202908c17b43?st=internal-txs&p=1&ps=25) (in December). With the RON price action, I would suggest increasing the fee from 0.001 RON to 0.1 RON to match the $0.01 update target. ![chart (34) (1)](https://us1.discourse-cdn.com/flex001/uploads/pyth_dao/original/1X/77867b49b0fade9ba2ea507b8997e130f37e1855.png) **Scroll → 0.000003 ETH** Activity on Scroll (Pyth’s and DeFi more generally) had a rather tough/quiet year in 2025. Using Pyth on Scroll is pretty cheap as [txs cost about $0.001](https://scrollscan.com/tx/0x2886d4c87fd41d4c65132c6bd49582e7dd914df2657fb9ce7245c95511aee2f1). As for other L2s, I’d recommend applying the now 0.000003 ETH fee baseline on Scroll. ![chart (35) (1)](https://us1.discourse-cdn.com/flex001/uploads/pyth_dao/original/1X/17acde3a2dcfcc102113e9f6a72a3e7f0b810f2f.png) **Superseed → 0.000003 ETH** Superseed is an OP L2 chain that failed to gained traction this year and currently have less than $1M in TVL. With a strong start, Pyth usage went to zero on Superseed as there’s no onchain activity there. I would still recommend charging the same fee, as on other EVMs, of 0.000003 ETH. ![chart (36) (1)](https://us1.discourse-cdn.com/flex001/uploads/pyth_dao/original/1X/505fc9f6d5f3f2747cc574dee052a832642f91d5.png) **Sei EVM → 0.1 SEI** Similarly to Avalanche, Aurora, and a few other chains, Sei had seen its fees increased early in 2025 to 0.01 SEI. Despite this increase in fees, usage has sustained throughout 2025, and over 2,500 SEI has been generated by the DAO so far. I would recommend increasing the fees to 0.1 SEI to match with the $0.01 overall baseline for Pyth feeds across networks. ![chart (37) (1)](https://us1.discourse-cdn.com/flex001/uploads/pyth_dao/original/1X/972b672069a1e335f781fa2c3696ac2fb34ee3cb.png) **Shimmer → 100 SMR** Like Avalanche above, early 2025, fees were increased on Shimmer. While usage stopped mid-year, this is coming from the underlying chain activity rather than cost to use Pyth feeds. To approximately match the $0.01 new baseline mark, I’d suggest increasing the fees from 1 to 100 SMR. ![chart (38) (1)](https://us1.discourse-cdn.com/flex001/uploads/pyth_dao/original/1X/b21c3ef69bb846e612f59e4a2ddb0cdf9033844a.png) **Skate → 0.000003 ETH** There has not been a [single price update performed on Skate chain this year](https://scan.skatechain.org/address/0x2880aB155794e7179c9eE2e38200202908C17B43?tab=txs). This is partly by design but still, I’d recommend charging the now baseline of 0.000003 ETH. **Sonic (EVM) → 0.000000000000000001 S** Pyth usage on Sonic has been significant and growing through all of 2025. It is important to note that Sonic currently has gas rebate program ([FeeM](https://feem.soniclabs.com/)) towards protocol generating txs/gas fees and the Pyth Network is currently ranked 6th in this program being allocated more than 180,000 S tokens ($10,000-$15,000). Having charged onchain protocol fees would have likely driven much less usage, and by extension less FeeM rewards. Based on this, I would suggest keeping fees as is (0.000000000000000001 S), as the DAO generates likely more solely based on FeeM. If/when FeeM program would be changed or not yielding as much S tokens as currently, I would suggest increasing the protocol fees. ![chart (40) (1)](https://us1.discourse-cdn.com/flex001/uploads/pyth_dao/original/1X/00236a2d7149853691eb23265cf37e034502ae15.png) **Soneium → 0.000003 ETH** Pyth usage on Soneium has been growing steadily through 2025. Cost to update feeds on Soneium is pretty cheap as [they hover around $0.002](https://soneium.blockscout.com/tx/0x014b8f7ea526d653213ede47eef0f24dbc539f22896fdceb366e80638967cec5) while updating 3 feeds together. As for any ETH L2s, I would recommend increasing the fees on Soneium to 0.000003 ETH. ![chart (41) (1)](https://us1.discourse-cdn.com/flex001/uploads/pyth_dao/original/1X/598455447243eed8b70745d84c712c6fd9b21ff9.png) **Story Protocol → 0.006 IP** Pyth usage on Story has been quite stable and pretty significant as every 20 seconds, 4 price feeds get updated. Story is a super cheap chain to [update 4 Pyth feeds on as it costs sub $0.000001](https://www.storyscan.io/tx/0xee171d2d0c623b75239edc2617145406a8e4f9110fb0bfc743e99b47098a0bfd). Nonetheless, I would still suggest aiming for approx. $0.01 per feed on Story. This might push the updaters to slightly reduce their activity but a balance shall be found. ![chart (42) (1)](https://us1.discourse-cdn.com/flex001/uploads/pyth_dao/original/1X/3fb7862fff83945c0afb0cf1c581a77d7b252766.png) **Swellchain → 0.000003 ETH** Pyth deployment on Swellchain was performed [through the DAO](https://forum.pyth.network/t/proposal-pyth-oracle-integration-for-swellchain/2103) with fees established at 0.00005 ETH ($0.15). There has been close to zero usage on Swellchain this year for Pyth feeds. It may be due to the significant update costs. Therefore, I’d suggest reducing the fees to the baseline of 0.000003 ETH. ---

**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:** [January 7, 2026, 2:59pm UTC](https://forum.pyth.network/t/q1-2026-pyth-core-onchain-fees/2319/6 "2026-01-07T14:59:29Z")

**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:** [January 7, 2026, 3:04pm UTC](https://forum.pyth.network/t/q1-2026-pyth-core-onchain-fees/2319/7 "2026-01-07T15:04:14Z")

Below data is as of end of November, 2025, sourced from this Dune Dashboard [here](https://dune.com/bats4/pyth-price-feed) and internal data. Shown below are the monthly averages of price updates per chains. You can find the table [here](https://docs.google.com/spreadsheets/d/1a8rNShCt4d0W7u1AgWU9A7MOhomo_2k_hmxLxcZjvII/edit?usp=sharing). Below are the non-EVM chains that will likely see their fees actually increased later on as the technical work is ready. **Solana → 0.00001 SOL** Solana remains one of the chains where the Pyth Price Feeds have the biggest footprint. It is however important to note that still majority of updates come from Push Feeds [here](https://docs.pyth.network/price-feeds/core/push-feeds/solana). Updating Pyth feeds on Solana remain quite cheap as [it costs $0.001 to update up to couple price feeds](https://solscan.io/tx/61YNxJ9pwLJhSFCAT1jm2wvKwNn896PabCUyupcFPy6KnMeKyR7r2nzaz8c3yKm69tU3Pb4g6A5NXzG42QV1ihw3). I would suggest starting the fee increase with 0.00001 SOL per feed updated. This is below the EVM baseline established above but very few if not none of the EVMs have had such scale / weight in usage. ![chart (48) (1)](https://us1.discourse-cdn.com/flex001/uploads/pyth_dao/original/1X/59b7eaa374658890bf47027c117f5e8d2001f108.png) **Sonic (SVM) → 0.3 SONIC** Despite some rather good usage over Q4, Pyth activity on Sonic stopped early December which can be linked to the underlying chain decreasing activity. Updating feeds on Sonic is relatively cheap as [it costs sub $0.000001](https://explorer.sonicsvm.org/tx/4bEuvakSwrVca4xG25nueMQMPiByQv6HDPBrpFs22h3EPSnqyCawhbGL1RZJaqHR4grCY5heFWtYftDWAC8cLVda). I would suggest applying a 0.3 SONIC fee per feed updated. This would make it rather aligned with the $0.01 initial benchmark. ![chart (50) (1)](https://us1.discourse-cdn.com/flex001/uploads/pyth_dao/original/1X/03ce58a7499a46bd92dc8a769525225cef611956.png) **Fogo → 0.000000001 FOGO** Price updates only started in December and according to [Fogoscan](https://fogoscan.com/account/rec5EKMGg6MxZYaMdyBfgwp4d5rB9T1VQH5pJv5LtFJ), there are about 5,400 txs performed per day updating price feeds. Most of these updates stem from Push Feeds [here](https://docs.pyth.network/price-feeds/core/push-feeds/fogo). Given that the Fogo token has yet to launch it is rather hard to currently price this. I would therefore recommend waiting for the second quarter pricing update to apply fees on Fogo. Reminder that the Fogo public launch is currently scheduled for mid-January. **Aptos → 0.005 APT** Pyth has always been the most active/feeds the most updated on Aptos. The significant decrease from January 2025 is due to a rather significant decrease in update frequencies from Push feeds [here](https://docs.pyth.network/price-feeds/core/push-feeds/aptos). Updating Pyth feeds on Aptos costs on average [$0.001](https://aptoscan.com/transaction/3996041736). It is important to note that majority of updates come from Pyth Push Feeds. I would suggest applying 0.005 APT per feed updated on Aptos. This is slightly below the $0.01 baseline established for most EVMs but due to an increased activity is, in my opinion, worth to take into account here. ![chart (51) (2)](https://us1.discourse-cdn.com/flex001/uploads/pyth_dao/original/1X/2e56f697afd6cd86872948b2e51634ae369cfa02.png) **Sui → 0.004 SUI** Similarly to Aptos, Pyth on Sui has always been the go-to oracle for DeFi protocols. The big decrease in January in price updates is also due to a significant decrease in update parameters of [Pyth Push Feeds](https://docs.pyth.network/price-feeds/core/push-feeds/sui). The subsequent decrease in Q3 is also stemming from a similar decision. Updating feeds on Sui currently costs, on average, [sub $0.01 (0.004 SUI)](https://suiscan.xyz/mainnet/object/0x04e20ddf36af412a4096f9014f4a565af9e812db9a05cc40254846cf6ed0ad91/tx-blocks). Based on this I would suggest applying 0.004 SUI as protocol fee per feed updated. This would practically double the costs for end users but given the rather low amount, this seems sustainable. ![chart (52) (1)](https://us1.discourse-cdn.com/flex001/uploads/pyth_dao/original/1X/685573336a436061826c1807c43d4a6412e7fdcd.png) **IOTA (Sui) → 0.1 IOTA** Collecting data here was tedious and numbers were estimated based. More recent numbers (like November) are definitely more accurate than the original estimates as the chain launched. Updating feeds on IOTA (Sui) [costs about 0.02 IOTA ($0.002)](https://explorer.iota.org/txblock/EYskGVifiYJ6mkHKksTWLJeYu3iuTJZDNMMbsYdfaaHE). Similarly to IOTA (EVM), I would suggest applying 0.1 IOTA as feed update fee. ![Q1 2026 Pyth Core Onchain Fees Chart (4) (1)](https://us1.discourse-cdn.com/flex001/uploads/pyth_dao/original/1X/c546dea5f6b89b335ed8344af049ad22a3818986.png) **Movement → 0.25 MOVE** Similarly to IOTA (Sui), data collection was not easy throughout the year but recently got better which enable to avoid extrapolating numbers too much. Updating Pyth feeds on Movement is super cheap as [it costs 0.0005 MOVE](https://explorer.movementnetwork.xyz/account/0x9357e76fe965c9956a76181ee49f66d51b7f9c3800182a944ed96be86301e49f?network=mainnet), which is practically zero. Last but not least, it is important to note that majority of updates come from Push Feeds [here](https://docs.pyth.network/price-feeds/core/push-feeds/movement). Still I would recommend applying 0.25 MOVE per feed updated. ![chart (53) (1)](https://us1.discourse-cdn.com/flex001/uploads/pyth_dao/original/1X/ac575fc92d767db56bf01eef9bdb8db36babeb39.png) **TON → 0.005 TON** Pyth price feeds on TON have already had a few lives. Indeed, thanks to the help from the EVAA team, a newly optimized contract has recently been deployed and used by the EVAA protocol itself. Updating price feeds on TON is rather not cheap as costs range from 0.1 to 0.3 TON. While more data gets collected in terms of usage of this new contract, I would suggest applying only 0.005 TON as fee for every feed updated. ![chart (54) (1)](https://us1.discourse-cdn.com/flex001/uploads/pyth_dao/original/1X/eaa46540c38f0b70491405797ced642ef007bd5e.png) **Fuel → 0.000003 ETH** Sadly collecting data for Fuel in a proper and automatic manner has not been possible this year. Extrapolating from the overall explorer activity from the [contract](https://app.fuel.network/contract/0x1c86fdd9e0e7bc0d2ae1bf6817ef4834ffa7247655701ee1b031b52a24c523da/transactions) would suggest that 8 feeds are updated a dozen time per day on average ; which would mean about couple thousands of price updates in a month. Transaction cost to update feeds are about $0.01 which is pretty good for 8 feeds altogether. Still, I would suggest to apply a fee similar to EVMs chains of 0.000003 ETH. **Injective (Cosmwasm) → 0.0001 INJ** Pyth Price Feeds on Injective — Cosmos — have seen a constant and significant usage throughout 2025 and before. Updating up to 19 price feeds together [costs 0.000715 INJ](https://injscan.com/transaction/559BFC4A3D4EC49F865C960FF80D8A2743D69909700865FEF39822DA6467EA08/) ($0.004) which is very cheap. Given the significant amount of price updates triggered, any increase in fees, even small, should lead to a significant reduction in price updates. With this in mind, I would recommend charging 0.0001 INJ per feed updated. ![chart (55) (1)](https://us1.discourse-cdn.com/flex001/uploads/pyth_dao/original/1X/0c23ea39bc98a62e9ee2dde3042f84a95afbf70d.png) **Osmosis → 0.1 OSMO** Data collected this year has been very sporadic and the lack of tooling for Osmosis did not make it easy. However, on average, usage of Pyth feeds has been consistent and rather significant. Updating 2 feeds together [costs about $0.003 per tx](https://www.mintscan.io/osmosis/tx/F1A7C50503BAA413C8C3AFEF02430C84DEA8C02771DEDDB6FBCFCBB531A35DE8?height=51591658). I would suggest applying 0.1 OSMO as the onchain oracle fee. ![chart (56) (1)](https://us1.discourse-cdn.com/flex001/uploads/pyth_dao/original/1X/a2bdfc4b7c61ebb594b46317545d3f8ada6030f0.png) **Neutron → 0.25 NTRN** Pyth usage on Neutron has been stable and quite sustained throughout 2025. Using Pyth on Neutron is quite cheap as it [costs about $0.0002](https://www.mintscan.io/neutron/tx/E630E958496620E9F95BB49B1F55470DF94DAF355AB2F6386FB01B50E46DDF57?height=44146399). Given this, I would recommend charging 0.25 NTRN per price updated. This amount is currently slightly below the $0.01 mark as established on other chains but seems a good start given the rather significant usage. ![Q1 2026 Pyth Core Onchain Fees Chart (6) (1)](https://us1.discourse-cdn.com/flex001/uploads/pyth_dao/original/1X/03431110ec2e17074f8f67b669db4f8c5ba056b9.png) **XION → 0.05 XION** Since deployment, there has been little to no usage on Xion. The underlying chain activity has also been very low for DeFi. With this in mind, I would just suggest to apply the $0.01 baseline target with 0.05 XION. **NEAR → 0.005 NEAR** Pyth usage on Near has been quite significant throughout the year, though diminishing recently. Updating price feeds on [Near costs sub $0.01](https://nearblocks.io/txns/A7Wy2QCrib5FrMdQGkYU5RQtTNPAD7xSxyJrZ3Hm73zz). Most of the usage is driven by the main DeFi application on NEAR. Therefore, I’d suggest applying 0.005 NEAR as oracle update fee. ![chart (57) (1)](https://us1.discourse-cdn.com/flex001/uploads/pyth_dao/original/1X/53f76ef1388380c44da9973c140baa90c97dfb0a.png) **Starknet → 0.125 STRK** Pyth has never found any significant usage on Starknet — it is important to note that DeFi on Starknet is also not significant. Using Pyth on Starknet is quite costly as updating 5 feeds led to [almost $0.1 in costs](https://starkscan.co/tx/0x03f6cdc6b87958a1caf1a602ac5d26d0ff2cd2e5e0169648867791377e33a648). Still I would recommend charging 0.125 STRK per feed updated. ![Q1 2026 Pyth Core Onchain Fees Chart (5) (1)](https://us1.discourse-cdn.com/flex001/uploads/pyth_dao/original/1X/5f0b65f5f635bdbe7ff8dbbc9cf5b4717f7e2b7c.png) ---

**Author:** ![Planck](https://sea1.discourse-cdn.com/flex001/user_avatar/forum.pyth.network/planck/32/386_2.png) [@Planck](https://forum.pyth.network/u/Planck)\ **Post date:** [January 8, 2026, 4:26pm UTC](https://forum.pyth.network/t/q1-2026-pyth-core-onchain-fees/2319/8 "2026-01-08T16:26:47Z")

Thank you for sharing not only the proposal but also a detailed explanation of Pyth usage across so many blockchains. Very helpful and insightful! Overall, this feels like a strong step toward sustainable fee generation. Moreover, I think it’s inevitable if we want to support long term network growth Increasing fees modestly on the most active chains seems like a wise approach, and it’s great to see concrete numbers included. This improves transparency and allows projects leveraging Pyth Price Feeds to better predict their costs I’ll review the proposal in more depth, but at first glance everything looks reasonable to me ---

**Author:** ![lowkeigh](https://avatars.discourse-cdn.com/v4/letter/l/ee7513/32.png) [@lowkeigh](https://forum.pyth.network/u/lowkeigh)\ **Post date:** [January 8, 2026, 8:33pm UTC](https://forum.pyth.network/t/q1-2026-pyth-core-onchain-fees/2319/9 "2026-01-08T20:33:58Z")

Its a massive yes for me, the fee updates above seem absolutely reasonable. Appreciate the details you go into with these proposals, this sort of transparency is rare to come across in web 3. Thank you for your work sir. ---

**Author:** ![Agarwal](https://avatars.discourse-cdn.com/v4/letter/a/7ab992/32.png) [@Agarwal](https://forum.pyth.network/u/Agarwal)\ **Post date:** [January 9, 2026, 11:22am UTC](https://forum.pyth.network/t/q1-2026-pyth-core-onchain-fees/2319/10 "2026-01-09T11:22:08Z")

voted yess for this thank you for the immeasurable efforts u have put in ---

**Author:** ![totti](https://sea1.discourse-cdn.com/flex001/user_avatar/forum.pyth.network/totti/32/37_2.png) [@totti](https://forum.pyth.network/u/totti)\ **Post date:** [January 10, 2026, 1:41am UTC](https://forum.pyth.network/t/q1-2026-pyth-core-onchain-fees/2319/11 "2026-01-10T01:41:32Z")

Thank you for this detailed proposal, much overdue in my opinion. Welcome this with open arms! ---

**Author:** ![Yura](https://avatars.discourse-cdn.com/v4/letter/y/e0b2c6/32.png) [@Yura](https://forum.pyth.network/u/Yura)\ **Post date:** [January 15, 2026, 12:37pm UTC](https://forum.pyth.network/t/q1-2026-pyth-core-onchain-fees/2319/12 "2026-01-15T12:37:29Z")

Hey Pyth core team! We fully understand the need to monetize protocol operations in a sustainable way. One nuance from the TON side: In the TON section of the proposal you mention typical update costs around ~0.1 - 0.3 TON and suggest a protocol fee of 0.005 TON per updated feed. Need to mention, that 2 feeds is essentially the minimum meaningful update, and the oracle fee starts around ~0.14 TON. As the number of feeds increases, update costs will be ~0.18 / ~0.22 / ~0.26 / ~0.30 TON / … / ~0.4. With 0.005 TON/feed, the added fee would be: +0.01 TON for 2 feeds - up to +0.04 for 8 feeds I also included below a small set of real EVAA user flows with a breakdown of “Pyth spends” vs “EVAA spends” (and the ratio). In this sample, the Pyth part is often comparable to EVAA’s own cost, and in some cases it dominates. We’re aligned with introducing fees, but when finalizing TON pricing, please keep in mind that TON updates already carry a significant compute cost, and the Pyth verification step is a material portion of total execution overhead in real user flows. Though this set is not representative and the last txs with 6 feeds are unsatisfied liquidations, it still shows the range. | **feeds** | **pyth spends (TON)** | **evaa spends (TON)** | **ratio (evaa/pyth)** | **tx hash** | | --- | --- | --- | --- | --- | | 2 | 0.141 | 0.155 | 1.099 | 6f10f5ce7d71a409415b848a757e433b6678e05e1f406f47085cea6d8755e025 | | 2 | 0.142 | 0.162 | 1.141 | c5afdadff43b5068ed36cd12ed6b55ce438a9968b243f7d9862d16ad8b2ea2bd | | 3 | 0.180 | 0.164 | 0.911 | 18179571fb1887779e5ca0bead7cd9cd0c3016a6ba2be370b3be769dd42dd9a5 | | 4 | 0.219 | 0.257 | 1.174 | 29629b4fd0e21b1bf355fc22d8bea780252098817f678005634c32ed7dd3f6f5 | | 5 | 0.259 | 0.234 | 0.903 | ea87430eade7bb60031a55d5d026cf9759a944b6dd25e6517fec6987208237f8 | | 5 | 0.259 | 0.195 | 0.753 | 40a1281fb91b12c1ba9e409c0b9a3c46945a504811ce8849a4b89a74bdfe5bf6 | | 6 | 0.299 | 0.122 | 0.408 | 1dc267023fe52a7e684cc0b17b452be42d9d053728129239afd00e4b603c6293 | | 6 | 0.299 | 0.123 | 0.411 | 1f185a14bb7292d264ef5bbf84b18b1080e428d89abe8a447e436898c84f99d7 | | 6 | 0.299 | 0.126 | 0.421 | 1f09bbbbb9369a1f16c4acc0882ad81d37f032b15501e86e48e2ce08735e406a | | 6 | 0.300 | 0.122 | 0.407 | fd4c15f700e6579b023420663db3b41c4177dbaf55b63d2b1f6d0b0104a78a66 | ---

**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:** [January 20, 2026, 9:51am UTC](https://forum.pyth.network/t/q1-2026-pyth-core-onchain-fees/2319/13 "2026-01-20T09:51:10Z")

> [@Yura](#): > > One nuance from the TON side: In the TON section of the proposal you mention typical update costs around ~0.1 - 0.3 TON and suggest a protocol fee of 0.005 TON per updated feed. Need to mention, that 2 feeds is essentially the minimum meaningful update, and the oracle fee starts around ~0.14 TON. As the number of feeds increases, update costs will be ~0.18 / ~0.22 / ~0.26 / ~0.30 TON / … / ~0.4. With 0.005 TON/feed, the added fee would be: +0.01 TON for 2 feeds - up to +0.04 for 8 feeds Hey @Yura Thanks a ton for the time and details provided. One thing I first want to remind you is that there’s a very high chance that TON will not see its fees increased (via a contract upgrade) in this first batch for technical reason as I do not think any code template is ready/available for the Pythian Council to review/implement. Still it is important to already come up with a ‘good’ number for all. The onchain (verification) cost is indeed rather high already, and adding fees to be paid will further increase the total cost (on top of the actual fees). However if I am understanding correctly the numbers, the fees suggested would bring an extra 10-25% cost to you depending on the number of feeds updated? What would be an appropriate number do you think Yura?