Add 'Why Update Prices' section to EVM Pull Integration guide #908
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
- Added a warning callout before the 'Write Contract Code' section - Explains the pull-based oracle model concept - Highlights advantages: lower costs, lower latency, flexibility - Details the three steps required in Pull integration - Warns about StalePrice error when prices aren't updated Co-Authored-By: Nidhi Singh <[email protected]>
Contributor
Author
🤖 Devin AI EngineerI'll be helping with this pull request! Here's what you should know: ✅ I will automatically:
Note: I can only respond to comments from users who have write access to this repository. ⚙️ Control Options:
|
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
Co-Authored-By: Nidhi Singh <[email protected]>
nidhi-singh02
approved these changes
Oct 17, 2025
aditya520
requested changes
Oct 17, 2025
|
|
||
| ## Why Update Prices? | ||
|
|
||
| <Callout type="warning" emoji="⚠️"> |
Member
There was a problem hiding this comment.
Either you can place the title inside the callout or you remove the callout and put the text as a paragraph.
Co-Authored-By: Nidhi Singh <[email protected]>
![devin-ai-integration[bot]](https://avatars.githubusercontent.com/in/811515?s=60&v=4){kind=small}
Contributor
|
add a section with title |
Per feedback from @nidhi-singh02: - Added 'Why Update Prices' as a section heading - Moved explanatory content outside the callout - Kept only the Important note about StalePrice errors in the callout Co-Authored-By: Nidhi Singh <[email protected]>
devin-ai-integration
bot
changed the title
aditya520
approved these changes
Oct 17, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
Added a "Why Update Prices" section to the EVM Pull Integration guide that explains why price updates are required in Pyth's pull-based oracle model. This addresses a common point of confusion for developers new to Pyth who may be accustomed to traditional push oracles.
The section includes:
Type of Change
Areas Affected
pages/price-feeds/use-real-time-data/pull-integration/evm.mdx- Added new "Why Update Prices" section with explanatory content and warning calloutChecklist
npm run lintto check for linting errors (passed with no errors)Related Issues
N/A
Additional Notes
Structure:
This structure ensures the information flows naturally while emphasizing the critical warning about price staleness.
Contributor Information