Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

add mzonder endpoints #1911

Open
wants to merge 2 commits into
base: main
Choose a base branch
from
Open

add mzonder endpoints #1911

wants to merge 2 commits into from

Conversation

maxzonder
Copy link
Contributor

@maxzonder maxzonder commented Feb 27, 2025

Overview

Summary by CodeRabbit

  • New Features
    • Expanded the Celestia Mainnet Beta documentation by adding new endpoints for community RPC, API, gRPC, and WebSocket connections.
    • Introduced additional data availability nodes, offering enhanced connectivity options through new RPC and Gateway ports.
    • Enhanced the Mocha testnet documentation with new community RPC, API, and gRPC endpoints, improving resource availability for users.

Copy link
Contributor

coderabbitai bot commented Feb 27, 2025

Walkthrough

This pull request updates the Celestia documentation for both the Mainnet Beta and Mocha testnet by adding several new community endpoints. The changes include new RPC, API, gRPC, and WebSocket endpoints, along with additional Data Availability node entries specifying their respective port configurations. These updates enhance the documentation by providing users with more options for connecting to the Celestia network.

Changes

File Change Summary
how-to-guides/mainnet.md Added community endpoints: RPC (rpc-celestia.mzonder.com:443), API (api-celestia.mzonder.com:443), gRPC (grpc-celestia.mzonder.com:443), WebSocket (wss://rpc-celestia.mzonder.com:443/websocket); added Data Availability nodes (celestia-archive-rpc.mzonder.com with ports 9090 and 26657, and celestia-da-full-storage.mzonder.com with ports 27758 and 27759).
how-to-guides/mocha-testnet.md Added community endpoints: RPC (celestia-mocha-archive-rpc.mzonder.com with ports 26657 and 9090), RPC (rpc-celestia-testnet.mzonder.com:443), API (http://api-celestia-testnet.mzonder.com:443), gRPC (grpc-celestia-testnet.mzonder.com:443); added full storage node (celestia-testnet-da-full-storage.mzonder.com with ports 27758 and 27759).

Possibly related PRs

Suggested reviewers

  • jcstein

Poem

I'm a rabbit, hopping with delight,
New endpoints shine so clearly bright!
RPCs, APIs dance in a row,
gRPC and websockets set the flow,
With each hop, Celestia’s network grows!
Hop on, explore the changes in sight!


📜 Recent review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between 567bafe and 6717b9e.

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

106-108: Add mzonder Archive RPC Endpoint

The new bullet for the mzonder archive RPC endpoint (celestia-mocha-archive-rpc.mzonder.com) is clearly defined with its associated RPC (26657) and gRPC (9090) ports. This addition aligns with the PR objective of incorporating mzonder endpoints, and the formatting is consistent with the surrounding items.


126-126: Introduce mzonder Community RPC Endpoint

The RPC endpoint rpc-celestia-testnet.mzonder.com:443 has been added to the community endpoints list. Verify that the use of port 443 here is intentional and consistent with the design for community access endpoints. If there are any discrepancies in port usage compared to similar entries, please address them.


207-209: Add mzonder Full Storage Node Endpoint

The addition of the full storage node endpoint celestia-testnet-da-full-storage.mzonder.com with the specified RPC port (27758) and Gateway port (27759) enhances the available node options within the guide. Ensure that these port assignments are correct as per the network configuration. Overall, the change is clearly presented and meets the PR objectives.


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
🪧 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
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: 0

🧹 Nitpick comments (2)
how-to-guides/mainnet.md (2)

178-178: New API Endpoint with Explicit Port

The new API endpoint api-celestia.mzonder.com:443 has been introduced. Note that in the same list there is also an entry api-celestia.mzonder.com without the port. Please verify if both entries are necessary or if they should be consolidated for clarity and consistency.


280-283: New Full-Storage DA Endpoint Addition

The addition of the full-storage DA endpoint:

  • Endpoint: celestia-da-full-storage.mzonder.com
  • RPC Port: 27758
  • Gateway Port: 27759

is a valuable expansion to the node options. It would be helpful to confirm that the distinction between this full-storage node and the archive endpoint (added above) is clear to users—both in terms of functionality and intended usage. Consider adding a brief note in the documentation if further clarification is needed.

📜 Review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between cc90f2e and 567bafe.

📒 Files selected for processing (1)
  • how-to-guides/mainnet.md (6 hunks)
🔇 Additional comments (4)
how-to-guides/mainnet.md (4)

156-157: New RPC Endpoint Addition for Community Consensus Nodes

The addition of the RPC endpoint rpc-celestia.mzonder.com:443 is formatted consistently with the other entries in this section. Please confirm that this endpoint has been tested in production-like scenarios to ensure proper connectivity and TLS configuration when using port 443.


199-199: New gRPC Endpoint Addition

The gRPC endpoint grpc-celestia.mzonder.com:443 has been added. Its format is consistent with other gRPC endpoints. Verify that the endpoint’s configuration (including the port) aligns with your service setup and that it adheres to the network’s security requirements.


208-208: New WebSocket Endpoint Addition

The WebSocket endpoint wss://rpc-celestia.mzonder.com:443/websocket is now part of the community WebSocket endpoints. Its use of the secure WebSocket protocol (wss://) is in line with best practices. Please ensure that the backend service correctly supports WebSocket connections on this endpoint.


262-264: Data Availability Archival Endpoint Addition

A new Data Availability (DA) RPC endpoint for archive nodes has been added:

  • Endpoint: celestia-archive-rpc.mzonder.com
  • gRPC Port: 9090
  • RPC Port: 26657

This configuration is consistent with existing DA endpoints. Please verify that these port assignments and the endpoint semantics align with the network specifications and that documentation elsewhere clearly explains the role of this archive endpoint.

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.

1 participant