docs(specs): update server endpoints from Daikon [Bot]#1086
Conversation
🔗 Preview Mode
|
🔍 Link CheckStatus: ⏭️ Skipped (no content changes) SummaryNo summary found. No markdown content files changed in this PR. |
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 21598e2992
ℹ️ About Codex in GitHub
Codex has been enabled to automatically 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 👍.
When you sign up for Codex through ChatGPT, Codex can also answer questions or update the PR, like "@codex address that feedback".
| - url: https://frax-sepolia.g.alchemy.com/v2 | ||
| name: Frax Sepolia |
There was a problem hiding this comment.
Keep Frax testnet endpoint aligned with Hoodi naming
This change reintroduces frax-sepolia in the Debug API servers, but the repo’s canonical Frax chain spec still defines the public testnet as frax-hoodi (src/openrpc/chains/frax/frax.yaml:12) and the supported-chains docs also publish Hoodi (content/api-reference/node-api/node-supported-chains.mdx:284). Leaving Debug on a different slug creates conflicting endpoint names across specs, which can mislead users and downstream doc/code generators that rely on these server entries.
Useful? React with 👍 / 👎.
🤖 Automated server endpoints update
This PR updates server endpoints based on the latest Daikon configuration. See this comprehensive guide
2 APIs updated:
This workflow run:
Something look wrong? If you are an Alchemy employee please open a PR with changes in Daikon. If you are a member of the public please reach out to our team.