Skip to content

docs(push-feeds): refresh pro_compatible_status and drop Avalanche carve-out #3875

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
aditya520 merged 1 commit into from
Jul 10, 2026
Merged

docs(push-feeds): refresh pro_compatible_status and drop Avalanche carve-out #3875

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
1 change: 0 additions & 1 deletion apps/developer-hub/content/docs/price-feeds/core/push-feeds/data/evm/avalanche-mainnet.json
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,5 +1,4 @@
{
"_comment": "Avalanche feeds are intentionally pinned to pro_compatible_status \"coming_soon\": Pro-compatible push feeds are not deployed for this chain (no deployment-pro-compatible.yaml). Do NOT auto-derive this field from the Hermes listing for this file. See the JSDoc on ProCompatibleStatus in src/components/SponsoredFeedsTable/index.tsx.",
"feeds": [
{
"alias": "HLP0/USDC.RR",
Comment on lines 1 to 4

@devin-ai-integration devin-ai-integration Bot Jul 3, 2026

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

🚩 Avalanche guard rail removed without replacement

The old _comment in avalanche-mainnet.json and step 3 in the JSDoc (SponsoredFeedsTable/index.tsx:27-31 before this PR) served as an explicit warning to future maintainers: "Do NOT auto-derive this field from the Hermes listing for this file." This guard rail existed because Pro-compatible push feeds are reportedly not deployed for Avalanche (no deployment-pro-compatible.yaml). The PR removes both the JSON comment and the JSDoc step, but the Avalanche feed still has "coming_soon". Without the guard rail, a future data refresh could accidentally flip Avalanche to "available" if the feed ID appears in the Hermes listing, even though the chain doesn't support Pro-compatible push feeds. If the underlying deployment situation for Avalanche hasn't changed, consider preserving some form of documentation (e.g. a simpler comment in the JSON or the JSDoc) to prevent accidental promotion.

(Refers to lines 1-12)

Open in Devin Review

Was this helpful? React with 👍 or 👎 to provide feedback.

Expand Down
2 changes: 1 addition & 1 deletion apps/developer-hub/content/docs/price-feeds/core/push-feeds/data/evm/berachain-mainnet.json
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -54,7 +54,7 @@
"time_difference": 3600,
"price_deviation": 1,
"confidence_ratio": 100,
"pro_compatible_status": "coming_soon"
"pro_compatible_status": "available"
},
{
"alias": "HONEY/USD",
Expand Down
4 changes: 2 additions & 2 deletions apps/developer-hub/content/docs/price-feeds/core/push-feeds/data/evm/hyperevm-mainnet.json
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -54,7 +54,7 @@
"time_difference": 3600,
"price_deviation": 1,
"confidence_ratio": 100,
"pro_compatible_status": "coming_soon"
"pro_compatible_status": "available"
},
{
"alias": "USH/USD",
Expand Down Expand Up @@ -102,7 +102,7 @@
"time_difference": 3600,
"price_deviation": 1,
"confidence_ratio": 100,
"pro_compatible_status": "coming_soon"
"pro_compatible_status": "available"
},
{
"alias": "WSTHYPE/STHYPE.RR",
Expand Down
6 changes: 3 additions & 3 deletions apps/developer-hub/content/docs/price-feeds/core/push-feeds/data/evm/monad-mainnet.json
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -78,7 +78,7 @@
"time_difference": 3600,
"price_deviation": 0.2,
"confidence_ratio": 100,
"pro_compatible_status": "coming_soon"
"pro_compatible_status": "available"
},
{
"alias": "STETH/ETH.RR",
Expand Down Expand Up @@ -118,7 +118,7 @@
"time_difference": 3600,
"price_deviation": 0.2,
"confidence_ratio": 100,
"pro_compatible_status": "coming_soon"
"pro_compatible_status": "available"
},
{
"alias": "USDE/USD",
Expand Down Expand Up @@ -166,7 +166,7 @@
"time_difference": 3600,
"price_deviation": 0.2,
"confidence_ratio": 100,
"pro_compatible_status": "coming_soon"
"pro_compatible_status": "available"
},
{
"alias": "FDUSD/USD",
Expand Down
2 changes: 1 addition & 1 deletion apps/developer-hub/content/docs/price-feeds/core/push-feeds/data/sui/sui-mainnet.json
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -54,7 +54,7 @@
"time_difference": 10,
"price_deviation": 0.5,
"confidence_ratio": 100,
"pro_compatible_status": "coming_soon"
"pro_compatible_status": "available"
},
{
"alias": "DEEP/USD",
Expand Down
6 changes: 3 additions & 3 deletions apps/developer-hub/content/docs/price-feeds/core/push-feeds/data/svm/solana-mainnet.json
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -34,7 +34,7 @@
"time_difference": 60,
"price_deviation": 0.5,
"confidence_ratio": 100,
"pro_compatible_status": "coming_soon"
"pro_compatible_status": "available"
},
{
"alias": "BONK/USD",
Expand Down Expand Up @@ -250,7 +250,7 @@
"time_difference": 60,
"price_deviation": 0.5,
"confidence_ratio": 100,
"pro_compatible_status": "coming_soon"
"pro_compatible_status": "available"
},
{
"alias": "NAV.USTB/USD",
Expand Down Expand Up @@ -412,7 +412,7 @@
"time_difference": 240,
"price_deviation": 0.05,
"confidence_ratio": 100,
"pro_compatible_status": "coming_soon"
"pro_compatible_status": "available"
},
{
"alias": "JUPUSD/USD",
Expand Down
6 changes: 1 addition & 5 deletions apps/developer-hub/src/components/SponsoredFeedsTable/index.tsx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -24,12 +24,8 @@ const PRO_COMPATIBLE_DOCS_URL = "/price-feeds/core/upgrade/preparing";
* GET https://pyth.dourolabs.app/hermes/v2/price_feeds
* 2. For each feed, set "available" if its `id` is present in that listing,
* otherwise "coming_soon".
* 3. Avalanche carve-out: every Avalanche feed is pinned to "coming_soon"
* regardless of the listing, because Pro-compatible push feeds are not
* deployed for that chain (no deployment-pro-compatible.yaml). See the
* `_comment` in data/evm/avalanche-mainnet.json.
*
* Last refreshed 2026-06-23. To refresh, re-run the steps above.
* Last refreshed 2026-07-03. To refresh, re-run the steps above.

@chatgpt-codex-connector chatgpt-codex-connector Bot Jul 3, 2026

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

P2 Badge Preserve Avalanche's non-upgraded carve-out

This refresh note now leaves only the generic Hermes-ID derivation, but Avalanche still has no pro-compatible-production EVM deployment in the repo: the current Avalanche contracts are the legacy entries in contract_manager/src/store/contracts/EvmPriceFeedContracts.json and EvmWormholeContracts.json, while the pro-compatible list starts later without an Avalanche entry. Since evm.mdx renders showProCompatibleStatus for Avalanche, the next refresh that sees HLP0/USDC.RR in Hermes would mark the Avalanche push feed Available even though users have no upgraded Avalanche contract to use; keep the chain-specific carve-out until the deployment exists.

Useful? React with 👍 / 👎.

*/
type ProCompatibleStatus = "available" | "coming_soon";

Expand Down