docs: use QuickNode public RPC endpoints - #2558
Merged
Merged
Conversation
Contributor
|
🚀 Preview Deployment Your preview is ready: https://celestiaorg.github.io/docs-preview/pr-2558/ |
…ples Public Mocha RPC endpoints are pruned and cannot serve bridge node sync from genesis, so the examples now use an <archive-consensus-endpoint> placeholder with a note explaining the archive requirement. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
jcstein
marked this pull request as ready for review
August 13, 2026 19:37
![devin-ai-integration[bot]](https://avatars.githubusercontent.com/in/811515?s=60&v=4){kind=small}
Point the Mocha hermes rpc_addr at the same QuickNode endpoint as the event_source websocket so queries and event subscriptions use one node. Remove the mochaRpcUrl/mochaRestUrl/mainnetRpcUrl/mainnetRestUrl constants, which are not referenced by any page. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
The public QuickNode endpoints serve celestia-node DA JSON-RPC on 443 in addition to consensus RPC/gRPC, so the Go client guide now uses QuickNode for both endpoints. The full submit and retrieve flow was verified live on Mocha (blob at block 13821340). Document the DA JSON-RPC interface in both network endpoint tables and note that the guide requires Go 1.25.x until bytedance/sonic supports Go 1.26. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Member
Author
Validation runbook results (2026-08-13)All checks run against the public QuickNode endpoints referenced in this PR. Mainnet (
|
| Check | Result |
|---|---|
HTTP RPC /status |
✅ synced, catching_up: false, earliest_block_height: 1 (archive) |
Archive query /block?height=1 |
✅ serves block 1 |
REST /cosmos/base/tendermint/v1beta1/blocks/latest |
✅ |
gRPC over TLS (GetNodeInfo, port 9090) |
✅ celestia-app v9.0.4 |
WebSocket NewBlock subscription |
✅ |
DA JSON-RPC (header.NetworkHead on 443) |
✅ |
Light node header sync (celestia-node v0.31.4, --core.tls) |
✅ |
Mocha (public-endpoint.celestia-mocha.quiknode.pro)
| Check | Result |
|---|---|
HTTP RPC /status |
✅ synced, pruned as expected (earliest ≈ 11805609) |
| REST latest block | ✅ |
gRPC over TLS (GetNodeInfo, port 9090) |
✅ celestia-app v9.0.4 |
WebSocket NewBlock subscription |
✅ live block received |
DA JSON-RPC (header.NetworkHead on 443) |
✅ |
Hermes RPC methods (health, status, block_results, validators, abci_info) |
✅ (validates the rpc_addr change) |
Light node header sync (celestia-node v0.31.4-mocha, --core.tls) |
✅ reached network head; DAS share: data not available retries are p2p sampling, unrelated to the endpoint |
Go client guide (end-to-end)
Ran the guide's exact main.go/go.mod with QuickNode for both DA JSON-RPC and consensus gRPC:
- ✅ account creation, balance query over Core gRPC
- ✅ blob submitted at block 13821340, retrieved, data verified
Note: build requires Go 1.25.x — bytedance/sonic v1.14.1 (transitive via celestia-node) does not compile on Go 1.26 (undefined: GoMapIterator). Workaround GOTOOLCHAIN=go1.25.1 is documented in the guide; the real fix is a sonic bump in celestia-node.
jcstein
commented
Aug 13, 2026
jcstein
commented
Aug 13, 2026
jcstein
commented
Aug 13, 2026
jcstein
commented
Aug 13, 2026
jcstein
left a comment
jcstein
left a comment
Member
Author
There was a problem hiding this comment.
reviewed with human eyes and lgtm. also tested all test cases above in comment
gbarros
approved these changes
Aug 14, 2026
|
Tick the box to add this pull request to the merge queue (same as
|
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
<archival-consensus-endpoint>placeholder with an archive-node warning, because public endpoints are pruned and cannot serve bridge sync from genesisrpc_addrwith the QuickNodeevent_sourcewebsocket so the relayer queries and subscribes to the same nodemochaRpcUrl/mochaRestUrl/mainnetRpcUrl/mainnetRestUrlconstants (not referenced by any page)--chain-id mocha-4in the cli-reference tx example: the "mocha" alias only exists for celestia-node's--p2p.networkflag, while celestia-appd signs transactions against the exact chain ID. Note: chain ID references will move tomocha-5with the network restart tracked in docs: prepare Mocha-5 network restart #2546.bytedance/sonicdoes not compile on Go 1.26 yet;GOTOOLCHAIN=go1.25.1workaround documented)Context
Tracks DEVX-102.
The endpoint aliases and Mainnet/Mocha split were confirmed in the original Slack thread.
Validation
npm run test:endpointsnpm run lint(passes with one unrelated existing warning)npm run build