docs(injective): align Injective API docs with chain-config#1235
docs(injective): align Injective API docs with chain-config#1235andra-catana wants to merge 2 commits intoalchemyplatform:mainfrom
Conversation
Document mainnet vs testnet JSON-RPC differences (testnet-only eth_getBlockReceipts, eth_syncing, net_listening), chain IDs, block tags, and debug namespace coverage from INJECTIVE chain method groups. Made-with: Cursor
![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: 7307dcf3d3
ℹ️ 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".
|
|
||
| The Injective chain includes the **`debug`** method group. The following Geth-style methods are supported on both Injective networks when using the [Debug API](/docs/reference/debug-api-endpoints) (same base URL as the Node API; access may require a paid plan): | ||
|
|
||
| `debug_dbAncient`, `debug_dbAncients`, `debug_dbGet`, `debug_getBadBlocks`, `debug_getRawBlock`, `debug_getRawHeader`, `debug_getRawReceipts`, `debug_getTrieFlushInterval`, `debug_storageRangeAt`, `debug_traceBlockByHash`, `debug_traceBlockByNumber`, `debug_traceCall`, `debug_traceCallMany`, `debug_traceTransaction`. |
There was a problem hiding this comment.
This list declares methods like debug_dbAncient, debug_dbAncients, debug_dbGet, debug_getBadBlocks, debug_getTrieFlushInterval, and debug_storageRangeAt as supported, but the Debug API spec in this repo (src/openrpc/alchemy/debug/debug.yaml) only defines debug_getRawBlock, debug_getRawHeader, debug_getRawReceipts, debug_traceBlockByHash, debug_traceBlockByNumber, debug_traceCall, debug_traceCallMany, and debug_traceTransaction. Advertising methods that are not in the shipped Debug API contract creates an accuracy issue for users and can lead to failed calls or missing endpoint docs.
Useful? React with 👍 / 👎.
Remove server/info prose not rendered by the docs site. Add Injective-specific descriptions on eth_getBlockReceipts, eth_syncing, and net_listening via _components/injective. Point Debug coverage to the Debug API spec in MDX. Made-with: Cursor
1 participant
Description
Align Injective Node API documentation and OpenRPC metadata with Alchemy chain configuration: chain IDs, mainnet vs testnet JSON-RPC differences, and Debug API coverage.
Related Issues
N/A (internal accuracy / chain-config parity).
Changes Made
injective.yaml): Expandedinfo.descriptionand per-server descriptions; documented testnet-only methods (eth_getBlockReceipts,eth_syncing,net_listening) and Debug namespace; reordered custom method refs (including syncing / net_listening).Testing
pnpm run generate:rpclocally (OpenRPC generation succeeded).pnpm run validate)Source:
chain-configINJECTIVE chain (evm+debugmethod groups) andtopconfig.ymlallowlists for INJECTIVE_MAINNET / INJECTIVE_TESTNET.Made with Cursor