docs: clarify public fallback RPC limitations#1688
Draft
UfukNode wants to merge 1 commit into
Draft
Conversation
Collaborator
🟡 Heimdall Review Status
|
UfukNode
force-pushed
the
docs/clarify-fallback-rpc-limitations
branch
from
c8504f6 to
15e38d8
Compare
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
2 participants
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
Clarifies that the Base Sepolia public RPC and suggested PublicNode fallback RPC are intended for local development, tutorials, and testnet experiments, not production traffic.
Closes #1356.
Why
The build app guide suggests a fallback public RPC endpoint when
https://sepolia.base.orgis unreachable. This update makes the same reliability limitation explicit for both public endpoints so builders do not treat the fallback as production infrastructure.Validation