Update mocha-testnet.md

[nodersteam]

add NODERS endpoints

Overview

Summary by CodeRabbit

• New Features
  • Added new community RPC, API, and gRPC endpoints for the Mocha testnet.
    • RPC: celestia-t-rpc.noders.services
    • API: https://celestia-t-api.noders.services
    • gRPC: celestia-t-grpc.noders.services:21090

[coderabbitai]

Walkthrough

This pull request updates the how-to-guides/mocha-testnet.md documentation by adding new community endpoints for the Mocha testnet. The update includes three new endpoints from Noders.services: an RPC endpoint, an API endpoint, and a gRPC endpoint. These additions provide users with additional connection options for interacting with the Mocha testnet, expanding the existing list of community-provided endpoints.

Changes

File	Change Summary
how-to-guides/mocha-testnet.md	Added new community endpoints: - RPC: celestia-t-rpc.noders.services - API: https://celestia-t-api.noders.services - gRPC: celestia-t-grpc.noders.services:21090

Possibly related PRs

• Add Nodes.Guru testnet endpoints #1589: Adds RPC, API, and gRPC endpoints for the Nodes.Guru testnet
• ITRocket endpoints for mocha #1597: Introduces new endpoints for ITRocket, including RPC, API, and gRPC endpoints

Suggested reviewers

• jcstein

Poem

🐰 Endpoints dancing, new and bright,
Mocha testnet shines with delight!
Noders.services joins the fray,
Connecting nodes in a rabbit's way
More paths to explore, more networks to see! 🌐

---

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.

[coderabbitai]

Actionable comments posted: 0

🧹 Nitpick comments (1)

how-to-guides/mocha-testnet.md (1)

129-129: Reminder: These are community endpoints not meant for production use

As per the documentation's warning, please ensure users are aware that these community endpoints should not be relied upon for production deployments. Production deployments should use service providers with SLAs or run their own nodes.

Also applies to: 151-151, 176-176

📜 Review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between 0a1917e and 783dd4b.

📒 Files selected for processing (1)

• how-to-guides/mocha-testnet.md (3 hunks)

🔇 Additional comments (1)

how-to-guides/mocha-testnet.md (1)

129-129: LGTM! The new NODERS endpoints are properly formatted and well-placed.

The additions follow the documentation's structure and naming conventions.

Let's verify the endpoints are accessible:

Also applies to: 151-151, 176-176