developer-hub: sunset Express Relay docs (OP-PIP-124) - #3943
Conversation
|
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}
🤖 llms.txt Content ReviewDocumentation changes detected, but no product-specific llms.txt files were affected.
Files analyzed |
![chatgpt-codex-connector[bot]](https://avatars.githubusercontent.com/in/1144995?s=60&v=4){kind=small}
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 7f84d418fe
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
| Auction-based MEV capture and order flow protection for DeFi protocols. | ||
| > https://docs.pyth.network/express-relay/index.mdx | ||
|
|
||
| ## Unsure Which Price Feed Product? |
There was a problem hiding this comment.
When clients use /llms-manifest.json hashes to decide whether to refetch content, these deletions are invisible because src/data/llm-token-counts.json was not regenerated: /llms.txt changed from 2459 to 2297 bytes and /SKILL.md from 10593 to 10467 bytes, while GET still publishes their old hashes, sizes, and token counts. Such clients can retain the removed Express Relay recommendations, so run pnpm count:llm-tokens and commit the generated JSON with these route changes.
Useful? React with 👍 / 👎.
| @@ -58,7 +58,6 @@ Use this Skill when the user asks for: | |||
| - Standard DeFi: Pyth Core + \`hermes-client\` + \`pyth-sdk-solidity\` | |||
| - Low latency HFT: Pyth Pro + \`pyth-lazer-sdk\` | |||
| - Randomness: Entropy + \`entropy-sdk-solidity\` | |||
There was a problem hiding this comment.
When an agent receives a request for MEV protection, the skill still explicitly claims that use case at line 19 and classifies it at line 54, but this deletion leaves step 2 without any corresponding product or action. The agent can therefore proceed into unrelated price-feed or randomness guidance instead of explaining the wind-down; either remove MEV protection from the supported classifications or replace this branch with the sunset and migration guidance.
Useful? React with 👍 / 👎.
…page Removes the "Existing integrators: reach out on the Pyth developer forum" line from the Express Relay sunset page. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01D7KUNWBSvBPgHuMvkXH9jJ
2 participants
Winds down the Express Relay section of the developer hub following Pyth governance decision OP-PIP-124: Express Relay Wind-Down. All changes are confined to
apps/developer-hub/.What changed
Sunset page.
content/docs/express-relay/index.mdxis replaced with a short notice that Express Relay has been wound down, pointing existing integrators at the Pyth developer forum for migration guidance and at Price Feeds / Entropy for Pyth's other products. TheGavelicon andfull: truefrontmatter are kept so the page keeps its existing top-tab styling.Deleted content. Every other page under
content/docs/express-relay/is removed: the protocol and searcher integration guides, the HTTP and WebSocket API references, contract addresses, error codes, the wholehow-express-relay-works/section, and the four diagram images.Sidebar.
content/docs/express-relay/meta.jsoncollapses to a singleindexpage.content/docs/meta.jsonis unchanged — Express Relay keeps its top-level slot, it just now lands on the sunset page.Cross-references removed. The "Express Relay — MEV Protection" section in
src/app/llms.txt/route.ts, the SDK bullet and product-table row insrc/app/SKILL.md/route.ts, and the folder-tree entry inREADME.md.Redirects. A
/express-relay/:path+→/express-relaypermanent redirect funnels every deep link to the sunset page.:path+(one-or-more) rather than:path*so/express-relayitself is not redirected to itself.Not in scope
The homepage product cards already omit Express Relay and are untouched. Retiring the SDK packages (
@pythnetwork/express-relay-js,express_relayPython), the auction service, and the on-chain contracts is separate wind-down work.Verification
pnpm turbo run test:lint,test:lint:stylelint,test:types,test:format, andbuildall pass (routing and MDX schema changed, so a production build was run perAGENTS.md).Against a dev server on port 3627:
/express-relayreturns 200 and renders the sunset copy; no self-redirect./express-relay/integrate-as-protocol,/express-relay/how-express-relay-works/auction,/express-relay/integrate-as-searcher/svm, and/express-relay/errorsall return 308 to/express-relay./llms.txt,/SKILL.md, and/llms-full.txtcontain no Express Relay mentions;/sitemap.xmllists only/express-relay.Note for reviewers
The
express-relayentry insrc/components/Root/index.tsxTABSis deliberately kept — it now points at the sunset page. Separately,TABSappears to have no consumer left inapps/developer-hub/; that is pre-existing and out of scope here.