docs(developer-hub): link Pyth Pro contracts from Core upgrade page - #3873
Open
aditya520 wants to merge 1 commit into
Open
docs(developer-hub): link Pyth Pro contracts from Core upgrade page#3873aditya520 wants to merge 1 commit into
aditya520 wants to merge 1 commit into
Conversation
The Core upgrade contracts page didn't point users to Pyth Pro contracts, which is confusing for chains like Fluent where Pro is available but an upgraded Core contract is not listed. Users could assume that a chain's absence from the upgraded Core table means Pyth has no contract path on that chain. Update the "Don't see your chain?" callout to explain that absence from the upgraded Core table does not necessarily mean there is no Pyth contract, and link to the Pyth Pro contract addresses page. Copy is worded so it does not imply every chain receives both upgraded Core and Pro deployments. Closes PFG-1186 Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
|
The latest updates on your projects. Learn more about Vercel for GitHub.
5 Skipped Deployments
|
![devin-ai-integration[bot]](https://avatars.githubusercontent.com/in/811515?s=60&v=4){kind=small}
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Summary
The Core upgrade contract addresses page doesn't point users to Pyth Pro contracts. For chains like Fluent — where Pyth Pro is available but an upgraded Core contract is not listed — a user seeing their chain missing from the Core table could wrongly assume Pyth has no contract path on that chain.
This updates the existing "Don't see your chain?" callout on the Core upgrade contracts page to:
Copy is deliberately worded ("though not every chain receives both") so it does not imply every chain gets both upgraded Core and Pro contracts. Existing Core upgrade guidance is unchanged.
No contract data changes — docs-only.
Acceptance criteria (PFG-1186)
Test plan
Ran the developer-hub dev server and verified the rendered callout: the "Pyth Pro contract addresses" link resolves to
/price-feeds/pro/contract-addresses(target page returns 200).Related: PFG-1186, and the inverse direction DEVREL-210 (Core guidance added to Pro docs).
🤖 Generated with Claude Code