Add new Cumulo endpoints

[santosdios]

Overview

Summary by CodeRabbit

• New Features
  • Added new community RPC, API, gRPC, and WebSocket endpoints for the Celestia Mainnet Beta to enhance connectivity options for users.

[coderabbitai]

Walkthrough

The pull request updates the mainnet.md document to include additional community endpoints for the Celestia Mainnet Beta. New entries have been added for consensus RPC, API, gRPC, and WebSocket endpoints. The changes enhance connectivity options for users without altering existing endpoints or other sections of the document.

Changes

File	Change Summary
how-to-guides/mainnet.md	Added new community endpoints: RPC (rpc.archive.celestia.cumulo.com.es), API (api.archive.celestia.cumulo.com.es), gRPC (grpc.archive.celestia.cumulo.com.es:443), and WebSocket (wss://rpc.archive.celestia.cumulo.com.es:443/websocket).

Possibly related PRs

• Adding moonli.me mainnet endpoints #1591: This PR adds new API endpoints for the Celestia Mainnet, which is related to the addition of new endpoints in the main PR for the Celestia Mainnet Beta.
• Add WebSocket endpoints Cumulo #1741: This PR adds WebSocket endpoints for the Celestia Mainnet Beta, which directly relates to the new WebSocket endpoint added in the main PR.
• Update noders archive RPC in mainnet.md #1732: This PR updates the RPC port configuration in the mainnet.md, which is relevant as it pertains to the same document being modified in the main PR.
• docs: slim down community, fix instances of mainnet -> mainnet beta #1712: This PR focuses on correcting terminology from "mainnet" to "Mainnet Beta," which aligns with the context of the main PR's updates regarding the Mainnet Beta.

Suggested reviewers

• jcstein

🐇 In the meadow, I hop and play,
New endpoints here brighten the day!
RPC, API, all in a row,
Celestia's network continues to grow.
With gRPC and WebSocket in sight,
Connectivity options, oh what a delight! 🌟

---

📜 Recent review details

Configuration used: CodeRabbit UI
Review profile: CHILL

📥 Commits

Reviewing files that changed from the base of the PR and between cd6c8a7 and b03fa51.

📒 Files selected for processing (1)

• how-to-guides/mainnet.md (4 hunks)

🔇 Additional comments (5)

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

142-142: LGTM! The new Cumulo endpoints are well-structured

The additions:

1. Follow consistent naming conventions
2. Are properly categorized in their respective sections
3. Include all necessary endpoint types (RPC, API, gRPC, WebSocket)
4. Are placed under community endpoints with appropriate production usage warnings

Also applies to: 164-164, 185-185, 200-200

---

142-142: Verify the new RPC endpoint's availability

The endpoint follows proper naming conventions. However, we should verify its availability and response.

✅ Verification successful

RPC endpoint is accessible and functioning correctly

The endpoint rpc.archive.celestia.cumulo.com.es is responding properly and is fully synced (not catching up), indicating it's a healthy and operational RPC node.

🏁 Scripts executed

The following scripts were executed for the analysis:

Script:

#!/bin/bash
# Description: Check if the new RPC endpoint is accessible and responding correctly

# Test RPC endpoint health
curl -s "https://rpc.archive.celestia.cumulo.com.es/status" | jq '.result.sync_info.catching_up'

Length of output: 100

---

185-185: Verify the new gRPC endpoint's availability

The endpoint follows proper naming conventions and uses the standard TLS port. Let's verify its accessibility.

---

200-200: Verify the new WebSocket endpoint's availability

The endpoint follows proper WebSocket secure protocol conventions. Let's verify its accessibility.

---

164-164: Verify the new API endpoint's availability

The endpoint follows proper naming conventions. Let's verify its accessibility.

✅ Verification successful

Let me try another verification approach to get more information about the endpoint's response.

---

API endpoint is accessible and functioning correctly

The endpoint api.archive.celestia.cumulo.com.es is responding properly with valid node information. The response confirms:

• Valid SSL certificate
• Running Celestia mainnet network
• Running node version 2.3.1
• Active node with block height 2845970

🏁 Scripts executed

The following scripts were executed for the analysis:

Script:

#!/bin/bash
# Description: Check if the new API endpoint is accessible and responding correctly

# Test API endpoint health
curl -s "https://api.archive.celestia.cumulo.com.es/cosmos/base/tendermint/v1beta1/node_info" | jq '.node_info.network'

Length of output: 122

---

Script:

#!/bin/bash
# Get the full response from the endpoint to understand the issue better
curl -v "https://api.archive.celestia.cumulo.com.es/cosmos/base/tendermint/v1beta1/node_info"

Length of output: 31203

---

Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

🪧 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 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.