Skip to content

docs: add Goldsky Edge RPC to RPC providers - #56

Merged
probablyangg merged 4 commits into
stablelabs:mainfrom
kasrakhosravi:docs/goldsky-edge-rpc
Oct 28, 2026
Merged

probablyangg merged 4 commits into
stablelabs:mainfrom
kasrakhosravi:docs/goldsky-edge-rpc

Conversation

@kasrakhosravi

@kasrakhosravi kasrakhosravi commented Oct 22, 2026 •

Copy link
Copy Markdown
Contributor

Summary

Adds Goldsky Edge RPC to the RPC providers overview and provider sections. Documents HTTPS JSON-RPC, caching, usage dashboards, and the absence of WebSocket support. Mainnet uses chain ID 988; Testnet uses 2201.

Refreshes the Chinese and Korean RPC providers pages using the translation pipeline and its model review pass. Restricts style-report comments and suggestions to same-repository PRs so fork PRs can finish the style job with read-only tokens. Linting and failure enforcement still run.

Validation

  • npm run check passed under Node 22 after integrating current main, including the three-locale build.
  • i18n:check: 0 missing. Both RPC providers translations have current source hashes; remaining stale warnings concern unrelated pages.
  • Checked translated links, inline code, section counts, and endpoint values against English.
  • Verified Goldsky Mainnet and Testnet return chain IDs 0x3dc and 0x899, plus block numbers.

Docs i18n checklist

  • Maintained English as the source of truth.
  • Generated and reviewed the Chinese and Korean translations.
  • No pages added, moved, or deleted; no sidebar changes needed.
  • npm run i18n:check reports 0 missing.
  • npm run check passes locally.

@probablyangg
probablyangg merged commit 49d5b58 into stablelabs:main Oct 28, 2026
3 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants