mocha: fix RPC docs section. Populate DA RPC first

[Bidon15]

Overview

Fixes #1337

Checklist

• New and updated code has appropriate documentation
• New and updated code has new and/or updated testing
• Required CI checks are passing
• Visual proof for any user facing features like CLI or documentation updates
• Linked issues closed with keywords

Summary by CodeRabbit

• Documentation
  • Updated and clarified instructions for connecting to DA Bridge, full, and light nodes on the Mocha testnet, including guidelines for running a local full consensus node when operating a bridge node.

[coderabbitai]

Walkthrough

The update restructures and clarifies the RPC endpoint documentation for the Mocha testnet, specifically for DA Bridge, full, and light nodes. It emphasizes the necessity of running a local full consensus node for bridge node operations and provides detailed connection instructions.

Changes

File Path	Change Summary
nodes/mocha-testnet.md	Updated RPC endpoint instructions for DA Bridge, full, and light nodes; highlighted local full consensus node requirement for bridge nodes.

Assessment against linked issues

Objective	Addressed	Explanation
bug: mocha rpcs not working (#1337)	✅

Related issues

• celestiaorg/docs#1392: This issue might be indirectly related as it involves documentation adjustments. The clarity and accuracy improvements in the RPC endpoint documentation could support a more comprehensive and up-to-date documentation framework, which aligns with the objective of potentially reinstating the Arbitrum rollup guide.

Poem

In the realm of code, under digital skies,
A rabbit hopped, with bright, curious eyes.
🌟 "To the Mocha testnet," it cheerfully said,
"With clearer paths, we confidently tread." 🐾

🐇💻🌌

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>.
  • Generate unit-tests for this file.
• 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 tests 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 generate interesting stats about this repository from git and render them as a table.
  • @coderabbitai show all the console.log statements in this repository.
  • @coderabbitai read src/utils.ts and generate unit tests.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.

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 as PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger a review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai help to get help.

Additionally, you can add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.

CodeRabbit Configration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• The JSON schema for the configuration file is available here.
• 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/coderabbit-overrides.v2.json

CodeRabbit Discord Community

Join our Discord Community to get help, request features, and share feedback.

[coderabbitai]

Review Status

Actionable comments generated: 0

Configuration used: CodeRabbit UI

Commits

Files that changed from the base of the PR and between 8c12369 and dc4548e.

Files selected for processing (1)

• nodes/mocha-testnet.md (2 hunks)

Additional comments: 2

nodes/mocha-testnet.md (2)

• 52-66: The section on RPC endpoints for DA Bridge, full, and light nodes introduces new endpoints and emphasizes the need for running a local full consensus node when operating a bridge node. Ensure that the URLs provided are accurate and accessible. Additionally, consider adding a brief explanation or link to documentation on how to set up a full consensus node for those unfamiliar with the process.
• 79-83: The RPC endpoints section lists default ports and provides a set of endpoints for users to interact with Celestia's nodes. Verify that the default port mentioned (26657) is consistent across all documentation and that the endpoints listed are currently operational and correctly formatted.

[jcstein]

LGTM, thanks for making this

[coderabbitai]

Review Status

Actionable comments generated: 0

Configuration used: CodeRabbit UI

Commits

Files that changed from the base of the PR and between dc4548e and 9d3b02c.

Files selected for processing (1)

• nodes/mocha-testnet.md (2 hunks)

Files skipped from review as they are similar to previous changes (1)

• nodes/mocha-testnet.md