docs: point Polygon node API references at the Bor Global Node endpoint#584
Merged
Conversation
…ndpoint The Polygon node API reference 'Try it' calls and code samples pointed at the retired Erigon demo node, which no longer reflects the live Bor service (and returns wrong/misleading results for trace calls). Swap all Polygon node API specs and reference pages to the current Polygon Bor Global Node (archive + debug/trace + bor namespace). Verified against the endpoint: bor v2.9.0, chainId 0x89, archive state, callTracer + flatCallTracer, debug_traceBlockByNumber, and bor_* methods all respond correctly. Scoped strictly to polygon_node_api specs and the reference pages that use them (41 specs + 39 pages); line endings preserved, only the endpoint host and token changed.
|
Contributor
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro Plus Run ID: 📒 Files selected for processing (80)
📝 WalkthroughSummary by CodeRabbit
WalkthroughPolygon OpenAPI specifications now use the Chainstack mainnet server and a new hashed operation path. Matching Polygon reference pages update their OpenAPI mappings to the same path identifier without changing operation schemas or documentation content. ChangesPolygon OpenAPI specifications
Documentation mappings
Estimated code review effort: 2 (Simple) | ~10 minutes Possibly related PRs
Poem
🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
Contributor
|
Preview deployment for your docs. Learn more about Mintlify Previews.
💡 Tip: Enable Workflows to automatically generate PRs for you. |
Contributor
|
Preview deployment for your docs. Learn more about Mintlify Previews.
💡 Tip: Enable Workflows to automatically generate PRs for you. |
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.
The Polygon node API reference pages (under API → Node APIs → Polygon node API) had their "Try it" endpoint and code samples pointing at the retired Erigon demo node. That node no longer reflects the live Polygon service — most importantly, trace calls there return misleading results versus the Bor end-state we now document.
This swaps every Polygon node API spec and reference page to the current Polygon Bor Global Node demo endpoint (archive + debug/trace).
Scope
openapi/polygon_node_api/—servershost + operation path.openapi:frontmatter path.polygon-*pages and the older unprefixed pages (chainid,getcode,ethcall, …) — all are in the Polygon node API nav section.eth_sendRawTransactionSync) was already on the new endpoint.Only the endpoint host and token changed (121 lines); line endings preserved, no whitespace churn.
Verified live
Confirmed the new endpoint serves everything the references exercise: bor v2.9.0, chainId 0x89, archive state (balance at block 1,000,000),
callTracer+flatCallTracer,debug_traceBlockByNumber, and thebor_*namespace (bor_getAuthor,bor_getSignersAtHash) — all respond correctly.mint broken-linksclean.