Skip to content

Conversation

aditya520
Copy link
Member

@aditya520 aditya520 commented Oct 1, 2025

Description

Type of Change

  • New Page
  • Page update/improvement
  • Fix typo/grammar
  • Restructure/reorganize content
  • Update links/references
  • Other (please describe):

Areas Affected

Checklist

  • I ran pre-commit run --all-files to check for linting errors
  • I have reviewed my changes for clarity and accuracy
  • All links are valid and working
  • Images (if any) are properly formatted and include alt text
  • Code examples (if any) are complete and functional
  • Content follows the established style guide
  • Changes are properly formatted in Markdown
  • Preview renders correctly in development environment

Related Issues

Closes #

Additional Notes

Contributor Information

  • Name:
  • Email:

Screenshots

@aditya520 aditya520 requested a review from jayantk October 1, 2025 02:15
Copy link

vercel bot commented Oct 1, 2025

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Preview Comments Updated (UTC)
docs Ready Ready Preview Comment Oct 8, 2025 5:29am
documentation Error Error Oct 8, 2025 5:29am

},

"use-real-time-data": "Use Real-Time Price Data",
"use-real-time-data": "Pull Real-Time Price Data",
Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I like the consistency before
Use Real-time Price Data
Use Historic Price Data

I believe adding Pull if good, but don't like breaking the above consistency?
Do you have any other ideas? @jayantk @KemarTiti

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

#860 (comment)

How about
"Pull Latest Price Data"
"Pull Historic Price Data" as we need to pull from benchmarks API and then verify.

This guide explains how to use real-time Pyth data in EVM contracts. For an interactive playground to explore the methods supported by the Pyth contract, see the [EVM API reference](../api-reference/evm/).
This guide explains how to **Pull real-time Pyth** data in EVM contracts. For an interactive playground to explore the methods supported by the Pyth contract, see the [EVM API reference](../api-reference/evm/).

<Callout type="info" emoji="ℹ️">
Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I believe we should start with this simple callout in every guide.
If we all feel good with this, then I will add this to every ecosystem guide.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think this code snippet is misleading as the users also need to check that their feeds are being pushed (maybe go pay for it etc). I think it's better to simply send them to a guide that can explain the whole process.

(i'm not strongly convinced of this, so open to discussion)

Copy link
Member Author

@aditya520 aditya520 Oct 3, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Push is simple and straightforward to use. It lets experienced users get started without jumping to another page, while still providing just enough information to begin consuming prices.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

my point here is that it does not provide enough information to consume prices. What if the feed they want isn't being pushed? That is necessary information that will be covered in the guide.

},

"use-real-time-data": "Use Real-Time Price Data",
"use-real-time-data": "Pull Real-Time Price Data",
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Wondering if Pyth pro is near real time, should we call core as real time data ?

May be say "Pull the latest Price Data"

- [Movement](pushed-feeds/movement)

<Callout type="info" emoji="ℹ️">
Push feeds are subject to change with prior notice. Please refer to the [dev
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

sorry i'm only suggesting rephrasing the second sentence. it's not entirely clear that the "updates" in that sentence means "changes to the feeds"

This guide explains how to use real-time Pyth data in EVM contracts. For an interactive playground to explore the methods supported by the Pyth contract, see the [EVM API reference](../api-reference/evm/).
This guide explains how to **Pull real-time Pyth** data in EVM contracts. For an interactive playground to explore the methods supported by the Pyth contract, see the [EVM API reference](../api-reference/evm/).

<Callout type="info" emoji="ℹ️">
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think this code snippet is misleading as the users also need to check that their feeds are being pushed (maybe go pay for it etc). I think it's better to simply send them to a guide that can explain the whole process.

(i'm not strongly convinced of this, so open to discussion)

It follows a design where price updates are pulled from pythnet, but it can be integrated into applications using push integration as well.
[What is a Pull Oracle](/price-feeds/pull-updates) explains this difference in detail.

Application developers can [schedule price updates](/price-feeds/schedule-price-updates) by running a [price-pusher](/price-feeds/schedule-price-updates/using-scheduler) to automate the process of updating the on-chain price.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

it's called the scheduler not the price pusher

Copy link
Member Author

@aditya520 aditya520 Oct 3, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Let's kepp this to price-pusher.
Price Pusher is more descriptive that just scheduler.
We should rename on other pages as well.

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We can use schedule as a verb, like schedule price updates using price-pusher, but let's use scheduler as the product name. We call price-pusher in our monorepo as well.

This guide explains how to use real-time Pyth data in EVM contracts. For an interactive playground to explore the methods supported by the Pyth contract, see the [EVM API reference](../api-reference/evm/).
This guide explains how to **Pull real-time Pyth** data in EVM contracts. For an interactive playground to explore the methods supported by the Pyth contract, see the [EVM API reference](../api-reference/evm/).

<Callout type="info" emoji="ℹ️">
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

my point here is that it does not provide enough information to consume prices. What if the feed they want isn't being pushed? That is necessary information that will be covered in the guide.

@aditya520
Copy link
Member Author

my point here is that it does not provide enough information to consume prices. What if the feed they want isn't being pushed? That is necessary information that will be covered in the guide.

The callout links them to both push-feeds and push-integration guide. I believe that should be sufficient.

Copy link
Contributor

@nidhi-singh02 nidhi-singh02 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

minor nits


## Choosing Your Integration Method

**Pull integration** is the default choice for most applications. In this integration, the application retrieves price data from a [webserveice](./how-pyth-works/hermes) and submits it to
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

nit typo webservice

function exampleMethod() public {
// Read the current price from a price feed if it is less than 60 seconds old.
// Each price feed (e.g., ETH/USD) is identified by a price feed ID.
// The complete list of feed IDs is available at https://docs.pyth.network/price-feeds/price-feeds
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

can we put this info in callout, difficult to read in code comments.

Consult [Schedule Price Updates](/price-feeds/schedule-price-updates) guide for more information.

The Pyth Data Association sponsors regular on-chain updates for some price feeds.
See [Sponsored Feeds](./sponsored-feeds.mdx) for the current list of feeds and their update parameters.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

let's call it Push Feeds, let's be consistent as we have renamed the page.

See [Sponsored Feeds](./sponsored-feeds.mdx) for the current list of feeds and their update parameters.

If you don't find relevant price IDs in the [Sponsored Feeds](./sponsored-feeds.mdx) list, please contact the Pyth team [here](https://tally.so/r/nGz2jj) to run the scheduler/price pusher for the price feed you need.
If you don't find relevant price IDs in the [Sponsored Feeds](./sponsored-feeds.mdx) list, please contact the Pyth team [here](https://tally.so/r/nGz2jj) to run the Price Pusher for the price feed you need.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

let's call it Push Feeds. pls check if any other place still uses the term sponsored feeds and replace it.

@aditya520 aditya520 merged commit 68a5f71 into main Oct 8, 2025
3 of 5 checks passed
@aditya520 aditya520 deleted the chore(price-feeds)-rename-to-price-pusher branch October 8, 2025 06:53
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants