Repository navigation
docs: add PublicNode to RPC providers - #50
Merged
Merged
Conversation
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
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.
Summary
Adds PublicNode by Allnodes to the RPC providers overview and provider sections. Documents its free public RPC endpoints without unsubstantiated marketing claims, including the EVM JSON-RPC example and links to other transports and snapshots.
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 checkpassed under Node 22 after integrating currentmain, including the three-locale build.i18n:check: 0 missing. Both RPC providers translations have current source hashes; remaining stale warnings concern unrelated pages.988and a block number.Docs i18n checklist
npm run i18n:checkreports 0 missing.npm run checkpasses locally.