Skip to content

Add Grove public endpoints to docs#1948

Merged
jcstein merged 1 commit intocelestiaorg:mainfrom
fredteumer:main
Mar 26, 2025
Merged

Add Grove public endpoints to docs#1948
jcstein merged 1 commit intocelestiaorg:mainfrom
fredteumer:main

Conversation

@fredteumer
Copy link
Copy Markdown
Contributor

@fredteumer fredteumer commented Mar 24, 2025

Overview

This PR adds the public endpoints for Celestia DA and Consensus for both Mainnet and Testnet provided by Grove on the Pocket Network to the documentation.

This PR also alphabetizes the providers in the RPC list for better legibility.

Summary by CodeRabbit

  • Documentation
    • Reorganized provider and consensus node endpoint listings for improved clarity.
    • Updated entries by replacing an existing provider with a new one and reordering other providers.
    • Added several new community endpoints and a robust RPC endpoint, enhancing access to the Celestia network on testnet.

@coderabbitai
Copy link
Copy Markdown
Contributor

coderabbitai bot commented Mar 24, 2025

Walkthrough

This pull request updates documentation files in the how-to-guides directory. It reorganizes RPC provider and community consensus node endpoint tables by replacing "QuickNode" with "Grove," reordering entries, and adding new provider entries. The mainnet guide reflects these updates with additional endpoint details, while the mocha-testnet guide similarly adjusts provider ordering and introduces a new RPC endpoint for Celestia testnet DA archival. These modifications reorganize data presentation without changing underlying functionality.

Changes

File Change Summary
how-to-guides/mainnet.md Replaced “QuickNode” with “Grove” in the RPC providers table and reordered entries (placing “Grove” before “Numia”). In the community consensus endpoints table, added new entries (“0xcryptovestor”, “AlphaB”, “Chainode”), updated “Grove” endpoints, and repositioned “lunaroasis” among others.
how-to-guides/mocha-testnet.md Modified RPC providers ordering by replacing duplicate “Grove” entries and moving “QuickNode”. Added a new RPC endpoint (celestia-testnet-da-archival.rpc.grove.city/v1/c33eeadb) across several sections including Production RPC, DA, API, gRPC, and JSON-RPC endpoints.

Possibly related PRs

Suggested reviewers

  • jcstein

Poem

🐰 I'm a bunny, hopping through docs so light,
Sorting out tables in the day and night.
From QuickNode to Grove, the entries now gleam,
New endpoints added like a digital dream.
With every rearrange, my heart does skip a beat—
CodeRabbit celebrates changes, oh so sweet!
🐇✨


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.

❤️ Share
🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

  • Review comments: Directly reply to a review comment made by CodeRabbit. Example:
    • I pushed a fix in commit <commit_id>, please review it.
    • Generate unit testing code for this file.
    • Open a follow-up GitHub issue for this discussion.
  • Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
    • @coderabbitai generate unit testing code for this file.
    • @coderabbitai modularize this function.
  • PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
    • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
    • @coderabbitai read src/utils.ts and generate unit testing code.
    • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
    • @coderabbitai help me debug CodeRabbit configuration file.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

  • @coderabbitai pause to pause the reviews on a PR.
  • @coderabbitai resume to resume the paused reviews.
  • @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
  • @coderabbitai full review to do a full review from scratch and review all the files again.
  • @coderabbitai summary to regenerate the summary of the PR.
  • @coderabbitai generate docstrings to generate docstrings for this PR.
  • @coderabbitai resolve resolve all the CodeRabbit review comments.
  • @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
  • @coderabbitai help to get help.

Other keywords and placeholders

  • Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
  • Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
  • Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

  • You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
  • Please see the configuration documentation for more information.
  • If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

  • Visit our Documentation for detailed information on how to use CodeRabbit.
  • Join our Discord Community to get help, request features, and share feedback.
  • Follow us on X/Twitter for updates and announcements.

Copy link
Copy Markdown
Contributor

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 1

🧹 Nitpick comments (3)
how-to-guides/mocha-testnet.md (1)

64-70: Production RPC Endpoints Table Update: Added Grove and Reordered QuickNode
The changes add the Grove provider at the top of the table and reposition QuickNode. This aligns with the PR objective of including Grove’s details and improves clarity. Please confirm that the ordering meets the intended presentation (alphabetical or prioritized order).

how-to-guides/mainnet.md (2)

100-106: Updated Production RPC Endpoints Table: Grove Entry and QuickNode Reordering
The Production RPC endpoints table now features Grove as the first entry, followed by Numia and then QuickNode. This update reflects the switch from QuickNode to Grove as the primary provider. Please verify that the changes match the intended documentation standards and presentation order.


179-185: Archival DA RPC Endpoints Table Adjustments
The Archival DA RPC endpoints table now includes a Grove entry with its archival endpoint and an updated QuickNode entry. Verify that these modifications correctly reflect the archival endpoint information and that they are consistent with the descriptions in other sections.

📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between e61440c and 587df57.

📒 Files selected for processing (2)
  • how-to-guides/mainnet.md (3 hunks)
  • how-to-guides/mocha-testnet.md (4 hunks)
🔇 Additional comments (2)
how-to-guides/mocha-testnet.md (2)

127-129: New Community JSON-RPC Endpoint Added
A new endpoint (celestia-testnet-da-archival.rpc.grove.city/v1/c33eeadb) has been introduced in the Community JSON-RPC Endpoints section. Verify that the endpoint URL is correct and that its formatting (using backticks) is consistent with the rest of the document.


150-152: New Community API Endpoint Added
The added API endpoint (https://celestia-testnet-da-archival.rpc.grove.city/v1/c33eeadb) provides additional access via the API interfaces. Ensure that this endpoint is consistent with the corresponding RPC endpoint and that users can differentiate between archival and standard endpoints.

Comment thread how-to-guides/mainnet.md
Comment on lines 121 to 143
| Provider | RPC Endpoint | API Endpoint | gRPC Endpoint | WebSocket Endpoint |
|----------|--------------|--------------|---------------|-------------------|
| Numia | `public-celestia-rpc.numia.xyz` | `public-celestia-lcd.numia.xyz` | `public-celestia-grpc.numia.xyz` | - |
| P-OPS | `rpc.celestia.pops.one` | `api.celestia.pops.one` | `grpc.celestia.pops.one` | - |
| lunaroasis | `rpc.lunaroasis.net` | `api.lunaroasis.net` | `grpc.lunaroasis.net:443` | - |
| NodeStake | `rpc.celestia.nodestake.top` | `api.celestia.nodestake.top` | `grpc.celestia.nodestake.top` | - |
| 0xcryptovestor | `celestia-rpc.0xcryptovestor.com` | - | - | - |
| AlphaB | `rpc-celestia.alphab.ai` | `api-celestia.alphab.ai` | `rpc-celestia.alphab.ai:9090` | - |
| Brightly Stake | `celestia-rpc.brightlystake.com` | `celestia-rpc.brightlystake.com/api` | `celestia-rpc.brightlystake.com:9090` | `wss://celestia-ws.chainode.tech:33373/websocket` |
| Stakin | `celestia.rpc.stakin-nodes.com` | `celestia.rest.stakin-nodes.com` | `celestia.grpc.stakin-nodes.com:443` | - |
| Chainode | `celestia-rpc.chainode.tech:33373` | `celestia-api.chainode.tech` | `celestia-grpc.chainode.tech:443` | `wss://celestia-ws.chainode.tech:33373/websocket` |
| Cumulo | `celestia.cumulo.org.es` | `celestia.api.cumulo.org.es` | `celestia.grpc.cumulo.org.es:443` | `wss://celestia.cumulo.org.es:443/websocket` |
| Cumulo Archive | `rpc.archive.celestia.cumulo.com.es` | `api.archive.celestia.cumulo.com.es` | `grpc.archive.celestia.cumulo.com.es:443` | `wss://rpc.archive.celestia.cumulo.com.es:443/websocket` |
| Stakeflow | `rpc-celestia-01.stakeflow.io` | `api-celestia-01.stakeflow.io` | `grpc-celestia-01.stakeflow.io:15002` | - |
| AlphaB | `rpc-celestia.alphab.ai` | `api-celestia.alphab.ai` | `rpc-celestia.alphab.ai:9090` | - |
| Easy2Stake | `celestia-rpc.easy2stake.com` | `celestia-lcd.easy2stake.com` | - | - |
| kjnodes | `celestia.rpc.kjnodes.com` | `celestia.api.kjnodes.com` | `celestia.grpc.kjnodes.com:443` | - |
| 0xcryptovestor | `celestia-rpc.0xcryptovestor.com` | - | - | - |
| Trusted Point | `rpc-celestia-mainnet.trusted-point.com` | `api-celestia-mainnet.trusted-point.com` | `grpc-celestia-mainnet.trusted-point.com:9095` | - |
| Chainode | `celestia-rpc.chainode.tech:33373` | `celestia-api.chainode.tech` | `celestia-grpc.chainode.tech:443` | `wss://celestia-ws.chainode.tech:33373/websocket` |
| Grove | `celestia-consensus-archival.rpc.grove.city/v1/c33eeadb` | `https://celestia-consensus-archival.rpc.grove.city/v1/c33eeadb` | - | - |
| ITRocket | `celestia-mainnet-rpc.itrocket.net:443` | `celestia-mainnet-api.itrocket.net:443` | `celestia-mainnet-grpc.itrocket.net:443` | `wss://celestia-mainnet-ws.itrocket.net:443/websocket` |
| Noders Services | `celestia-rpc.noders.services` | `celestia-api.noders.services` | `celestia-grpc.noders.services:11090` | - |
| kjnodes | `celestia.rpc.kjnodes.com` | `celestia.api.kjnodes.com` | `celestia.grpc.kjnodes.com:443` | - |
| Lava | - | `celestia.rest.lava.build` | `celestia.grpc.lava.build:443` | - |
| lunaroasis | `rpc.lunaroasis.net` | `api.lunaroasis.net` | `grpc.lunaroasis.net:443` | - |
| Mzonder | `rpc-celestia.mzonder.com:443` | `api-celestia.mzonder.com:443` | `grpc-celestia.mzonder.com:443` | `wss://rpc-celestia.mzonder.com:443/websocket` |
| NodeStake | `rpc.celestia.nodestake.top` | `api.celestia.nodestake.top` | `grpc.celestia.nodestake.top` | - |
| Noders Services | `celestia-rpc.noders.services` | `celestia-api.noders.services` | `celestia-grpc.noders.services:11090` | - |
| Numia | `public-celestia-rpc.numia.xyz` | `public-celestia-lcd.numia.xyz` | `public-celestia-grpc.numia.xyz` | - |
| P-OPS | `rpc.celestia.pops.one` | `api.celestia.pops.one` | `grpc.celestia.pops.one` | - |
| Stakeflow | `rpc-celestia-01.stakeflow.io` | `api-celestia-01.stakeflow.io` | `grpc-celestia-01.stakeflow.io:15002` | - |
| Stakin | `celestia.rpc.stakin-nodes.com` | `celestia.rest.stakin-nodes.com` | `celestia.grpc.stakin-nodes.com:443` | - |
| Trusted Point | `rpc-celestia-mainnet.trusted-point.com` | `api-celestia-mainnet.trusted-point.com` | `grpc-celestia-mainnet.trusted-point.com:9095` | - |

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🛠️ Refactor suggestion

Reorganized Community Consensus Endpoints Table
Multiple rows have been added and reordered in the Community Consensus Endpoints table (including new entries for 0xcryptovestor, AlphaB, Chainode, etc.). The updated order appears to follow an alphabetical (or prioritized) approach, which should improve readability. Double-check that all provider names, endpoint URLs, and port information are accurate and consistent with other parts of the documentation.

@jcstein jcstein merged commit bec8116 into celestiaorg:main Mar 26, 2025
2 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